From: forbrich@yahoo.net   
      
   Ana C. Dent wrote:   
      
   >   
   > Oracle is too brain dead to know about "read-only" transactions.   
   > Oracle GUARENTEES a read consistant view of the database.   
   > If Process B has issued a SELECT prior to Process A doing the COMMIT,   
   > then Oracle ENSURES Process B won't see the changed data. This is   
   > because Oracle can't know what Process B intends to do with the   
   > data from the 1st SELECT. The only way I know how to convince Oracle   
   > that my process wants to see "new data" is to issue a COMMIT (or   
   > ROLLBACK) to indicate all my previous activity is a completed   
   > transaction.After my session issues a COMMIT, Oracle will present   
   > to my session data as it exists at the time of my next SELECT!   
   >   
      
   There are several scenarios & purposes possible.   
      
   If the purpose is to communicate intermediate results to other processes,   
   autonomous transactions might be useful.  They can do their own commits   
   without affecting the transaction's committment state.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)