#23624: Regression in ManyToManyField with through, runtime-generated models
----------------------------------------------+--------------------
     Reporter:  ludoo                         |      Owner:  nobody
         Type:  Bug                           |     Status:  new
    Component:  Database layer (models, ORM)  |    Version:  1.7
     Severity:  Normal                        |   Keywords:
 Triage Stage:  Unreviewed                    |  Has patch:  0
Easy pickings:  0                             |      UI/UX:  0
----------------------------------------------+--------------------
 I admit my situation is a corner case: an app interfacing with a legacy
 db, where I need to extend an abstract model to contextualize it to
 identical tables, named differently (eg obj_1 table, obj_2 table, etc.),
 and to make things worse the number of tables is only known at runtime.

 I am then dynamically generating a module for each set of models, and
 while things work great in Django 1.6, in 1.7 ManyToManyField using a
 through model breaks.

 I am attaching a sample models.py file that illustrates the issue. I have
 not yet found the time to delve into what's happening, I hope someone with
 a better understanding of all the related stuff steps in as it's something
 I have never looked into.

--
Ticket URL: <https://code.djangoproject.com/ticket/23624>
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 post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/048.ce59b5d482628459b9a4d85ceef400e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to