On Mon, Dec 15, 2008 at 4:51 AM, Alex Rades <alera...@gmail.com> wrote: > my understanding about custom managers is that if you want to define a > custom manager, you also HAVE to remember to define the "objects" > manager first, otherwise some parts of django (eg. admin) will not > work.
No, if you want to have every object viewable/editable in the admin you have to either set up a default manager which makes all objects available, or you have to do some overriding in the ModelAdmin subclass to make sure it gets the QuerySet you want it to get. > I find this suboptimal. I find it pretty logical, and I can think of plenty of cases where the ability to prevent access to certain objects is a requirement. So I'm very much against this proposal. -- "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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
