If a Customer can NOT have a LifeInsurance without a Mortgage, then just link LifeInsurance to Mortgage which will then link to a Customer. Of course, if having a Mortgage is not a requirement for LifeInsurance, that won't work and you'll have to use your current scheme with an additional ForiegnKey from LifeInsurance to Customer. In either case, you may want to take a look at the limit_choices_to argument of many-to-one fields[1].
[1] http://www.djangoproject.com/documentation/model_api/#many-to-one-relationships On 8/21/06, Sybren Stüvel <[EMAIL PROTECTED]> wrote: > > So one CustomerData object can have multiple Mortgage and > LifeInsurance objects. > > Now I want to have an extra relation: a LifeInsurance object has to be > linked to a single Mortgage object of the same CustomerData object. > > Is this possible with Django? If so, how? > -- ---- Waylan Limberg [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
