<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Refactoring and Schema Evolution</title>
<link rel="stylesheet" type="text/css" href="../../style.css">
</head>
<body>
<div class="CommonContent">
<div class="CommonContentArea">
<h1>Refactoring and Schema Evolution</h1>
<P>Application design is a volatile thing: it changes from version to version, from one customer implementation to another. The database (if used) changes together with the application. For relational databases this process is called Schema Evolution, for object databases the term Refactoring is used as more appropriate.</P>
<P>Object database refactoring changes the shape of classes stored on the disk. The main challenge here is to preserve old object information and make it usable with the new classes' design.</P>
<P><div class="childTopicList">More Reading:<ul>
<li><p><a href="refactoring_and_schema_evolution/automatic_refactoring.html" class="wikiLink">Automatic refactoring</a></p></li>
<li><p><a href="refactoring_and_schema_evolution/refactoring_api.html" class="wikiLink">Refactoring API</a></p></li>
<li><p><a href="refactoring_and_schema_evolution/field_type_change.html" class="wikiLink">Field type change</a></p></li>
<li><p><a href="refactoring_and_schema_evolution/refactoring_class_hierarchy.html" class="wikiLink">Refactoring Class Hierarchy</a></p></li>
</ul></div>
</P></div>
</div>
<div id="footer">
This revision (5) was last Modified 2006-11-14T18:57:20 by Eric Falsken.
</div>
</body>
</html>
