#36438: makemigrations removes fields in wrong order when GeneratedFields are
involved
-------------------------------------+-------------------------------------
Reporter: Colton Saska | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: Migrations | Version: 5.2
Severity: Normal | Resolution:
Keywords: generatedfield | Triage Stage: Accepted
removefield |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* component: Database layer (models, ORM) => Migrations
* easy: 1 => 0
* keywords: => generatedfield removefield
* stage: Unreviewed => Accepted
Comment:
I haven't reproduced myself but given I can't find any logic in
`AutoDetector._generate_removed_field` to ensure that `GeneratedField`
removals depend on removals of fields they reference this seems legitimate
--
Ticket URL: <https://code.djangoproject.com/ticket/36438#comment:2>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701973ba8fc93-d08b2f24-23ca-4dfc-86d4-689e67f94605-000000%40eu-central-1.amazonses.com.
