Re: define "_default_manager" and the admin-interface

As far as I can see in principle you would want to leave the live manager first as your default manager and then override it in your admin class as the exception - something like this: class EntryAdmin(admin.ModelAdmin): ... manager = Entry.objects But admin needs patching to make that

Re: define "_default_manager" and the admin-interface

is there anybody out there who could answer this question? On 29 Aug., 07:59, Brot <[EMAIL PROTECTED]> wrote: > Hello, > > At the moment I am reading the "Practical Django Projects" - Book > written by James Bennett. > On page 120 there is a admonition about using Default Managers. Above > this

Re: define "_default_manager" and the admin-interface

On Fri, Aug 29, 2008 at 7:59 AM, Brot <[EMAIL PROTECTED]> wrote: > > Hello, > > At the moment I am reading the "Practical Django Projects" - Book > written by James Bennett. > On page 120 there is a admonition about using Default Managers. Above > this paragraph there is the explanation about the

define "_default_manager" and the admin-interface

Hello, At the moment I am reading the "Practical Django Projects" - Book written by James Bennett. On page 120 there is a admonition about using Default Managers. Above this paragraph there is the explanation about the Default Manager und Entry.objects.all() and Entry.live.all(). It seems clear