#36438: makemigrations removes fields in wrong order when GeneratedFields are
involved
-------------------------------------+-------------------------------------
Reporter: Colton Saska | Owner: Clifford
Type: | Gama
Cleanup/optimization | Status: closed
Component: Migrations | Version: 5.2
Severity: Normal | Resolution: fixed
Keywords: generatedfield | Triage Stage: Ready for
removefield | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"1a7fc0f65d5b2ef56625a8b5897496e28a5834ff" 1a7fc0f]:
{{{#!CommitTicketReference repository=""
revision="1a7fc0f65d5b2ef56625a8b5897496e28a5834ff"
Fixed #36438 -- Made MigrationAutodetector remove generated fields before
their base fields.
Thanks to Colton Saska for the report and to Simon Charette for the
review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36438#comment:7>
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/010701984173af8d-d5f95f00-5d13-4587-84a4-45ba9c447eb2-000000%40eu-central-1.amazonses.com.
