#24893: Django migrations don't add unique constraint for field that is changed
from primary_key to unique
---------------------------------+-------------------------------------
Reporter: jbzdak | Owner: timgraham
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"1c57d7e7faaeadb7f32e01586da7997d11df1ad9" 1c57d7e]:
{{{
#!CommitTicketReference repository=""
revision="1c57d7e7faaeadb7f32e01586da7997d11df1ad9"
[1.8.x] Fixed #24893 -- Fixed lack of unique constraint when changing a
field from primary_key=True to unique=True
Backport of e1e6399c2ce39a3656155c4d704340eac83926a7 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24893#comment:5>
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/064.6f995b78df5e345327504b499ee7de29%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
