I suspect that the query isn't being executed, cause you're not
accessing any elements?
have you tried to print games and see what comes out?
passing {games:"object_list"} seems like it should make sense, but
since I'm not an expert on Python or django, I'd imagine that the
"object_list" isn't being hit, hence the no query.
Try the print, and then you'll know if it's a variable in your
template error or something.
Do you have the code that you used when you used a generic view?
HTH
J
On Nov 28, 3:15 pm, "R. Gorman" <r.m.gor...@gmail.com> wrote:
> I've got a real stumper. Well, a stumper for me; I'm hoping someone
> has some insight. Here's the view I'm calling:
>
> def season_schedule_month(request, league_slug, year, month):
> """Given a league slug, retrieve the season's schedule
> month by month.
> return date_based.archive_month(
> request,
> year = year,
> #month_format = "%m"
> month = month,
> date_field = 'date',
> queryset = Game.season.schedule(league_slug),
> template_name ='season_schedule.html')"""
> #games = Game.season.schedule(league_slug).filter
> (date__month=month)
> games = Game.objects.all()
> return render_to_response('season_schedule.html',
> {games:"object_list"},context_instance = RequestContext(request))
>
> It was originally a generic view, but I've reduced it down to a simple
> all objects request because of the bug in my code I'm trying to figure
> out. So the generic view does not work either. The same query run in
> the Django shell produces something like 30 objects. This page is
> returned without any errors but also without any queryset. It doesn't
> even give an empty set of brackets, denoting an empty queryset. I've
> looked at the django debug-toolbar and it does not show the SQL query
> in the queries list, so it appears the query is not even run. Rest of
> the site, which often accesses the same model, runs fine. I have no
> idea why this simple query will not run correctly. It is code related
> because I've moved the code to a different server with a different
> setup and the problem follows.
>
> Anyone run into this before?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
