Re: Foreign key spaghetti

Hi folks, I don't like replying to my own mails, but I'm working against a deadline here. Is it possible to do what I want? Luke wrote: > limit_choices_to is (essentially) a class level attribute, and has > no access to instance level data. which probably means that I can't do what I want base

Re: Foreign key spaghetti

On Mon, Aug 21, 2006 at 01:18:03PM -0400, Waylan Limberg wrote: > In either case, you may want to take a look at the limit_choices_to > argument of many-to-one fields[1]. Could you give me an example of how to do this? I've tried the following. The source is in Dutch, but I'd rather copy & paste t

Re: Foreign key spaghetti

On Mon, Aug 21, 2006 at 01:18:03PM -0400, Waylan Limberg wrote: > 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 wor

Re: Foreign key spaghetti

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 ForiegnK

Foreign key spaghetti

Hi folks, I want to have the following, but I'm not sure on how to do that. This is the layout of the models: CustomerData - name - age - etc. Mortgage - Many-to-one key to CustomerData - start date - end date - sum - etc. LifeInsurance - Many-to-one key to CustomerData - st