On 12/10/06, Darin Lee <[EMAIL PROTECTED]> wrote: > In the console, if I populate the Contest, the instance produces a > "category_set" method/property (as expected and documented). However, > if you "dir(c.category_set)" there is no "finalist_set" method/ > property in the category_set's namespace...
That's because c.category_set is a manager object describing a _set_ of categories. Each item in the set will have its own unique finalist_set member: for example: for cat in c.category_set.all(): print cat.finalist_set.all() or c.category_set.all()[0].finalist_set.all() > So, am I correct in > surmising that the current implementation of the ORM will not > currently work with this type of DB model (2 level indirection)? Is > there a workaround? Any thoughts or suggestions are most welcome. Django _does_ support multiple levels of relations, in both the object structure and the query language - you just have to keep a careful track of when you have an object, and when you have a list of objects. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
