On Thu, Jun 25, 2009 at 3:31 PM, afrobeard <afrobe...@gmail.com> wrote:
>
> I have a problem where I'm using Django, specifically the ORM in a non
> web based daemon script to process some data from a site, by setting
> the environment variables respectively so that it knows where the
> settings module is, etc
>
> I'm running the following query:-
>
> Inqueue.objects.filter(processed = 0).order_by('-timestamp')
>
> Now the thing is that it gets the right results the first time, but if
> someone makes a change on the site that the script itself is unaware
> of, it does not get new items that were added onto the site until the
> script is restarted. It behaves as if it's using some caching system.
>
> Everything works fine on an Ubuntu server, however not on windows
> machines. I'm not sure why, the python and django versions are the
> same on both systems.
>
> Can anybody point me to what could be causing this behavior?
>
> Thanks in advance
> >
>
When a queryset is iterated over it stores the data so if you iterate over
the same queryset object again it doesn't do another DB query. If you want
to iterate over a new one instead of the current one you can just do
queryset.all() and then you won't be going through the cache.
Alex
--
"I disapprove of what you say, but I will defend to the death your right to
say it." --Voltaire
"The people's good is the highest law."--Cicero
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
