On Tue, 2008-09-30 at 03:24 -0700, David Cramer wrote:
> Oh, and it's also selecting the user in that history log query and not
> using it.. at least from the looks of it.
So work out what the actual problems are (or might be) and please file
some tickets. Please don't use the mailing list as a
At least part of it seems to be fixed here:
http://code.djangoproject.com/attachment/ticket/9083/getAdminLogRelated.patch
On Sep 30, 5:24 am, David Cramer <[EMAIL PROTECTED]> wrote:
> Oh, and it's also selecting the user in that history log query and not
> using it.. at least from the looks of it
Oh, and it's also selecting the user in that history log query and not
using it.. at least from the looks of it.
On Sep 30, 5:23 am, David Cramer <[EMAIL PROTECTED]> wrote:
> It seems theres some issues, and this may go outside of the scope of
> the admin history log (I didn't dig into the code).
It seems theres some issues, and this may go outside of the scope of
the admin history log (I didn't dig into the code).
1) It looks like it could use a .select_related('content_type') as
it's doing a query for every content type, repeatedly even.
2) It's adding an ORDER BY on the .get()-like qu
