No Model Inheritance in Magic-Removal?

"James Bennett" <ubernostrumgmail.com> wrote in message
news:21787a9f0605301106ye3ecf9anaaf2d76be974d11bmail.gmail.com...
>
> On 5/30/06, daniel.tietzegmail.com
<daniel.tietzegmail.com> wrote:
> > Now that I knew what I was looking for, I found a
note in this page:
> > http://c
ode.djangoproject.com/wiki/WikiStart : "[...] so
if you need
> > model subclassing stick to one of the older stable
releases".
>
> "or use workarounds like one-to-one
relationships."
>
> It's not the prettiest thing in the world, but it'll
work for now and
> it might be easier to migrate than bringing an entire
app up to
> current trunk from an older release once subclassing is
hashed out.

"it'll work for now..." BUT, as has been
discussed here over the past few
weeks, it is not guaranteed to work for the future -- there
is a warning in
the new docs *not* to use OneToOneField because it's
expected to change
soon.





--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Django users" group.
To post to this group, send email to django-usersgooglegroups.com
To unsubscribe from this group, send email to
django-users-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---