On 10/26/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > It might also be possible to achieve the same with model inheritance > because the way we have decided to expose that is via an attribute on > the base model. So if MyComment was a subclass of Comment, a Comment > instance would have a mycomment attribute (or the name can be set by the > user) that would provide access to the associated MyComment instance.
My personal preference would be to specify an interface that comments have to implement, and then let the actual model be whatever the developer wants; maybe a subclass of django.contib.models.Comment, maybe not. That feels like it'd give the maximum flexibility, and also feels a bit more natural in terms of Python -- rather than having to *be* a Comment, it just has to be able to *act like* a Comment. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
