See also http://code.djangoproject.com/ticket/9676
On Dec 15, 12:51 pm, "Alex Rades" <alera...@gmail.com> wrote: > Hi, > 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. > > I find this suboptimal. > > I think that "objects" should always be the default manager, always > present and working. If you want to define a new one, this should not > interfere with "objects" being present and working. Of course you can > overwrite "objects" if you need to (eg. when you want to customize the > initial queryset). > > The downside of this solution is that you cannot use a field named > "objects", but this is a feature for me, as it improves readability. > > What do you think? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
