Re: [Django] #35422: Migration crash when renaming a field referenced in GeneratedField.expression (was: Migration crash when renaming a field referenced in GeneratedField.expression on SQLite)

[Django]

#35422: Migration crash when renaming a field referenced in
GeneratedField.expression
---------------------------------+------------------------------------
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
---------------------------------+------------------------------------
Changes (by Sarah Boyce):

* summary:
Migration crash when renaming a field referenced in
GeneratedField.expression on SQLite
=>
Migration crash when renaming a field referenced in
GeneratedField.expression

Comment:

> In other words, if we can't generate the SQL for the old field anymore
but we can for the new one then it was certainly changed and the same lack
of alteration support limitation applies.

Makes sense! Agree that I found this on SQLite is irrelevant
--
Ticket URL: <https://code.djangoproject.com/ticket/35422#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.