Re: cross-referencing design question

Daniel and Matthias Thanks for your help. I finally figured out I don't need any automatic Django n:m at all! I just made my own n:m table and everything works the way I expect. I'll really try to keep things simple from now on ... Cheers Mike Mike Dewhirst wrote: > Matthias Kestenholz

Re: cross-referencing design question

Please disregard my previous - I've got something happening/hatching Thanks Matthias and Daniel Mike Mike Dewhirst wrote: > Matthias Kestenholz wrote: > > > >> Is this your complete Membership model? Or do you have additional >> fields there? If you've only got these two foreign keys, it

Re: cross-referencing design question

Matthias Kestenholz wrote: > Is this your complete Membership model? Or do you have additional > fields there? If you've only got these two foreign keys, it might be > better to use a many to many field that references the same model ( > ManyToManyField('self') ) Thanks Matthias - exactly

Re: cross-referencing design question

On Jul 24, 5:46 am, Mike Dewhirst wrote: > I'm new to Django and want to express a self-referencing design > feature to link clients in the same table with each other. Django is > currently objecting to this. Could you please point me to > documentation which will let me

cross-referencing design question

I'm new to Django and want to express a self-referencing design feature to link clients in the same table with each other. Django is currently objecting to this. Could you please point me to documentation which will let me figure it out? This is my models.py in a play project using Django from