SELECT and read-consistentcy

From: Tony Rozga <rozga_at_derby.com>
Date: Thu, 29 Jul 1999 09:38:53 -0600
Message-ID: <37A0758C.C223D965@derby.com>

Hello,

We have an application that archives and optionally deletes large data sets based on user-defined filters (for example, all entities in this date range, etc.). Is there anything wrong with this pseudo-code:

SELECT all entities in the filter range

rowsArchived = 0
FOREACH row

• increment rowsArchived
• perform archive on current row
• IF rowsArchived == userSpecifiedBatchSize THEN
  • execute DELETE statement that deletes the rows that have been archived
    • rowsArchived = 0 ENDIF ENDFOR

In terms of that code, does the DELETE statement (or any other database activity) affect the result set of the original SELECT statement?

Thanks for your help and sorry if this is Oracle 101.

Tony Rozga Received on Thu Jul 29 1999 - 10:38:53 CDT