#26162: Data loss when ManyToManyField refers to the wrong table
-------------------------------------+-------------------------------------
     Reporter:  Ian-Foote            |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.8
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Django 1.6 gave a validation error for this case:
 {{{
 CommandError: One or more models did not validate:
 foo.foo: Accessor for m2m field 'bars' clashes with related m2m field
 'Bar.+'. Add a related_name argument to the definition for 'bars'.
 foo.foo: Reverse query name for m2m field 'bars' clashes with related m2m
 field 'Bar.+'. Add a related_name argument to the definition for 'bars'.
 foo2.foo: Accessor for m2m field 'bars' clashes with related m2m field
 'Bar.+'. Add a related_name argument to the definition for 'bars'.
 foo2.foo: Reverse query name for m2m field 'bars' clashes with related m2m
 field 'Bar.+'. Add a related_name argument to the definition for 'bars'.
 }}}
 but this ceased after 9f76ea1eaad0db0183fa3b5bade16392db0cafbd.

 This might be related to #24505  and its duplicate, #25486.

--
Ticket URL: <https://code.djangoproject.com/ticket/26162#comment:1>
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/067.64495e17bef1e16d0d73bd092a407411%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to