Re: Question about commit
Date: Fri, 17 Sep 2004 14:26:50 +0200
Message-ID: <ciel6a$q3h$1_at_pentheus.materna.de>
Mark C. Stock wrote:
> "Markus Breuer" <markus.breuer_at_gmx.de> wrote in message
> news: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
>
> the commit completes the transaction before returning control to the issuing
> application, and the data is immediately available to all other users with
> privileges
>
> is the second process selecting from a view?
Is there any difference between selecting from a table and form a view? Our processes directly access the table.
I dont know what VPD means...
> some more details about the processes and SQL involved would help. likely
> the version would also be helpful