#31317: Migration using CreateModel with unique_together followed by
AlterUniqueTogether crashes
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
We'll likely have to use a specialized `ddl_statement.Statement` subclass
when deferring constraints and indices and have `_delete_composed_index`
consider them by looping through `dereferred_sql` before raising that
exception.
That would have the benefit of also avoiding creating constraints meant to
be immediately dropped.
--
Ticket URL: <https://code.djangoproject.com/ticket/31317#comment:3>
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/068.a0d7661138d93b8080914394087e2866%40djangoproject.com.
