There are no problems except the fact, that B has to be created and edited as a separate model in the contributed administration and you won't be able to set C's for A, from within A with those select widgets. Although you can still set the administration so that you could edit B as inline for A and select C's there from a drop-down list.
I hope all I've written is understandable. Now you can try creating models and set different settings and see the pros and cons yourself.
Good luck!
Aidas Bendoraitis [aka Archatas]
On 10/20/06, MerMer <[EMAIL PROTECTED]> wrote:
Since a many-to-many relationship is effectively a join table of two
1-many relationships can you implement a many-to-many relationship like
this in django like this? Any problems associated with this approach?
class A
class B
foreignkey(A)
foreignKey(C)
class C
MerMer
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
