Sophie

Sophie

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

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

<html>
  <head>
    <META http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>Referential Integrity</title>
    <link rel="stylesheet" type="text/css" href="../../../../style.css">
  </head>
  <body>
    <div class="CommonContent">
      <div class="CommonContentArea">
        <h1>Referential Integrity</h1>

<p>Referential integrity (RI) is an important feature of RDBMS.
It helps to protect data from misuse and corruption.&nbsp; However, in the modern world of multi-tier and distributed technologies
it becomes questionable if referential integrity should be realized on a
database level or is it a responsibility of a business layer. The answer to
this question depends on the system design.&nbsp;
Usually database RI makes lots of sense in a data-centric application
with one main database. More complex, distributed in space and time referential
constraints can be better implemented within a business object framework.</p>

db4o database does not provide full referential
integrity support, rather it gives a user possibilities to implement RI on the
application level. For an example of a referential integrity solution, see
<a href="../../../implementation_strategies/callbacks/possible_usecases/referential_integrity.html" class="wikiLink">Referential Integrity</a>.


</div>
    </div>
    <div id="footer">
					This revision (1) was last Modified 2007-06-02T20:23:12 by Tetyana.
				</div>
  </body>
</html>