Sophie

Sophie

distrib > Fedora > 15 > i386 > by-pkgid > 864d1c3c3cd8df4e3a2692faf8776e05 > files > 1272

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

<html>
  <head>
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>No test instances</title>
    <link rel="stylesheet" type="text/css" href="../../../style.css">
  </head>
  <body>
    <div class="CommonContent">
      <div class="CommonContentArea">
        <h1>No test instances</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.TestConstructors(false)</code></p></span>
<a name="Advantage"></a><h2>Advantage</h2><p>
will prevent db4o from creating a test instance of persistent classes upon opening a database file.<br>
<br>
</p><a name="Effect"></a><h2>Effect</h2><p>
Upon system startup, db4o attempts to create a test instance of all persistent classes, to ensure that a public zero-parameter constructor is present. This process can take some time, if a large number of classes are present in the database file. For the best possible startup performance this feature can be turned off.<br>
<br>
</p><a name="Alternate Strategies"></a><h2>Alternate Strategies</h2><p>
In any case it's always good practice to create a zero-parameter constructor. If this is not possible because a class from a third party is used, it may be a good idea to write a <a href="../../implementation_strategies/translators.html" class="wikiLink">translator</a> that translates the third party class to one's own class. <br></p><br></div>
    </div>
    <div id="footer">
					This revision (7) was last Modified 2007-05-07T16:17:31 by Tetyana.
				</div>
  </body>
</html>