gabor wrote:
> so, is everyone just cut&paste-ing all this stuff into every model?
I am :) I do it a lot for date based stuff (created/modified) to support
admin/generic views. But whenever it gets figured out all I'll have to
do is change the superclass and delete some cruft - not so bad.
Btw, I'd be very happy to alter admin interface and skip inheritance
support since most of the inheritance usecases I have for content can be
done ("betterly" imo) with delegation*. The problem I have is that if I
have a FooDocument with an fk to DublinCoreMetaCrap, the admin seems
wants me to work from DublinCoreMetaCrap first and add a FooDocument -
perhaps I'm missing something.
cheers
Bill
* Zope/Plone works this way as well. It makes me say things like "FAQ
is_a DublinCore", which is dangerously close to "Car is a subclass of
Carpark" territory.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
