#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
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"3dac3271d286f2790780e89d31ddbb7197f8defa" 3dac327]:
{{{#!CommitTicketReference repository=""
revision="3dac3271d286f2790780e89d31ddbb7197f8defa"
Reverted "Fixed #28646 -- Prevented duplicate index when unique is set to
True on PostgreSQL."
This reverts commit 9cf9c796be8dd53bc3b11355ff39d65c81d7be6d due to a
crash on Oracle
as it didn't allow multiple indexes on the same field.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28646#comment:26>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701910cd65611-e97274d6-d6b6-4031-a853-e6def574a952-000000%40eu-central-1.amazonses.com.
