Question about commit

From: Markus Breuer <markus.breuer_at_gmx.de>
Date: Fri, 17 Sep 2004 09:47:25 +0200
Message-ID: <cie4qd$s30$1_at_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. 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 Received on Fri Sep 17 2004 - 09:47:25 CEST

Original text of this message