#26535: Possible bug - when migrating and removing unique constraint.
-------------------------------+--------------------------------------
Reporter: jenlu | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.9
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 jenlu):
Hi, did some test but unable to reproduce in my ‘current’ setup - it
always generates a
uniqueness constraint that can be removed.
Seems like my oldest models did generate one ordering in pg
(UNIQUE(number, event_id)
whereas models added later on did generate the different ordering in pq
(UNIQUE(event_id,
number) and this later have no problems to be removed/relaxed.
Workaround for me was just to DROP the constraint and add a new one with
same arguments
but in different order..
/ Jens
--
Ticket URL: <https://code.djangoproject.com/ticket/26535#comment:2>
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/063.8fd583f16bc171abdab0429beb217098%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
