On Mon, 2009-02-02 at 22:32 -0800, Simon Westphahl wrote: > On 3 Feb., 03:54, Malcolm Tredinnick <malc...@pointy-stick.com> wrote: > > Have you verified that an object exists for whatever the slug value is > > that you're passing in? Using Django's debug page, you should be able to > > see the slug value and try it out at a Python prompt. That would be the > > first step. > > > > On the surface, your code looks fine. The queryset is cloned each time > > the generic view is called, which causes it to be refreshed, so that > > shouldn't be an issue. I suggest you start debugging from the error > > message: why is nothing matching the query (remember that it's > > performing a "get()" based on the slug, so that's why you're getting an > > ObjectDoesNotExist exception). > > > > Regards, > > Malcolm > > The poblem is with the 'datetime.now' callable passed to my custom > manager. I was able to reproduce the same behavior by starting the > development server and manually changing the clock to a date in the > future. The 'object_detail' generic view of 'objects' created AFTER > the start date of the dev server (emulated by manually changing the > clock ...) are not accessible since the generic view seems to to some > kind of caching.
It's much simpler than that. Hear hoofbeats, think horses.. not zebras. :-) As I mentioned in my reply, the queryset is cloned in the generic view, which causes the query to be run against the database each time (cloning removes any cached Python results). It does *not* mean that the query parameters will be re-evaluated each time, since that could be exorbitantly expensive, given the number of times we clone querysets in the overall scheme of things. The goal in generic views is to make sure we're retrieving the most up-to-date database values for the (same) query each time. Re-evaluating the parameters would lead to a different query each time. Sure, it's a subtle point and maybe you could come up with a documentation change to make it clearer (without overwhelming the explanation of the less minor points, which is always the tricky balance). Hopefully the above paragraphs explain the logic of what's going on behind the scenes and why your solution gives you what you want. > It seems to me as if there is some magic going on ;) Only in the "any sufficiently advanced technology..." sense. :-) 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 django-users@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 -~----------~----~----~----~------~----~------~--~---
