#28646: Migration calls "CREATE INDEX" when one already exists when 'unique'
field
attribute is added
-------------------------------------+-------------------------------------
Reporter: Hari - 何瑞理 | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
postgresql,migration,index | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => worksforme
Comment:
I couldn't reproduce this by changing `SlugField()` to
`SlugField(unique=True)`. Perhaps the bug is in django-tenant-schemas.
Please reopen if you find that Django is at fault and add more specific
steps to reproduce.
--
Ticket URL: <https://code.djangoproject.com/ticket/28646#comment:3>
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/066.f22bb84e477cdabba8a79737ecb8ca1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
