On Wed, Sep 16, 2009 at 2:01 PM, PlanetUnknown <nikhil.kodil...@gmail.com>wrote:
> > Thanks Karen. > Let me explain it a bit more. > e.g. > All CONTACT details are present in one table - email, home address, > work address, home phone, work phone etc. > Forget about the statement about growing for now. > Since each user "has-a" contact it is a pure one-to-one relationship > and not a one-to-many or many-to-one; each user in the USER table will > have only one corresponding entry in the CONTACT table. > Does this help explaining the issue ? > The above is just an example, the main question is how does one > usually implement a "has-a" relationship in dJango. > > Then you are saying you want a OneToOneField. Your rejection of that alternative based on the fact that "seems to be more of an inheritance type" of relationship doesn't make sense to me. The fact that it may be used to implement inheritance relationships doesn't mean it cannot be used for the non-inheritance case. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
