Re: question about the "default" Manager

2010-09-15 Thread Carlton Gibson
On 15 Sep 2010, at 14:28, Rev. Johnny Healey wrote: > According to the django docs: "If you use custom Manager objects, take > note that the first Manager Django encounters (in the order in which > they're defined in the model) has a special status. Django interprets > the first Manager defined i

Re: question about the "default" Manager

2010-09-15 Thread Rev. Johnny Healey
Ahh, clever. Thanks, Johnny -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more o

Re: question about the "default" Manager

2010-09-15 Thread James Bennett
On Wed, Sep 15, 2010 at 8:28 AM, Rev. Johnny Healey wrote: > I may be missing something here, but this jumps out at me as being > impossible.  The ModelBase metaclass receive the attributes as a dict, > so isn't the original order lost? All instances of Manager have an internal-use-only attribute

question about the "default" Manager

2010-09-15 Thread Rev. Johnny Healey
According to the django docs: "If you use custom Manager objects, take note that the first Manager Django encounters (in the order in which they're defined in the model) has a special status. Django interprets the first Manager defined in a class as the "default" Manager, and several parts of Djang