#14549: Disambiguation of target/source fields for intermediary models when 
using
ManyToManyField
---------------------------------------------------+------------------------
          Reporter:  Kronuz                        |         Owner:  nobody
            Status:  new                           |     Milestone:        
         Component:  Database layer (models, ORM)  |       Version:  SVN   
        Resolution:                                |      Keywords:        
             Stage:  Design decision needed        |     Has_patch:  1     
        Needs_docs:  0                             |   Needs_tests:  1     
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Changes (by ramiro):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 1
  * needs_docs:  => 0

Comment:

 This needs tests and is currently causing a test error precisely in the
 model validation tests (modeltests.invalid_models):

 {{{
 FAIL: runTest (__main__.InvalidModelTestCase)
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "./runtests.py", line 85, in runTest
     self.assert_(not unexpected, "Unexpected Errors: " +
 '\n'.join(unexpected))
 AssertionError: False is not True : Unexpected Errors:
 invalid_models.group: Intermediary model RelationshipDoubleFK has more
 than one foreign key to Person. Add a target_fk_name argument to the
 definition for tertiary.
 }}}

-- 
Ticket URL: <http://code.djangoproject.com/ticket/14549#comment:1>
Django <http://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 post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to