On 2008-06-12 14:32, Karen Tracey wrote: > This class isn't > going to ever be used in isolation, so abstract base classes are what you're > after.
> In your case it sounds like you do want the base model to have its own > database table (so you can write File.objects.all()), so it is not a class > that isn't ever going to be used in isolation. Therefore it sounds like > multi-table inheritance is what you want to look at using, not an abstract > base class. You are contradicting yourself (or was that a double negative?), but I got it to work now. To clear it up: the File class is never going to be used in isolation (except for File.objects.all() ), therefore I now use multi-table inheritance. -Stephan --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
