#34333: Migrations tries to add constraint before adding a foreign key.
-------------------------------------+-------------------------------------
Reporter: Raphael Beekmann | Owner: Durval
| Carvalho
Type: Bug | Status: closed
Component: Migrations | Version: 4.1
Severity: Normal | Resolution: fixed
Keywords: migration, | Triage Stage: Ready for
constraint, field | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"4b1bfea2846f66f504265cec46ee1fe94ee9c98b" 4b1bfea]:
{{{
#!CommitTicketReference repository=""
revision="4b1bfea2846f66f504265cec46ee1fe94ee9c98b"
Fixed #34333 -- Fixed migration operations ordering when adding
index/constraint on new foreign key.
Thanks Simon Charette and David Wobrock for reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34333#comment:11>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070186ca725d4d-fe7113ff-ff7b-4fa7-a13e-2642d0c25f21-000000%40eu-central-1.amazonses.com.
