Thanks for the input! While I do think this is the most elegant way of modelling this data there's nothing that necessitates the use of a separate db table to store the addresses, as is the consequence of declaring a separate django model for it.
But it would be nice to not need to declare all address fields more than once. I'm sure I could declare these fields separately and then include them in each model object that needs an address, using some python hackery. I'll look into it when I have more time. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
