I need some sort of GenericForeignKey thing by the end of the week,
and will be getting paid to work on it. I'll go either the subclassing
route or the GenericForeignKey route, whatever is easiest. Let me know
if you need a hand
On 9/26/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
>
> Jason Davi
Jason Davies wrote:
> Robert Wittams wrote:
>
> [snip]
>
>
>>The other form of subtyping - ( ie is-a relationship) available, is the
>>one-to-one field. This makes a set of fields an extension to another
>>object. The way this is generated in django is to add
>>get_ to each instance of the supe
Robert Wittams wrote:
[snip]
> The other form of subtyping - ( ie is-a relationship) available, is the
> one-to-one field. This makes a set of fields an extension to another
> object. The way this is generated in django is to add
> get_ to each instance of the supertype. A base type
> can have a
I have been thinking about the way subtyping (inheritance) works in django.
Currently (correct me if I am wrong), a model class that inherits from
another model class is treated as a copy of its supertype.
This means it makes a copy of all the fields and methods, possibly
suppressing, and can al
