Sophie

Sophie

distrib > Mandriva > current > i586 > media > main-updates > by-pkgid > fc480f9d5aabed8eeaffe8ad3401a94c > files > 5415

openoffice.org-devel-doc-3.2.1-0.3mdv2010.2.i586.rpm

<html>
<head>
<title>Constants' Group TransactionIsolation</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" type="text/css" href="../../../../idl.css">
</head>
<body>
<div id="adc-idlref">

<a name="_top_"> </a><table class="navimain" border="0" cellpadding="3">
<tr>
<td class="navimain"><a href="../module-ix.html" class="navimain">Overview</a></td>
<td class="navimain"><a href="module-ix.html" class="navimain">Module</a></td>
<td class="navimainnone">Use</td>
<td class="navimain"><a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Using_DBMS_Features#Transaction_Handling" class="navimain">Devguide</a></td>
<td class="navimain"><a href="../../../../index-files/index-1.html" class="navimain">Index</a></td>
</tr>
</table>
<table class="navisub" border="0" cellpadding="0">
<tr>
<td class="navisub"><a href="#Constants" class="navisub">Constants</a></td>
<td class="navisub"><a href="#ConstantDetails" class="navisub">Constants' Details</a></td>
</tr>
</table>
<hr>
<table border="0" width="100%" cellpadding="5" cellspacing="3" class="title-table" style="margin-bottom:6pt;">
<tr>
<td><p class="namechain"><a href="../../../../module-ix.html" class="namechain">::</a> <a href="../../../module-ix.html" class="namechain">com</a> :: <a href="../../module-ix.html" class="namechain">sun</a> :: <a href="../module-ix.html" class="namechain">star</a> :: <a href="module-ix.html" class="namechain">sdbc</a> :: </p>
</td>
</tr>
<tr>
<td class="title">constants group TransactionIsolation</td>
</tr>
<tr>
<td><dl>
<dt><b>Description</b></dt>
<dd>distinguishes different possible transaction isolation levels.
 </dd>
</dl>
<a name="devmanual"> </a><dl>
<dt><b>Developers Guide</b></dt>
<dd><a href="http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Database/Using_DBMS_Features#Transaction_Handling">Database - Using DBMS Features - Transaction Handling</a></dd>
</dl>
</td>
</tr>
</table>
<hr>
<a name="Constants"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
<tr>
<td class="subtitle" colspan="2">Constants</td>
</tr>
<tr>
<td class="imsum_left"><a href="#NONE">NONE</a></td>
<td class="imsum_right">indicates that transactions are not supported.
 &nbsp;</td>
</tr>
<tr>
<td class="imsum_left"><a href="#READ_UNCOMMITTED">READ_UNCOMMITTED</a></td>
<td class="imsum_right">Dirty reads, non-repeatable reads and phantom reads can occur. 
 This level allows a row changed by one transaction to be read 
 by another transaction before any changes in that row have been 
 committed (a "dirty read"). If any of the changes are rolled back, 
 the second transaction will have retrieved an invalid row.
 &nbsp;</td>
</tr>
<tr>
<td class="imsum_left"><a href="#READ_COMMITTED">READ_COMMITTED</a></td>
<td class="imsum_right">Dirty reads are prevented; non-repeatable reads and phantom 
 reads can occur. This level only prohibits a transaction 
 from reading a row with uncommitted changes in it.
 &nbsp;</td>
</tr>
<tr>
<td class="imsum_left"><a href="#REPEATABLE_READ">REPEATABLE_READ</a></td>
<td class="imsum_right">Dirty reads and non-repeatable reads are prevented; phantom 
 reads can occur. This level prohibits a transaction from 
 reading a row with uncommitted changes in it, and it also 
 prohibits the situation where one transaction reads a row, 
 a second transaction alters the row, and the first transaction 
 rereads the row, getting different values the second time 
 (a "non-repeatable read").
 &nbsp;</td>
</tr>
<tr>
<td class="imsum_left"><a href="#SERIALIZABLE">SERIALIZABLE</a></td>
<td class="imsum_right">Dirty reads, non-repeatable reads and phantom reads are prevented. 
 This level includes the prohibitions in 
 <code>REPEATABLE_READ</code>
 and further prohibits the 
 situation where one transaction reads all rows that satisfy 
 a WHERE condition, a second transaction inserts a row that 
 satisfies that WHERE condition, and the first transaction 
 rereads for the same condition, retrieving the additional 
 "phantom" row in the second read.
 &nbsp;</td>
</tr>
</table>
<a name="ConstantDetails"/><table border="1" width="100%" cellpadding="5" cellspacing="0" class="subtitle">
<tr>
<td class="subtitle">Constants' Details</td>
</tr>
<tr>
<td class="imdetail"><a name="NONE" class="membertitle">NONE</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center">
<tr>
<td>const long <b>NONE</b> =  0;<hr>
<dl>
<dt><b>Description</b></dt>
<dd>indicates that transactions are not supported.
 </dd>
</dl>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td class="imdetail"><a name="READ_UNCOMMITTED" class="membertitle">READ_UNCOMMITTED</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center">
<tr>
<td>const long <b>READ_UNCOMMITTED</b> =  1;<hr>
<dl>
<dt><b>Description</b></dt>
<dd>Dirty reads, non-repeatable reads and phantom reads can occur. 
 This level allows a row changed by one transaction to be read 
 by another transaction before any changes in that row have been 
 committed (a "dirty read"). If any of the changes are rolled back, 
 the second transaction will have retrieved an invalid row.
 </dd>
</dl>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td class="imdetail"><a name="READ_COMMITTED" class="membertitle">READ_COMMITTED</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center">
<tr>
<td>const long <b>READ_COMMITTED</b> =  2;<hr>
<dl>
<dt><b>Description</b></dt>
<dd>Dirty reads are prevented; non-repeatable reads and phantom 
 reads can occur. This level only prohibits a transaction 
 from reading a row with uncommitted changes in it.
 </dd>
</dl>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td class="imdetail"><a name="REPEATABLE_READ" class="membertitle">REPEATABLE_READ</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center">
<tr>
<td>const long <b>REPEATABLE_READ</b> =  4;<hr>
<dl>
<dt><b>Description</b></dt>
<dd>Dirty reads and non-repeatable reads are prevented; phantom 
 reads can occur. This level prohibits a transaction from 
 reading a row with uncommitted changes in it, and it also 
 prohibits the situation where one transaction reads a row, 
 a second transaction alters the row, and the first transaction 
 rereads the row, getting different values the second time 
 (a "non-repeatable read").
 </dd>
</dl>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td class="imdetail"><a name="SERIALIZABLE" class="membertitle">SERIALIZABLE</a><table border="0" width="96%" cellpadding="5" cellspacing="0" class="table-in-data" bgcolor="#ffffff" align="center">
<tr>
<td>const long <b>SERIALIZABLE</b> =  8;<hr>
<dl>
<dt><b>Description</b></dt>
<dd>Dirty reads, non-repeatable reads and phantom reads are prevented. 
 This level includes the prohibitions in 
 <code>REPEATABLE_READ</code>
 and further prohibits the 
 situation where one transaction reads all rows that satisfy 
 a WHERE condition, a second transaction inserts a row that 
 satisfies that WHERE condition, and the first transaction 
 rereads for the same condition, retrieving the additional 
 "phantom" row in the second read.
 </dd>
</dl>
</td>
</tr>
</table>
</td>
</tr>
</table>
<a href="#_top_">Top of Page</a><hr size="3"><p class="copyright" align="center">Copyright &copy; 2011, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.</p>

</div> <!-- id="adc-idlref" -->
</body>

</html>