Wednesday 12 October 2011

2 modes of isolation for form module

{\rtf1\ansi\ansicpg1252\deff0\deflang16393{\fonttbl{\f0\froman\fprq2\fcharset0 Times New Roman;}{\f1\fnil\fcharset0 Calibri;}}
{\*\generator Msftedit 5.41.21.2509;}\viewkind4\uc1\pard\lang1033\f0\fs22\par
\pard\li720 Specifies whether or not transactions in a session will be serializable. If Isolation Mode has the value Serializable, the end user sees a consistent view of the database for the entire length of the transaction, regardless of updates committed by other users from other sessions. If the end user queries and changes a row, and a second user updates and commits the same row from another session, the first user sees Oracle error (ORA-08177: Cannot serialize access.).\par
\par
Read committed (default)\par
\pard\fi720 Serialize \par
\pard\par
\pard\li720 The serialize works in conjunction with the block's locking property set as delayed. The basic idea behind serialize is that the user sees a consistent set of rows throughout the entire runtime session, inspite of any row being changed by another user of different session.\par
This is mainly useful when the application access a very large databases and very few users use the appln so that the chances of users waiting for locked records is less.\par
\par
\pard\sa200\sl276\slmult1\lang9\f1\par
}

No comments:

Post a Comment