#28646: Migration calls "CREATE INDEX" when one already exists when 'unique'
field
attribute is added (PostgreSQL)
-------------------------------------+-------------------------------------
Reporter: Hari - 何瑞理 | Owner: bcail
Type: Bug | Status: closed
Component: Migrations | Version: 1.11
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
postgresql,migration,index,#djangocph| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"9cf9c796be8dd53bc3b11355ff39d65c81d7be6d" 9cf9c79]:
{{{#!CommitTicketReference repository=""
revision="9cf9c796be8dd53bc3b11355ff39d65c81d7be6d"
Fixed #28646 -- Prevented duplicate index when unique is set to True on
PostgreSQL.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28646#comment:25>
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/010701910440b617-02d0ca4e-0f0a-48f1-9b15-1f5efcd3d38e-000000%40eu-central-1.amazonses.com.
