From: anacedent@hotmail.com   
      
   Markus Breuer  wrote in   
   news:cie4qd$s30$1@pentheus.materna.de:   
      
   > I have a question about oracle commit and transactions. Following   
   > scenario:   
   >   
   > Process A performs a single sql-INSERT into a table and commits the   
   > transaction. Then he informs process B (ipc) to read the new date.   
      
   As strange as this may sound PRIOR to issuing the SELECT,   
   Process B needs to issue a COMMIT.   
      
   I suspect that this will allow Process B to "see" the new data.   
      
   >So   
   > process B starts "select ..." but does not get the previously inserted   
   > row. The timespan between commit and select is very short.   
   > (NOTE: two different sessions are used)   
   >   
   > Questions:   
   > 1.) Does commit when returning from call ensure, that all changes are   
   > immediatelly visible to all other Sessions/transactions?   
   > 2.) Does commit ensure only that all data is stored persistent, but   
   > changes are deferred visible to other transactions?   
   > 3.) May the "select ..." cause the problem? Other than dml statements   
   > a select does not start a transaction. Would "select for update"   
   > instead solve the problem?   
   >   
   > regards markus   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)