#34856: Running tests with historical migrations that contain index together 
fails
with TypeError.
-------------------------------+--------------------------------------
     Reporter:  Sage Abdullah  |                    Owner:  nobody
         Type:  Bug            |                   Status:  closed
    Component:  Migrations     |                  Version:  dev
     Severity:  Normal         |               Resolution:  invalid
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by David Sanders):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I was about to reply linking to the 4.2 release notes then saw you
 answered your own question:

 > To add, the ‚Äč4.2 release notes do say the following though:
 > ...
 > But with the problem in this ticket, it seems squashing the migrations
 will be mandatory?

 Yes :)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34856#comment:2>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018ab30e801a-4829da8a-3b6d-49fe-a320-9c50ff6e984d-000000%40eu-central-1.amazonses.com.

Reply via email to