#28646: Migration calls "CREATE INDEX" when one already exists when 'unique' 
field
attribute is added (PostgreSQL)
-------------------------------------+-------------------------------------
     Reporter:  Hari - 何瑞理        |                    Owner:  (none)
         Type:  Bug                  |                   Status:  new
    Component:  Migrations           |                  Version:  1.11
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
  postgresql,migration,index         |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 Comments on PR: we have an error in the boolean logic, not correctly
 distinguishing between the `_unique` and `primary_key` cases.

 (The original suggestion leads to just 3 failures a fix should be simple
 enough...)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28646#comment:9>
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.8edd22b675062033426ba5cbe30d69e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to