Re: Question about commit
Date: Sat, 18 Sep 2004 00:54:15 GMT
Message-ID: <XGL2d.67752$XP3.11846_at_edtnps84>
Ana C. Dent wrote:
>
> Oracle is too brain dead to know about "read-only" transactions.
> Oracle GUARENTEES a read consistant view of the database.
> If Process B has issued a SELECT prior to Process A doing the COMMIT,
> then Oracle ENSURES Process B won't see the changed data. This is
> because Oracle can't know what Process B intends to do with the
> data from the 1st SELECT. The only way I know how to convince Oracle
> that my process wants to see "new data" is to issue a COMMIT (or
> ROLLBACK) to indicate all my previous activity is a completed
> transaction.After my session issues a COMMIT, Oracle will present
> to my session data as it exists at the time of my next SELECT!
>
There are several scenarios & purposes possible.
If the purpose is to communicate intermediate results to other processes, autonomous transactions might be useful. They can do their own commits without affecting the transaction's committment state. Received on Sat Sep 18 2004 - 02:54:15 CEST