Commit-read question
Posted in 2003
I am experiencing a quirk of some sorts. I am
running the query below with a wait 30 against a table that has an application
stepping thru recordid #'s checking for the next record that has a status of
"not processed". Once the application does other modifications to other tables
it updates the status to "complete" and moves to find the next record that
needs to be processed.
select recordid
from xxxx
where processor = xx
and clubcode = 'xx'
order by recordid.
As the query is running, is returning what I am to believe is the before and
after image of the record to the sql editor grid.
recordid status processor clubcode id createtime lstupdate
xxxxxxx W xx xx 60627539 7/10/2003 11:44 7/10/2003 11:44
xxxxxxx C xx xx 1060627539 7/10/2003 11:44 7/10/2003 11:58
I am running IDS 7.31UC2 with the database unbuffered. I understand the
default read is commited-read. Can someone please explain how this maybe
happening? Why am I getting both? I have my theories but would like some input.