Russell Keith-Magee wrote: > On 9/4/06, Sean Perry <[EMAIL PROTECTED]> wrote: >> >> So according to this, I am doing things correctly and should not get an >> error. Bug? Code change without document update? > > > Yes, this seems to be a bug. The documentation is correct, and agrees with > the actual model implementation. It looks like the problem is the model > validator in manage.py being overly vigilant. In addition, it looks like the > 'invalid_models' unit test doesn't currently check this particular > condition. > > This should definitely be logged. >
I dropped a ticket on Trac, will see if it shows up. Looking at the code myself, it seems that the problem boils down to get_accessor_name(). Most of the django code seems to know not to use this method if the relationship is symmetrical. However it is not clear from the code is ALL of django honors this. Perhaps if symmetrical is true get_accessor_name should return None or some similarly bogus value. This would also make the test in core/management.py work as planned. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
