Hi Russ,
Thanks for the reply. I had previously tried to do a
ManyToMany("self") a few months ago, with no luck, so I figured it must
still be the case. Also, the "bug" for this is still open:
http://code.djangoproject.com/ticket/75
So, I quickly went in and tried this out, and unfortunately, it doesn't
solve the problem. The advantage in my original approach, an
intermediary class with two ForeignKeys, is that it has a sense of
directionality: it's an ordered graph. With ManyToMany, it's
unordered, and I'm not quite sure how I can store that directionality
anywhere.
So I may be stuck with the intermediary unless anyone has any brilliant
ideas.
Which brings up my original question -- is there any easy way to
translate a QuerySet on one node into a QuerySet on another (by use of
a ForeignKey field)?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
