#31503: Moving a unique constraint from unique_together to Field.unique 
generate an
invalid migration.
-------------------------------------+-------------------------------------
     Reporter:  Xiang Wang           |                    Owner:  David
                                     |  Wobrock
         Type:  Bug                  |                   Status:  assigned
    Component:  Migrations           |                  Version:  3.0
     Severity:  Normal               |               Resolution:
     Keywords:  unique_together      |             Triage Stage:  Accepted
  unique migrations                  |
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  1
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by David Wobrock):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 A first PR https://github.com/django/django/pull/14722 with approach 5/
 (from my comment above) basically.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31503#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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.9c08e4e9a15be84639611195f506469a%40djangoproject.com.

Reply via email to