I have a database of patients ("Patient" model), and a patient can
have subordinate accounts which is a self-foreign-key (eg, for family
members), We also store multiple addresses for each patient (home,
work, billing). I'm pretty sure I need to have an Address model as a
many-to-one, because a patient can have multiple addresses. But, I'm
also thinking of going one more step and making it a many-to-many,
because multiple patients (eg, a family) can share the same address.
Am I over-normalizing if I do this? It seems that it would make
editing via the admin a bit more difficult, however the data would
not be duplicated. Is there a good rule-of-thumb for these kind of
design decisions?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
