diff options
Diffstat (limited to 'docs/installation/upgrade_4_8_dpl.html')
| -rw-r--r-- | docs/installation/upgrade_4_8_dpl.html | 68 |
1 files changed, 36 insertions, 32 deletions
diff --git a/docs/installation/upgrade_4_8_dpl.html b/docs/installation/upgrade_4_8_dpl.html index da0005fd..e9d3b6fc 100644 --- a/docs/installation/upgrade_4_8_dpl.html +++ b/docs/installation/upgrade_4_8_dpl.html @@ -7,14 +7,14 @@ <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> - <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> - <link rel="prev" href="upgrade_4_8_toc.html" title="Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="up" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> + <link rel="prev" href="upgrade_4_8_toc.html" title="Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8" /> <link rel="next" href="upgrade_4_8_mpool.html" title="Minor Change in Behavior of DB_MPOOLFILE->get" /> </head> <body> <div xmlns="" class="navheader"> <div class="libver"> - <p>Library Version 11.2.5.3</p> + <p>Library Version 12.1.6.1</p> </div> <table width="100%" summary="Navigation header"> <tr> @@ -22,7 +22,7 @@ </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="upgrade_4_8_toc.html">Prev</a> </td> - <th width="60%" align="center">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> + <th width="60%" align="center">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8</th> <td width="20%" align="right"> <a accesskey="n" href="upgrade_4_8_mpool.html">Next</a></td> </tr> </table> @@ -37,41 +37,45 @@ </div> </div> <p> - Entity subclasses that define secondary keys must now be registered - prior to storing an instance of the class. This can be done in two - ways: -</p> + Entity subclasses that define secondary keys must now be + registered prior to storing an instance of the class. This can + be done in two ways: + </p> <div class="itemizedlist"> <ul type="disc"> <li> - <p> - The <code class="methodname">EntityModel.registerClass()</code> method - may be called to register the subclass before opening the - entity store. - </p> + <p> + The + <code class="methodname">EntityModel.registerClass()</code> + method may be called to register the subclass before + opening the entity store. + </p> </li> <li> - <p> - The <code class="methodname">EntityStore.getSubclassIndex()</code> - method may be called to implicitly register the subclass after - opening the entity store. - </p> + <p> + The + <code class="methodname">EntityStore.getSubclassIndex()</code> + method may be called to implicitly register the + subclass after opening the entity store. + </p> </li> </ul> </div> - <p> - Failure to register the entity subclass will result in an - <code class="classname">IllegalArgumentException</code> the first time an - attempt is made to store an instance of the subclass. An exception will - not occur if instances of the subclass have previously been stored, - which allows existing applications to run unmodified in most cases. -</p> - <p> - This behavioral change was made to increase reliability. In several - cases, registering an entity subclass has been necessary as a - workaround. The requirement to register the subclass will ensure that - such errors do not occur in deployed applications. -</p> + <p> + Failure to register the entity subclass will result in an + <code class="classname">IllegalArgumentException</code> the first + time an attempt is made to store an instance of the subclass. + An exception will not occur if instances of the subclass have + previously been stored, which allows existing applications to + run unmodified in most cases. + </p> + <p> + This behavioral change was made to increase reliability. In + several cases, registering an entity subclass has been + necessary as a workaround. The requirement to register the + subclass will ensure that such errors do not occur in deployed + applications. + </p> </div> <div class="navfooter"> <hr /> @@ -84,7 +88,7 @@ <td width="40%" align="right"> <a accesskey="n" href="upgrade_4_8_mpool.html">Next</a></td> </tr> <tr> - <td width="40%" align="left" valign="top">Chapter 13. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8 </td> + <td width="40%" align="left" valign="top">Chapter 15. Upgrading Berkeley DB 4.7 applications to Berkeley DB 4.8 </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> |