On Sat, Jun 27, 2009 at 12:55 PM, Daniele Procida <dani...@apple-juice.co.uk > wrote:
> > I am wondering what sort of coding/storage approach to take to manage > contact details in a more sophisticated way. > > For example, one person might need: > > Phone (London): xxx xxxxx > Phone (Edinburgh): xxx xxxxxx > > and another: > > Phone (office): xxx xxxx > Phone (laboratory): xxx xxxx > Phone (mobile): xxx xxxxx > > but you can't know in advance how any particular person might need their > details labelled. > > Is there a name for this kind of scheme, or a standard way of handling it? > > Thanks, > > Daniele > > > > > Yep, you'd have a second model that has a foreign key to person that has the type and number fields on it. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
