On Mon, Jun 16, 2008 at 1:48 PM, Johannes Dollinger <[EMAIL PROTECTED]> wrote: > You could as stick them in a single manager as well (and wouldn't > have to remember which method is available via which manager). > My point is that one manager per model would be enough to do anything > you can do with multiple managers (and if you want modified querysets > you get a little extra flexibility if you just subclass QuerySet).
Simply "being enough" won't cut it though, because you'd end up having to do some very ugly things and crowding up your single manager with a lot of stuff that'd make more sense logically broken out. 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. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
