Re: problems with request.user

of effect this has on the efficiency of the underlying DB hit, but it seems the best I can do for now. --B On Aug 21, 12:20 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Wed, Aug 20, 2008 at 5:13 PM, Burr Settles <[EMAIL PROTECTED]> wrote: > > > I recently came

problems with request.user

I recently came back to a project I put on hold for a couple weeks, and after updating the Django trunk, all my references to "request.user.id" are broken. Here is an example view for a rating widget: 1 @login_required 2 def rate(request, song_id): 3 song = get_object_or_404(Song, pk=song_id)

Complex queryset construction

Hey fellow djanglers, I am trying to construct a view that's a bit complicated, and struggling to create the proper queryset. Hopefully some of you have done something like this before, or otherwise have some ideas on how to tackle it efficiently. Imagine we have something like these models: cl