Sophie

Sophie

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

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

<html>
  <head>
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>Query Modes</title>
    <link rel="stylesheet" type="text/css" href="../../../style.css">
  </head>
  <body>
    <div class="CommonContent">
      <div class="CommonContentArea">
        <h1>Query Modes</h1><p>What is the best way to process queries? How to get
the optimum performance for your application needs?</p>

<p>Those of you, who have dealt with query time and
memory constraints (situations, when query result is bigger than the memory
available, or when query time is longer than the whole functional operation)
should know how searching a suitable solution might affect the whole
application design and implementation.</p>

<p>Luckily db4o takes most of the trouble for itself.
There are 3 query modes allowing to fine tune the balance between speed, memory
consumption and availability of the results:</p>

<ul><li>immediate </li><li>lazy</li><li>snapshot</li></ul>





<p>The query mode can be set using:</p>

<span name="cs_wiki_filter" csw_filters="net"><p>.NET:&nbsp; </p><p><code>configuration.Queries().EvaluationMode(QueryEvaluationMode)</code> <br></p>

</span><p>

Let's look at each of them in more detail.</p><p><div class="childTopicList">More Reading:<ul>
<li><p><a href="query_modes/immediate_queries.html" class="wikiLink">Immediate Queries</a></p></li>
<li><p><a href="query_modes/lazy_queries.html" class="wikiLink">Lazy Queries</a></p></li>
<li><p><a href="query_modes/snapshot_queries.html" class="wikiLink">Snapshot Queries</a></p></li>
</ul></div>
&nbsp;</p></div>
    </div>
    <div id="footer">
					This revision (5) was last Modified 2007-04-23T06:31:11 by Tetyana.
				</div>
  </body>
</html>