Sorry I was unclear...
I'm currently using the same song_dict for both podcast and
playlist.xml, which is  'queryset': Song.objects.all(),
That's fine for the podcast. In the template I reverse sort it on
pub_date, and it's perfect.
But for playlist I want   something like:  'queryset':
Song.objects.all().order_by('?')[:30] as I don't want all of the
objects, and I need a random sample.

So, my question is, do I need to define a second dict for playlist, or
can I somehow modify song_dict in the URL line to just grab a random
30 items instead of all of them?



On May 11, 11:34 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Fri, 2007-05-11 at 09:14 -0700, [EMAIL PROTECTED] wrote:
> > OK, I have song_dict, which gathers up songs:
> > song_dict = {
> >     'queryset': Song.objects.all(),
> >     'allow_empty': 'true',
> > }
>
> > Which I pass to the podcast and playlist.xml. Playlist.xml is picked
> > up by the flash player for folks who want to listen on-site:
>
> >  (r'^radio/podcast.xml',
> > 'django.views.generic.list_detail.object_list', dict(song_dict,
> > template_name="radio/podcast.xml")),
> >  (r'^radio/playlist.xml',
> > 'django.views.generic.list_detail.object_list', dict(song_dict,
> > template_name="radio/playlist.xml")),
>
> > Podcast.xml does a reverse sort on pub date, which works nicely for
> > the podcast. No problems there. The problem is the playlist. The
> > number of songs are overloading it a bit, so what I'd like to do is a
> > random slice of 30 songs or so.
>
> > So my question is, do I need another dict, or can I slice and sort on
> > song_dict for the playlist only?
>
> If you're wanting to use a different queryset, then you at least need to
> change the 'queryset' key in the song_dict dictionary. That seems so
> obvious that I'm pretty sure I don't understand the question you're
> really asking. Could you ask it in another way or give an example of
> what you've tried that doesn't work?
>
> Regards,
> Malcolm


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to