On Fri, 2008-11-14 at 00:17 -0500, Steve Holden wrote:
[...] > Sure. Perhaps it's not common terminology: by "recursive" I meant a > self-referential relationship, though now you mention it I see that the > same issue can occur if the order of model definitions is sub-optimal. The recursive case is just a collapsed form of forwards references, so I didn't address that specifically. You don't even need sub-optimal ordering to require forwards references. For example, circular reference loops (particularly with NULL relations) aren't unheard of. Even in Django, you need forwards reference to implement the "through" option for ManyToMany fields, since you need to define the intermediate model with a ForeignKey to model A and then define model A with a many-to-many through the intermediate model. So one of them has to be defined second. All I'm saying is that forwards references crop up naturally; they're not a wart (and references to the same model are the other obvious case they crop up naturally). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
