i do not know the answer to your question, but it reminded me that
there is a decorator like @login_required or something that you could
use in stead of checking your self. (if it applies to your case).
konstantin
On Mar 7, 4:18 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> On a more specific note, I'm finding lots of places I've done
> something like:
> if request.user.is_authenticated() and request.user.is_staff):
>
> It seems to me there's a redundant check being made there. Wouldn't
> one have to be authenticated for is_staff to evaluate to true, meaning
> I can safely just say
>
> if request.user.is_staff?
>
> On Mar 7, 2:45 pm, "Karsu" <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hello,
>
> > First, If you use many relations it is very important to use JOIN
> > like: Example.objects.filter(first_object__second__third=something)
>
> > It is important to use select_related too (also in template!!)
>
> > example:
>
> > {% for item in example.objects.all %}
> > {{ item.related_object.value }}
> > {% endfor %}
>
> > TO
>
> > {% for item in example.objects.select_related %}
> > {{ item.related_object.value }}
> > {% endfor %}- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
