Thanks a lot Andrew !!
It never occurred to me but you were absolutely correct.
In my connect I turned off auto-commit. Maybe that had some bearing on the
behaviour.
Anyway, my solution was to simply issue a rollback immediately before
polling the table of interest. Works !!
Thanks for taking
Steve Baldwin schrieb am 23.04.2012 um 20:53 (+1000):
>
> loop
> select count(*) from some_table
> sleep 2 seconds
> end loop
>
> My problem is that the count shows the number of rows the first time
> it executes and from that point never changes.
>
> While the program is running, I insert r
Steve,
First, a caveat: I've never used mysql, so I could be totally off-base
here.
Perhaps this behavior is the result of some implicit transaction, so
the first SELECT begins a transaction, and the DBMS wants to present a
consistent view of the database (that is, return the
Hi all,
This is driving me nuts.
I have a simple test case where I do something like this :
loop
select count(*) from some_table
sleep 2 seconds
end loop
My problem is that the count shows the number of rows the first time it
executes and from that point never changes.
While the program is
