Am 16.06.2008 um 20:56 schrieb James Bennett: > It'd also hurt the reusability of managers (which is a big advantage I > and others have taken advantage of), because you wouldn't be able to > keep methods specific to a single model separate from methods which > aren't, at least not without introducing a whole chain of manager > classes inheriting from each other to bring in the right sets of > methods.
That's exactly what I do now - I have model specific managers and use them as bases for submodel managers. There are no reusability drawbacks and you can split functionality as needed. You could add a manager_mixin attribute to Meta to make the parallel inheritance structure (models and managers) more convenient. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
