#27946: Removing unique_together creates invalid migration
-----------------------------+--------------------------------------
Reporter: Robin Elvin | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by Robin Elvin):
This is on MySQL.
In the course of trying to recreate this issue I have discovered that the
issue stems from the fact that the table does not have the UNIQUE KEY
currently. I am unsure as to how this has happened but this means that the
table is not consistent with the migrations. I have manually added the
UNIQUE KEY back using ALTER TABLE and successfully applied the migration.
So, I don't know if this is something migrations should handle. Given that
the desired state of the model is in effect what it is currently should it
just ignore the error? Or perhaps the error message should be more
descriptive as this threw me off the scent for quite a while.
--
Ticket URL: <https://code.djangoproject.com/ticket/27946#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.3451b076cb60085e8d2e3bae27853cc0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
