#35422: Migration crash when renaming a field referenced in
GeneratedField.expression on SQLite
---------------------------------+------------------------------------
Reporter: Sarah Boyce | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 5.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Simon Charette):
I don't think the problem is specific to SQLite.
The non-invasive back portable solution I can think of is for `FieldError`
to be caught and also result in a `ValueError` pointing out that the
generated field must be removed first.
--
Ticket URL: <https://code.djangoproject.com/ticket/35422#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f3a23b309-1b0a8ab0-8fdc-474c-95d8-6d517b0bbdf7-000000%40eu-central-1.amazonses.com.
