#31834: Cannot sqlmigrate on Django migrations that change unique_together
----------------------------+--------------------------------------
Reporter: Brіаn Lаі | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.0
Severity: Normal | Resolution: duplicate
Keywords: sqlmigrate | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => duplicate
* component: Database layer (models, ORM) => Migrations
Comment:
I think we can mark this as a duplicate of #26624, because they have the
same cause. In both scenarios a constraint doesn't exist in the database
and cannot be introspected, `sqlmigrate` works properly if you first apply
a migration which adds a constraint.
--
Ticket URL: <https://code.djangoproject.com/ticket/31834#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/062.b215cdf3955ec5f32c194be418fca7fb%40djangoproject.com.
