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).
>
> 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 queries which it is
> doing. I'm concerned that this is a bug deeper inside the codebase
> than just the history log.
>
> http://www.pastethat.com/1AJeU
>
> django-debug-toolbar informed me of this, talk about usefulness ;)
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
