On 11/04/2013 4:41pm, Lachlan Musicman wrote:
At the moment I have tables on the database:
account_account
account_account_parents
account_account_children
account_account_partners
account_account_siblings
Not wishing to throw a spanner in the works, but I have always had a
design in the back of my mind for such a set of relationships.
I think it needs a single table for all the people and a through table
carrying sufficient information to accurately describe each
relationship. This would deliver flexibility to describe any possible
relationship including client, supplier, apprentice etc.
I don't think it would be as complex as a multi-table design like yours
but that would depend on what your system has to achieve.
Mike
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
