On Sat, 2007-02-10 at 23:22 +0000, Zach Seifts wrote: > I don't want to use a ForeignKey. I want to be able to set up a class > in the model and not have a table created. Maybe the base model thing > is the way to do it. I've read somewhere about mixins, could these be > of interest?
As Collin mentioned, true model inheritance in Django (even with abstract base classes as you are doing here) does not work yet. The reason is that although it works on the Python level, you end up with the wrong model manager and the multi-table queries are not constructed correctly. A fix for this will land shortly (see [1]). For what you are trying to do, you might be able to get away with not making Foo a subclass of models.Model and then making Bar inherit from both models.Model and Foo, although I'm not 100% sure that will work correctly, either. But it should be fairly quick to test. Sorry we cannot help you with a perfect solution. This is completely my fault -- I have been dragging the chain on this one. It will be fixed soon. [1] http://code.djangoproject.com/wiki/VersionOneFeatures Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
