hello,
I myself hink that your solution with foreign keys is good. the fact
that django requires raw sql to handle left joins is its limitation
but not that of your design.
another solution that comes to mind is to have a table of generic
"attributes" for each patron. this way you will have two tables, one
with patrons the other with attributes.
model Attribute(models.Model) :
owner = models.ForeignKey(Patron)
type = ...field for attribute type perhaps...
value = ...field for attribute value...
it is difficult though to have attributes of different types, data,
blobs, integers, srings because you will have to have separate fields
for that.
konstantin
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
