From: forbrich@yahoo.net   
      
   Markus Breuer wrote:   
      
   > 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. 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   
      
   Instead of trying to fix your solution, you might be able to use other   
   Oracle capabilities to fix your problem ...   
      
   If you are attempting to communicate between session, you might want to look   
   at "autonomous transactions" to do the interaction using tables or   
   "dbms_pipe" for interaction using IPCs.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)