Hello Jeff, Not sure of your implementation but you should be able to adapt: http://projects.django-development.com/trac/dd_devel/wiki/recursive_groups_of_groups to work. You could replace department with navigation-collection and employee with menu item I believe. If nothing else the tests show examples of using self referencing m2m.
Mark On Mar 2, 10:01 am, Jeffrey Taggarty <jtagga...@gmail.com> wrote: > Hi Guys, > > I have a website (go figure!) where there is a main navigation, there > is going to need to be sub pages for each main nav item, but this sub > page can belong to more than 1 main nav, typically in the past I used > a self referencing FK to handle this, but this time it's a m2m, any > tips on how i should go about modeling this? I guess my real confusion > is with the FK way of doing things I used the _set on the parent model > to get the subs. What can I do with the m2m way of doing this? > > Thx > > Jeff -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
