On 20 fév, 17:07, Michael Elsdörfer <[EMAIL PROTECTED]> wrote:
> > I understand you could also reuse it from model to model, but in my
> > code I have rarely found reusing those methods between different
> > models, except some ways that would generally be better solved with
> > model inheritance.
>
> Managers as a concept are very useful. For example, they can also
> inherit from one another, which I use in a couple instances. A base
> class might provide the initial queryset, which is further modified by
> descendant managers: One returning only rows that are intended for the
> general public, while another might allow access to everything,
> including e.g. unapproved records.
Couldn't that be done using chaining staticmethods, such as
@classmethod
def even_positive_low(cls) : return cls.positive().filter(bar__lt=25)
>
> With static methods, you also couldn't do things like:
>
> if request.user.is_admin:
> manager = MyModel.objects
> else:
> manager = MyModel.public_objects
>
> # work with ``manager``
Not trying to be slow-witted, but couldn't you do
objects = MyModel.unfiltered() if request.user.is_admin else
MyModel.filtered()
(where objects is a queryset)
is there a functionnal difference or is it more of a style (which can
have its importance) ?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
