Re: Querying in a loop - cached results?

On Sun, Aug 8, 2010 at 3:09 PM, Karen Tracey wrote: > > Probably you are seeing the effects of the default transaction isolation >> level on MySQL/InnoDB, which is "repeatable read". See >> http://groups.google.com/group/django-users/browse_thread/thread/e25cec400598c06dfor

Re: Querying in a loop - cached results?

On Sun, Aug 8, 2010 at 11:52 AM, Daniel Roseman wrote: > > > Where is this query running - in a view, or an external script? And > how is the data being added to the db? In both cases -- adding data and analyzing -- it is an external script, using the Django ORM. Nick

Re: Querying in a loop - cached results?

On Sun, Aug 8, 2010 at 1:03 PM, Nick Arnett wrote: > I'm having a problem that I can't figure out from reading the docs. I have > a loop that runs the same query every five minutes, to see if there is new > data to process. However, it doesn't return the new data the

Re: Querying in a loop - cached results?

On Aug 8, 6:03 pm, Nick Arnett wrote: > I'm having a problem that I can't figure out from reading the docs.  I have > a loop that runs the same query every five minutes, to see if there is new > data to process.  However, it doesn't return the new data the second and >

Querying in a loop - cached results?

I'm having a problem that I can't figure out from reading the docs. I have a loop that runs the same query every five minutes, to see if there is new data to process. However, it doesn't return the new data the second and subsequent times it loops. It's something like this: while 1: data