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 work which is an open ticket
http://code.djangoproject.com/ticket/7510.
At the moment you would need to override every method in
admin.ModelAdmin that gets the default manager, so it's easier at the
moment just to make the standard manager the default instead of your
custom manager.
I'm writing a blog on this book - but I am only just finishing up
chapter 5 which first defines the custom manager.
http://blog.haydon.id.au/2008/08/notes-on-practical-django-projects.html
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
