On 3/25/06, James Bennett <[EMAIL PROTECTED]> wrote: > > On 3/25/06, Andy Dustman <[EMAIL PROTECTED]> wrote: > > Surprisingly (a bit, at least), I created an app with the example model: > > ..snip... > > > Which is not what you'd expect based on that page, so presumably the > > changes haven't been implemented yet. Or is the page obsolete? I'd > > assume not since there are some post-PyCon Sprint notes there. > > I'd bet on "not yet implemented". I don't know whether discussion's > still going on about the best way to handle it or not, but generally > once something's implemented a note about it is added on the > "RemovingTheMagic" wiki page.
I think it's safe to say that model inhertiance doesn't work at all at this point, or at least it doesn't in the admin interface. You can add new items to a subclassed table, and they show up on the index, but when you try to edit one, it tries to pull them out of the base class' table, and you get a 404 page. It took a couple hours of testing and cursing until I finally made the backup print all SQL statements, and figured out what was going on. Plus there is the previously-mentioned problem that ManyToManyFields are not inherited. -- The Pythonic Principle: Python works the way it does because if it didn't, it wouldn't be Python. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
