#33125: Changing model field to become PK creates redundant UNIQUE constraint
--------------------------------------+------------------------------------
     Reporter:  Fabio Sangiovanni     |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  Migrations            |                  Version:  dev
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. We can probably add the same behavior as in #29496
 (see 6dd4edb1b4f5441c5f543e29395039839c50d10b) on Oracle to other
 backends.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33125#comment:1>
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/065.08a805769b4400e6aab26a12eebca01a%40djangoproject.com.

Reply via email to