#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
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"45ba7683a6e399815731a13cceb3acb518a2f1f2" 45ba7683]:
{{{#!CommitTicketReference repository=""
revision="45ba7683a6e399815731a13cceb3acb518a2f1f2"
Refs #36438 -- Made FieldOperation.references_field() detect references in
GeneratedField.expression.
Thanks to Simon Charette for the suggestion and review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36438#comment:8>
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/010701984173afce-6f70384c-7548-4b26-946d-679e9b94b6f2-000000%40eu-central-1.amazonses.com.
