MVSFORUMS.com

[anu.k]

Hi,

In my application program, I have declared a cursor with some 'where' clause for table X. For each Fetch from the cursor, I am 'inserting' a new row into the table X which also satisfies the 'where' clause.

My question is, somehow these newly inserted rows are seeping back into the cursor and are being fetched again. I am not sure of the reason.

Please advice on why this is happening and ways to overcome it.

Thanks
Anu

[dbzTHEdinosauer]

before SENSITIVE Cursors where available,
we could normally get around this
by having a WHERE Condition in the DECLARE CURSOR
that would not be satisfied by the new INSERTs; normally a date.

Knowing that this would occur,
I have always been able to avoid it,
thus never complicated my SQL with Scrollable/Sensitive cursors.
Read up on these types of Cursors, they were introduced to easily solve this type of problem.
_________________
Dick Brenholtz
American living in Varel, Germany

[vini]

When you INSERT do you have a column correspoding to Current date for ex: a Creation date ?

If yes, you can change your WHERE clause to exclude these rows
For ex:
WHERE...
......
AND CREATION_DATE < :WSH-CURRENT-DATE

[kalidasv]

This is interesting.

Are you executing the 'OPEN CURSOR' statement multiple times.

My understanding/experience is once the 'OPEN CURSOR' statement is executed, newly inserted rows should not cause any difference. Only when the CURSOR is closed and opened again, the rows inserted would be fetched.

Database gurus, please help.

[kolusu]