> If you want to be able to specify a different default manager for some > particular use of an existing model, you're sort of after a third type > of model subclassing that I've thought about but haven't implemented: > subclassing an existing model and explicitly telling Django that this is > only Python-level (and not database-/ORM-level) inheritance.
You're absolutely right--thanks for that a-ha moment. This really seems like the cleanest way of getting custom functionality onto models while leaving existing code alone. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
