#28646: Migration calls "CREATE INDEX" when one already exists when 'unique' field attribute is added (PostgreSQL) -------------------------------------+------------------------------------- Reporter: Hari - 何瑞理 | Owner: nobody Type: Bug | Status: new Component: Migrations | Version: 1.11 Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted postgresql,migration,index | Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------------+------------------------------------- Changes (by Tim Graham):
* component: Database layer (models, ORM) => Migrations * stage: Unreviewed => Accepted Comment: I can reproduce as long as the three operations are in the same migration. The crash doesn't happen if you put the `AlterField` operations in a separate migration. -- Ticket URL: <https://code.djangoproject.com/ticket/28646#comment:5> 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 post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/066.42aafaeae5a61983fad4b062bc10173e%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.