Sophie

Sophie

distrib > Fedora > 14 > i386 > by-pkgid > 864d1c3c3cd8df4e3a2692faf8776e05 > files > 1269

db4o-doc-7.4-2.fc13.i686.rpm

<html>
  <head>
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>No lock file thread</title>
    <link rel="stylesheet" type="text/css" href="../../../style.css">
  </head>
  <body>
    <div class="CommonContent">
      <div class="CommonContentArea">
        <h1>No lock file thread</h1><div id="TOC"><div id="TOCinner"><span class="TOCtitle">Contents</span><div class="TOCcontents"><ul><li><a href ="#Advantage">Advantage</a></li><li><a href ="#Effect">Effect</a></li><li><a href ="#Alternate Strategies">Alternate Strategies</a></li></ul></li></ul></div></div></div>




<span name="cs_wiki_filter" csw_filters="net">
<p>.NET: </p><p><code>configuration.LockDatabaseFile(false)</code></p>
</span>
<a name="Advantage"></a><h2>Advantage</h2>
<p>
will prevent the creation of a lock file thread on Java platforms without NIO (&lt; JDK 1.4.1).
</p>
<a name="Effect"></a><h2>Effect</h2>
<p>
If file locking is not available on the system, db4o will regularily write a timestamp lock information to the database file, to prevent other VM sessions from accessing the database file at the same time. Uncontrolled concurrent access would inevitably lead to corruption of the database file. If the application ensures that it can not be started multiple times against the database file, db4o file locking may not be necessary.</p>
<a name="Alternate Strategies"></a><h2>Alternate Strategies</h2>
<p>
Database files can safely be opened from multiple sessions in readonly mode. Use:</p>


<span name="cs_wiki_filter" csw_filters="net">
<p>.NET: </p><p><code>configuration.ReadOnly(true)</code></p>
</span></div>
    </div>
    <div id="footer">
					This revision (7) was last Modified 2007-05-07T15:51:32 by Tetyana.
				</div>
  </body>
</html>