Hi, I'm wanting to reduce an unneeded query from my page views in my project caused from Django's built-in auth_messages. I'm looking for the best solution to do this while still allowing me to use contrib/ auth and the admin.
The source of the query comes from the 'auth' context processor, I believe. So one solution I've thought of would be not to use it. But then the admin breaks horribly. I'm curious of 2 workarounds: 1) Add the 'auth' context processor only for URLs starting with '/ admin/'? 2) Since I might want the user object hanging off of request at some point, write my own auth context processor that doesn't add messages or permissions stuff to request. I'm not sure exactly which parts of the 'auth' context processor the admin uses so maybe this would need to also do #1. Or is there a better way to take care of this want (not necessarily a "need"). Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
