[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_<extension_type_name> to each instance of the supertype. A base type
> can have any combination of extensions.
>
>
> I would suggest that the second type of subtyping is a more natural fit
> for python inheritance of model classes.
[snip]
That sounds like a good solution. Preserving the semantics of Python's
subclassing is important so that things are intuitive and work as
expected.
Would this have any bearing on solving ticket #529 (GenericForeignKey)?
An aside: will we still break backwards compatibility after milestone
1.0?
Jason