On Fri, 2009-08-07 at 00:30 -0700, Jan Ostrochovsky wrote:
> Thank you, Malcolm.
>
> In fact, our current design was, as you recommended:
>
> Subject ---one-to-one-null-false--- Address ---one-to-one-null-true---
> Payment (Invoice)
>
> I want to use generic views and to join Subject+Address
Thank you, Malcolm.
In fact, our current design was, as you recommended:
Subject ---one-to-one-null-false--- Address ---one-to-one-null-true---
Payment (Invoice)
I want to use generic views and to join Subject+Address in the same
form, and model inheritance seemed to me as most straightforward
On Thu, 2009-08-06 at 07:15 -0700, Jan Ostrochovsky wrote:
> Hello,
>
> http://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance
> says:
> The inheritance relationship introduces links between the child model
> and each of its parents (via an automatically-created
Hello,
http://docs.djangoproject.com/en/dev/topics/db/models/#multi-table-inheritance
says:
The inheritance relationship introduces links between the child model
and each of its parents (via an automatically-created OneToOneField).
4 matches
Mail list logo
