#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 Jacob Walls <jacobtylerwalls@…>):
In [changeset:"336e713e2a1ac143eeec021d66a6f3168f983183" 336e713]:
{{{#!CommitTicketReference repository=""
revision="336e713e2a1ac143eeec021d66a6f3168f983183"
Refs #36438 -- Simplified retrieval of GeneratedField base fields in
migrations autodetector.
This was creating an unusable Q object solely to call
referenced_base_fields on it.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36438#comment:9>
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/01070199638ac75c-b3028199-9365-461c-aa64-6925bf9e15d9-000000%40eu-central-1.amazonses.com.
