On Mon, 2009-02-23 at 02:38 -0800, fero wrote:
> I tried to override the default manager when I am importing my views.
>
> I noticed that I needed to do override both;
>
> * objects attribute
> * _default_manager attribute
>
> In my views module I do something like
>
> from app.models import MyModel
> from app.models.managers import MyManager
>
> MyModel.add_to_class('objects', MyManager())
> MyModel.add_to_class('_default_manager', MyManager())
>
> Overriding the '_default_manager' attribute is needed in order to make
> the AnyModel?.foreingKey_set working with the new custom manager.
>
> Is it correct and/or safe ?
Highly unrecommended. Very internal API (subject to change). Also, not
part of the design intention of managers. If another application sets up
the managers for their models, it's because they know what the
appropriate default, and other, managers are. If you're reusing that
application, you don't get to change that (well, you can, by flailing
about wildly under the covers, but, as I say, highly unsupported).
You'd be advised to rethink the problem you're trying to solve.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
