#33125: Changing model field to become PK creates redundant UNIQUE constraint
-------------------------------------+-------------------------------------
Reporter: Fabio Sangiovanni | Owner: Jordan
Type: | Bae
Cleanup/optimization | Status: closed
Component: Migrations | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f5a3243911a5c42775cd838a3da1d0f3ac4a74ee" f5a32439]:
{{{
#!CommitTicketReference repository=""
revision="f5a3243911a5c42775cd838a3da1d0f3ac4a74ee"
Fixed #33125 -- Avoided redundant unique constraint when converting a non-
unique field to primary key on MySQL and PostgreSQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33125#comment:7>
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/065.07264563cd25c5b887618e4d83549441%40djangoproject.com.
