#33938: Defining the "through" model in a many-to-many field in another app 
causes
"AttributeError: 'str' object has no attribute '_meta'" on migration
-------------------------------------+-------------------------------------
     Reporter:  bryan.af7            |                    Owner:  Simon
                                     |  Charette
         Type:  Bug                  |                   Status:  closed
    Component:  Migrations           |                  Version:  4.0
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  migration many-to-   |             Triage Stage:  Ready for
  many bug                           |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):

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


Comment:

 In [changeset:"c9ebd5b7aa82c2958c59786a9925037602ab00b8" c9ebd5b7]:
 {{{
 #!CommitTicketReference repository=""
 revision="c9ebd5b7aa82c2958c59786a9925037602ab00b8"
 [4.1.x] Fixed #33938 -- Fixed migration crash for m2m with a through model
 in another app.

 Regression in aa4acc164d1247c0de515c959f7b09648b57dc42.

 Thanks bryangeplant for the report.

 Backport of 71902e0d9f93670c4f93ff9d66095b0e571be74b from main
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33938#comment:6>
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/01070182d4226e4f-64c7eac2-1892-45e5-90bc-5fd6dc8fc8dc-000000%40eu-central-1.amazonses.com.

Reply via email to