From: mcstockX@Xenquery   
      
   "Ana C. Dent"  wrote in message   
   news:Xns956745E1C17DDSunnySD@68.6.19.6...   
   | 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.   
   |   
      
   That does sound strange... the only reason for this would be if B is in a   
   read-only transaction... (see my other post).   
      
   Issuing a COMMIT to see other user's changes is never a requirement.   
      
   If B is in a read-only transaction, then a COMMIT or ROLLBACK should only be   
   entered when the read-only transaction is completed (per the business   
   functionality specification), not as a work around to a scenario that is not   
   yet fully analyzed.   
      
   ++ mcs   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)