Adrian Holovaty wrote:
> On 9/18/05, Eric Walstad <[EMAIL PROTECTED]> wrote:
>
>>I'd like to make a base class for my model classes that defines some
>>fields but doesn't result in a table in the database. If my base class
>>is derived from meta.Model, then django makes a table for it in the
>>database.
>>
>>Is it possible to do what I want, move common fields to a super class,
>>without generating a table for that super class?
>
>
> It's not currently possible, but that exact functionality is on the
> to-do list: http://code.djangoproject.com/ticket/419 .
>
> Adrian
>
Is it possible or planned to make the generated methods for superclasses
aggregate sub class instances?
Eg
class animal(meta.Model):
name = TextField()
class dog(animal):
pass
class cat(animal):
pass
Then animal.get_list(name__exact='Fluff') would return instances of both
cats and dogs.
As far as I can tell this doesn't currently work.
