#28646: Migration calls "CREATE INDEX" when one already exists when 'unique'
field
attribute is added (PostgreSQL)
-------------------------------------+-------------------------------------
Reporter: Hari - 何瑞理 | Owner: bcail
Type: Bug | Status: assigned
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
postgresql,migration,index,#djangocph|
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by bcail):
* needs_better_patch: 1 => 0
Comment:
Hi Mariusz, I added that test. I also updated the code to use "CREATE
INDEX IF NOT EXISTS"... what do you think of going that direction?
--
Ticket URL: <https://code.djangoproject.com/ticket/28646#comment:17>
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/0107018da443ce23-a3e5726d-89fb-4819-9125-c3ef0ef1ff12-000000%40eu-central-1.amazonses.com.
