#34529: Squashing migrations with Meta.index_together -> indexes transition 
should
remove deprecation warnings.
-------------------------------------+-------------------------------------
     Reporter:  Mariusz Felisiak     |                    Owner:  Mariusz
                                     |  Felisiak
         Type:  Bug                  |                   Status:  closed
    Component:  Migrations           |                  Version:  4.2
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8e2460d599aec95f8cfe514d3cc8acdd4ca4b1fb" 8e2460d5]:
 {{{
 #!CommitTicketReference repository=""
 revision="8e2460d599aec95f8cfe514d3cc8acdd4ca4b1fb"
 Fixed #34529, Refs #34525 -- Reduced index operations with
 Meta.indexes/index_together when optimizing migrations.

 This makes squashing migrations an available path for changing
 Meta.index_together, which is deprecated, to Meta.indexes.

 Follow up to f81032572107846922745b68d5b7191058fdd5f5.
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34529#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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070187e14b62e1-7f568aa6-da88-4fd8-b85a-4cb62bf6ff80-000000%40eu-central-1.amazonses.com.

Reply via email to