Re: Serializable transactions

Hi Thomas,

this behaviour is not strange, it is normal.

Setting the isolation level to seriazable forces ORACLE to check whether the data you are manipulating is the same as it was when the transaction started.

Start of a transaction are:

• connecting to the database
• terminate previous transaction with commit / rollback

set transaction does not open a new transaction !

[Quoted] At the beginning of transaction 1 there were 3 rows in table ref_table_1. But at the time the delete takes place there are only two rows in that table therefore ORACLE knows that there have been changes during the transaction and the update is refused.

bye

Roger

• Sent from AltaVista http://www.altavista.com Where you can also find related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is Beautiful