svn commit: r998438 [4/6] - in /websites/production/db/content/derby: ./ blogs/ dev/ integrate/ manuals/ papers/ papers/DerbyTut/ releases/ skin/

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

svn commit: r998438 [4/6] - in /websites/production/db/content/derby: ./ blogs/ dev/ integrate/ manuals/ papers/ papers/DerbyTut/ releases/ skin/

bpendleton
Modified: websites/production/db/content/derby/releases/release-10.10.1.1.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.10.1.1.html (original)
+++ websites/production/db/content/derby/releases/release-10.10.1.1.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.10.1.1 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.10.1.1 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -515,7 +515,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="Distributions"></a>
+</div>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby. You should <strong>always</strong> <a href="#Verifying Releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -539,13 +540,13 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.1.1/db-derby-10.10.1.1-src.zip">db-derby-10.10.1.1-src.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.1.1/db-derby-10.10.1.1-src.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.1.1/db-derby-10.10.1.1-src.zip.md5">MD5</a>]<br>
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.1.1/db-derby-10.10.1.1-src.tar.gz">db-derby-10.10.1.1-src.tar.gz</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.1.1/db-derby-10.10.1.1-src.tar.gz.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.1.1/db-derby-10.10.1.1-src.tar.gz.md5">MD5</a>] (Note that, due to long filenames, you will need gnu tar to unravel this tarball.)</p>
 </div>
-<a name="N10094"></a><a name="Release Notes for Apache Derby 10.10.1.1"></a>
+<a name="Release Notes for Apache Derby 10.10.1.1"></a>
 <h2 class="boxed">Release Notes for Apache Derby 10.10.1.1</h2>
 <div class="section">
 <div>
 <p>These notes describe the difference between Apache Derby release 10.10.1.1 and the preceding release 10.9.1.0.</p>
 </div>
-<a name="N1009D"></a><a name="Overview"></a>
+<a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <div>
 <p>The most up to date information about Derby releases can be found on the <a href="http://db.apache.org/derby/derby_downloads.html">Derby download page</a>.</p>
@@ -562,7 +563,7 @@ document.write("Last Published: " + docu
 <li>Java ME CDC/Foundation Profile 1.1 with JSR-169 JDBC Optional Package for CDC/Foundation Profile.</li>
 </ul>
 </div>
-<a name="N100C0"></a><a name="New+Features"></a>
+<a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <div>
 <p>This is a feature release. The following new features were added:</p>
@@ -583,7 +584,7 @@ document.write("Last Published: " + docu
 <strong>Optional tools</strong> - Derby has new, optional tools to support data migration and metadata queries. See the "Optional tools" section in the Derby Tools and Utilities Guide.</li>
 </ul>
 </div>
-<a name="N100E9"></a><a name="Bug+Fixes"></a>
+<a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <div>
 <p>The following issues are addressed by Derby release 10.10.1.1. These issues are not addressed in the preceding 10.9.1.0 release.</p>
@@ -1189,7 +1190,7 @@ document.write("Last Published: " + docu
 </tr>
 </table>
 </div>
-<a name="N10665"></a><a name="Issues"></a>
+<a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <div>
 <p>Compared with the previous release (10.9.1.0), Derby release 10.10.1.1 introduces the following new features and incompatibilities. These merit your special attention.</p>
@@ -1634,7 +1635,7 @@ where T.A = S.A;
 <p>In environments where the server version and the client driver version differ, and the return value from <span class="codefrag">SQLException.getErrorCode()</span> has significance for the application, it is recommended to upgrade both the client driver and the server to version 10.10 or higher.</p>
 </div>
 </div>
-<a name="N107E2"></a><a name="Build+Environment"></a>
+<a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <div>
 <p>Derby release 10.10.1.1 was built using the following environment:</p>
@@ -1651,7 +1652,7 @@ where T.A = S.A;
 <strong>JSR 169</strong> - Java ME support was built using libraries from phoneME Advanced Milestone Release 2.</li>
 </ul>
 </div>
-<a name="N10800"></a><a name="Verifying+Releases"></a>
+<a name="Verifying+Releases"></a>
 <h3 class="boxed">Verifying Releases</h3>
 <div>
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>

Modified: websites/production/db/content/derby/releases/release-10.10.2.0.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.10.2.0.html (original)
+++ websites/production/db/content/derby/releases/release-10.10.2.0.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.10.2.0 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.10.2.0 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -518,7 +518,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="Distributions"></a>
+</div>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby. You should <strong>always</strong> <a href="#Verifying Releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -542,13 +543,13 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.2.0/db-derby-10.10.2.0-src.zip">db-derby-10.10.2.0-src.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.2.0/db-derby-10.10.2.0-src.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.2.0/db-derby-10.10.2.0-src.zip.md5">MD5</a>]<br>
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.2.0/db-derby-10.10.2.0-src.tar.gz">db-derby-10.10.2.0-src.tar.gz</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.2.0/db-derby-10.10.2.0-src.tar.gz.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.10.2.0/db-derby-10.10.2.0-src.tar.gz.md5">MD5</a>] (Note that, due to long filenames, you will need gnu tar to unravel this tarball.)</p>
 </div>
-<a name="N10094"></a><a name="Release Notes for Apache Derby 10.10.2.0"></a>
+<a name="Release Notes for Apache Derby 10.10.2.0"></a>
 <h2 class="boxed">Release Notes for Apache Derby 10.10.2.0</h2>
 <div class="section">
 <div>
 <p>These notes describe the difference between Apache Derby release 10.10.2.0 and the preceding release 10.10.1.1.</p>
 </div>
-<a name="N1009D"></a><a name="Overview"></a>
+<a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <div>
 <p>The most up to date information about Derby releases can be found on the <a href="http://db.apache.org/derby/derby_downloads.html">Derby download page</a>.</p>
@@ -565,12 +566,12 @@ document.write("Last Published: " + docu
 <li>Java ME CDC/Foundation Profile 1.1 with JSR-169 JDBC Optional Package for CDC/Foundation Profile.</li>
 </ul>
 </div>
-<a name="N100C0"></a><a name="New+Features"></a>
+<a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <div>
 <p>This is a bug fix release. There are no new features:</p>
 </div>
-<a name="N100C9"></a><a name="Issues+of+special+concern"></a>
+<a name="Issues+of+special+concern"></a>
 <h3 class="boxed">Issues of special concern</h3>
 <div>
 <p>Compared with the previous release (10.10.1.1), Derby release 10.10.2.0 introduces the following incompatibilities. These merit your special attention.</p>
@@ -989,7 +990,7 @@ document.write("Last Published: " + docu
 <p>Most applications should not be affected by this change in any way. Any applications that read the values stored in <tt>SYS.SYSTRIGGERS.CREATIONTIMESTAMP</tt> should take into account that this column doesn't necessarily tell the exact time the trigger was created, because it contains a value that may have been adjusted in order to ensure the correct execution order.</p>
 </div>
 </div>
-<a name="N10261"></a><a name="Bug+Fixes"></a>
+<a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <div>
 <p>The following issues are addressed by Derby release 10.10.2.0. These issues are not addressed in the preceding 10.10.1.1 release.</p>
@@ -1208,7 +1209,7 @@ document.write("Last Published: " + docu
 </tr>
 </table>
 </div>
-<a name="N10456"></a><a name="Fixes+in+the+Documentation"></a>
+<a name="Fixes+in+the+Documentation"></a>
 <h3 class="boxed">Fixes in the Documentation</h3>
 <div>
 <p>The following issues are addressed by Derby release 10.10.1.4. These issues are not addressed in the preceding 10.10.1.1 release.</p>
@@ -1322,7 +1323,7 @@ document.write("Last Published: " + docu
 </tr>
 </table>
 </div>
-<a name="N10556"></a><a name="Build+Environment"></a>
+<a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <div>
 <p>Derby release 10.10.2.0 was built using the following environment:</p>
@@ -1339,7 +1340,7 @@ document.write("Last Published: " + docu
 <strong>JSR 169</strong> - Java ME support was built using libraries from IBMs weme 6.2.</li>
 </ul>
 </div>
-<a name="N10574"></a><a name="Verifying+Releases"></a>
+<a name="Verifying+Releases"></a>
 <h3 class="boxed">Verifying Releases</h3>
 <div>
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>

Modified: websites/production/db/content/derby/releases/release-10.2.1.6.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.2.1.6.html (original)
+++ websites/production/db/content/derby/releases/release-10.2.1.6.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.2.1.6 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.2.1.6 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -512,43 +512,43 @@ document.write("Last Published: " + docu
 <a href="#">DERBY-253</a>
 </li>
 <li>
-<a href="#-N10744">DERBY-668</a>
+<a href="#-N1073B">DERBY-668</a>
 </li>
 <li>
-<a href="#-N10764">DERBY-721</a>
+<a href="#-N1075B">DERBY-721</a>
 </li>
 <li>
-<a href="#-N10784">DERBY-781</a>
+<a href="#-N1077B">DERBY-781</a>
 </li>
 <li>
-<a href="#-N107AE">DERBY-822</a>
+<a href="#-N107A5">DERBY-822</a>
 </li>
 <li>
-<a href="#-N107CE">DERBY-1130</a>
+<a href="#-N107C5">DERBY-1130</a>
 </li>
 <li>
-<a href="#-N107F3">DERBY-1295</a>
+<a href="#-N107EA">DERBY-1295</a>
 </li>
 <li>
-<a href="#-N10813">DERBY-1314</a>
+<a href="#-N1080A">DERBY-1314</a>
 </li>
 <li>
-<a href="#-N10838">DERBY-1323</a>
+<a href="#-N1082F">DERBY-1323</a>
 </li>
 <li>
-<a href="#-N10858">DERBY-1357</a>
+<a href="#-N1084F">DERBY-1357</a>
 </li>
 <li>
-<a href="#-N10880">DERBY-1384</a>
+<a href="#-N10877">DERBY-1384</a>
 </li>
 <li>
-<a href="#-N108A0">DERBY-1621</a>
+<a href="#-N10897">DERBY-1621</a>
 </li>
 <li>
-<a href="#-N108D0">DERBY-1652</a>
+<a href="#-N108C7">DERBY-1652</a>
 </li>
 <li>
-<a href="#-N108FE">DERBY-1867</a>
+<a href="#-N108F5">DERBY-1867</a>
 </li>
 </ul>
 </li>
@@ -563,7 +563,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="Distributions"></a>
+</div>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby from the archives. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -596,7 +597,7 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.2.1.6/derby_ui_plugin_1.1.0.zip">derby_ui_plugin_1.1.0.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.2.1.6/derby_ui_plugin_1.1.0.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.2.1.6/derby_ui_plugin_1.1.0.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using the 10.2 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N100BC"></a><a name="Release Overview"></a>
+<a name="Release Overview"></a>
 <h2 class="boxed">Release Overview</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.2.1.6 and the preceding release 10.1.3.1.</p>
@@ -689,7 +690,7 @@ document.write("Last Published: " + docu
 <li>JSR-169, JDBC 2.1, and JDBC 3.0 support</li>
 </ul>
 </div>
-<a name="N10177"></a><a name="JDBC 4.0 Support"></a>
+<a name="JDBC 4.0 Support"></a>
 <h2 class="boxed">JDBC 4.0 Support</h2>
 <div class="section">
 <p>Derby 10.2.1.6 comes with source code for drivers which conform to a beta version of the JDBC standard, JDBC 4.0. This source code conforms to the following state of the JDBC 4.0 specification:</p>
@@ -701,7 +702,7 @@ document.write("Last Published: " + docu
 <p>Due to license restrictions on the beta builds of JDK 6, Derby 10.2.1.6 does not contain compiled versions of JDBC 4.0 drivers. When run on Java SE 6, Derby 10.2.1.6 exposes the same JDBC 3.0 implementation seen when run on JDK 1.4 and 1.5. You may, however, compile Derby's JDBC 4.0 support yourself. This will let you use JDBC 4.0 features when you run Derby 10.2.1.6 on Java SE 6.</p>
 <p>To build this optional JDBC 4.0 support yourself, please download the source distribution and consult BUILDING.txt. You may also follow a simplified set of instructions for building JDBC 4.0 support, which you may find in the "Building the Optional JDBC4 Support" section of the <a class="external" href="http://wiki.apache.org/db-derby/TenTwoRelease">Derby 10.2 wiki page</a>.</p>
 </div>
-<a name="N10193"></a><a name="XML Support"></a>
+<a name="XML Support"></a>
 <h2 class="boxed">XML Support</h2>
 <div class="section">
 <p>If you intend to use any of the Derby XML operators, you must ensure that you have:</p>
@@ -711,7 +712,7 @@ document.write("Last Published: " + docu
 </ul>
 <p>Apache Derby 10.2.1.6 has been tested with Xalan-Java Version 2.7.0. If you have a version of Xalan that is earlier than 2.7, the Derby XML operators may still work. However, it is possible that you will experience unexpected errors when using the Derby XML operators. </p>
 </div>
-<a name="N101A2"></a><a name="New Features"></a>
+<a name="New Features"></a>
 <h2 class="boxed">New Features</h2>
 <div class="section">
 <p>These features appear in Derby 10.2.1.6 but not in the preceding release 10.1.3.1.</p>
@@ -807,7 +808,7 @@ document.write("Last Published: " + docu
 </tbody>
 </table>
 </div>
-<a name="N10278"></a><a name="Bug Fixes"></a>
+<a name="Bug Fixes"></a>
 <h2 class="boxed">Bug Fixes</h2>
 <div class="section">
 <p>List the bugs fixed by this release. These are bug fixes which turn up in Derby 10.2.1.6 but not in the preceding 10.1.3.1 release.</p>
@@ -1320,12 +1321,12 @@ document.write("Last Published: " + docu
 </tbody>
 </table>
 </div>
-<a name="N1071B"></a><a name="Issues"></a>
+<a name="Issues"></a>
 <h2 class="boxed">Issues</h2>
 <div class="section">
 <p>Please be aware of the following issues:</p>
 <hr>
-<a name="N10724"></a>
+<a name="N1071C"></a>
 <h3 class="boxed">DERBY-253</h3>
 <p>
 <strong>Problem</strong>
@@ -1348,7 +1349,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Use setCharacterStream() and getCharacterStream() instead of setUnicodeStream() and getUnicodeStream().</p>
 <hr>
-<a name="N10744"></a><a name="-N10744"></a>
+<a name="-N1073B"></a>
 <h3 class="boxed">DERBY-668</h3>
 <p>
 <strong>Problem</strong>
@@ -1371,7 +1372,7 @@ document.write("Last Published: " + docu
 </p>
 <p>No workaround. The behavior is now correct.</p>
 <hr>
-<a name="N10764"></a><a name="-N10764"></a>
+<a name="-N1075B"></a>
 <h3 class="boxed">DERBY-721</h3>
 <p>
 <strong>Problem</strong>
@@ -1394,7 +1395,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Users must recode Applications which open multiple streams on the same column.</p>
 <hr>
-<a name="N10784"></a><a name="-N10784"></a>
+<a name="-N1077B"></a>
 <h3 class="boxed">DERBY-781</h3>
 <p>
 <strong>Problem</strong>
@@ -1420,7 +1421,7 @@ document.write("Last Published: " + docu
 <p>There is no way to disable/workaround this new behavior since the symptom as described above is a good one for Derby.</p>
 <p>That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer enhancement, is encouraged to visit the <a class="external" href="http://wiki.apache.org/db-derby/PerformanceDiagnosisTips">performance diagnosis page</a> and to follow up with his/her findings on the Derby mailing lists.</p>
 <hr>
-<a name="N107AE"></a><a name="-N107AE"></a>
+<a name="-N107A5"></a>
 <h3 class="boxed">DERBY-822</h3>
 <p>
 <strong>Problem</strong>
@@ -1443,7 +1444,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Application code needs to be changed to adjust error handling if needed.</p>
 <hr>
-<a name="N107CE"></a><a name="-N107CE"></a>
+<a name="-N107C5"></a>
 <h3 class="boxed">DERBY-1130</h3>
 <p>
 <strong>Problem</strong>
@@ -1470,7 +1471,7 @@ document.write("Last Published: " + docu
 </p>
 <p>If using release prior to version 10.2, make sure database name is set only as a DataSource property when using Derby's client DataSources.</p>
 <hr>
-<a name="N107F3"></a><a name="-N107F3"></a>
+<a name="-N107EA"></a>
 <h3 class="boxed">DERBY-1295</h3>
 <p>
 <strong>Problem</strong>
@@ -1493,7 +1494,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Fix applications which rely on the previous, non-standard behavior.</p>
 <hr>
-<a name="N10813"></a><a name="-N10813"></a>
+<a name="-N1080A"></a>
 <h3 class="boxed">DERBY-1314</h3>
 <p>
 <strong>Problem</strong>
@@ -1520,7 +1521,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Use execute() instead of executeUpdate()/executeQuery() to invoke a stored procedure which does not return exactly 0 or 1 ResultSet objects.</p>
 <hr>
-<a name="N10838"></a><a name="-N10838"></a>
+<a name="-N1082F"></a>
 <h3 class="boxed">DERBY-1323</h3>
 <p>
 <strong>Problem</strong>
@@ -1543,7 +1544,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Fix applications which rely on this non-standard behavior.</p>
 <hr>
-<a name="N10858"></a><a name="-N10858"></a>
+<a name="-N1084F"></a>
 <h3 class="boxed">DERBY-1357</h3>
 <p>
 <strong>Problem</strong>
@@ -1568,7 +1569,7 @@ document.write("Last Published: " + docu
 <p>There is no way to disable/workaround this new behavior since the symptom as described above is a good one for Derby.</p>
 <p>That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer change, is encouraged to visit the <a class="external" href="http://wiki.apache.org/db-derby/PerformanceDiagnosisTips">performance diagnosis page</a> and to follow up with his/her findings on the Derby mailing lists.</p>
 <hr>
-<a name="N10880"></a><a name="-N10880"></a>
+<a name="-N10877"></a>
 <h3 class="boxed">DERBY-1384</h3>
 <p>
 <strong>Problem</strong>
@@ -1591,7 +1592,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Fix applications which rely on Derby rejecting LOBs that are bigger than 1M.</p>
 <hr>
-<a name="N108A0"></a><a name="-N108A0"></a>
+<a name="-N10897"></a>
 <h3 class="boxed">DERBY-1621</h3>
 <p>
 <strong>Problem</strong>
@@ -1654,7 +1655,7 @@ document.write("Last Published: " + docu
 </p>
 <p>None.</p>
 <hr>
-<a name="N108D0"></a><a name="-N108D0"></a>
+<a name="-N108C7"></a>
 <h3 class="boxed">DERBY-1652</h3>
 <p>
 <strong>Problem</strong>
@@ -1705,7 +1706,7 @@ document.write("Last Published: " + docu
 </pre>
 <p>In the above statement, the trigger will only fire when an update is made to the "info" column instead of any column(s).</p>
 <hr>
-<a name="N108FE"></a><a name="-N108FE"></a>
+<a name="-N108F5"></a>
 <h3 class="boxed">DERBY-1867</h3>
 <p>
 <strong>Problem</strong>
@@ -1728,7 +1729,7 @@ document.write("Last Published: " + docu
 </p>
 <p>If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is available in the JCE provider that is available with a particular JVM. For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.</p>
 </div>
-<a name="N1091D"></a><a name="Build Environment"></a>
+<a name="Build Environment"></a>
 <h2 class="boxed">Build Environment</h2>
 <div class="section">
 <p>Derby release 10.2.1.6 was built using the following environment:</p>
@@ -1753,7 +1754,7 @@ document.write("Last Published: " + docu
 <strong>JSR 169</strong> - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).</li>
 </ul>
 </div>
-<a name="N1094A"></a><a name="Testing"></a>
+<a name="Testing"></a>
 <h2 class="boxed">Testing</h2>
 <div class="section">
 <p>Tests were run on the following platforms. Results are listed separately for each platform.</p>
@@ -1883,7 +1884,7 @@ document.write("Last Published: " + docu
 <p>Tests for a specific platform can be run using the derbyTesting.jar file that can be found in the lib directory of the -lib or -bin distributions.</p>
 <p>Instructions on how to run the tests can be found in the <a class="external" href="http://svn.apache.org/repos/asf/db/derby/code/branches/10.2/java/testing/README.htm">testing README</a>.</p>
 </div>
-<a name="N10A73"></a><a name="Verifying+releases"></a>
+<a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>

Modified: websites/production/db/content/derby/releases/release-10.2.2.0.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.2.2.0.html (original)
+++ websites/production/db/content/derby/releases/release-10.2.2.0.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.2.2.0 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.2.2.0 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -554,7 +554,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="Distributions"></a>
+</div>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby from one of our mirrors. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -587,7 +588,7 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.2.2.0/derby_ui_plugin_1.1.0.zip">derby_ui_plugin_1.1.0.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.2.2.0/derby_ui_plugin_1.1.0.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.2.2.0/derby_ui_plugin_1.1.0.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using the 10.2 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N100BC"></a><a name="Release Overview"></a>
+<a name="Release Overview"></a>
 <h2 class="boxed">Release Overview</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.2.2.0 and the preceding release, 10.2.1.6. 10.2.2.0 is a bug-fix release. It includes compiled versions of Derby's JDBC4 drivers, which appeared in the previous release only as source code. In addition, 10.2.2.0 includes a number of <a href="#Bug Fixes">bug fixes</a> not found in the previous release. No new features appear in 10.2.2.0.</p>
@@ -626,12 +627,12 @@ document.write("Last Published: " + docu
 <li>JSR-169, JDBC 2.1, JDBC 3.0, and JDBC 4.0 support</li>
 </ul>
 </div>
-<a name="N10100"></a><a name="New Features"></a>
+<a name="New Features"></a>
 <h2 class="boxed">New Features</h2>
 <div class="section">
 <p>Release 10.2.2.0 is a bug-fix release. No new features were added since 10.2.1.6.</p>
 </div>
-<a name="N10108"></a><a name="Bug Fixes"></a>
+<a name="Bug Fixes"></a>
 <h2 class="boxed">Bug Fixes</h2>
 <div class="section">
 <p>The following bug fixes turn up in Derby 10.2.2.0 but not in the preceding 10.2.1.6 release.</p>
@@ -712,12 +713,12 @@ document.write("Last Published: " + docu
 </tbody>
 </table>
 </div>
-<a name="N101BB"></a><a name="Issues"></a>
+<a name="Issues"></a>
 <h2 class="boxed">Issues</h2>
 <div class="section">
 <p>Applications which run against Derby 10.0 or 10.1 may rely on incorrect Derby behavior. After upgrading to 10.2, those applications may need some recoding so that they no longer rely on bad behavior which has been fixed. Please consult the following list of issues which may require some application recoding. Note that 10.2.2.0 does not introduce any additional issues beyond the issues introduced by 10.2.1.6:</p>
 <hr>
-<a name="N101C4"></a><a name="DERBY-253"></a>
+<a name="DERBY-253"></a>
 <h3 class="boxed">DERBY-253</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-253">DERBY-253</a>.</p>
 <p>
@@ -741,7 +742,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Use setCharacterStream() and getCharacterStream() instead of setUnicodeStream() and getUnicodeStream().</p>
 <hr>
-<a name="N101E8"></a><a name="DERBY-668"></a>
+<a name="DERBY-668"></a>
 <h3 class="boxed">DERBY-668</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-668">DERBY-668</a>.</p>
 <p>
@@ -765,7 +766,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Grant these permissions so that sysinfo can run correctly under the Java security manager.</p>
 <hr>
-<a name="N1020C"></a><a name="DERBY-721"></a>
+<a name="DERBY-721"></a>
 <h3 class="boxed">DERBY-721</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-721">DERBY-721</a>.</p>
 <p>
@@ -789,7 +790,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Users must recode Applications which open multiple streams on the same column.</p>
 <hr>
-<a name="N10230"></a><a name="DERBY-781"></a>
+<a name="DERBY-781"></a>
 <h3 class="boxed">DERBY-781</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-781">DERBY-781</a>.</p>
 <p>
@@ -816,7 +817,7 @@ document.write("Last Published: " + docu
 <p>There is no way to disable/workaround this new behavior. The increased compilation time buys better performance at query execution time.</p>
 <p>That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer enhancement, is encouraged to visit the <a class="external" href="http://wiki.apache.org/db-derby/PerformanceDiagnosisTips">performance diagnosis page</a> and to follow up with his/her findings on the Derby mailing lists.</p>
 <hr>
-<a name="N1025E"></a><a name="DERBY-822"></a>
+<a name="DERBY-822"></a>
 <h3 class="boxed">DERBY-822</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-822">DERBY-822</a>.</p>
 <p>
@@ -840,7 +841,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Application code needs to be changed to adjust error handling if needed.</p>
 <hr>
-<a name="N10282"></a><a name="DERBY-1130"></a>
+<a name="DERBY-1130"></a>
 <h3 class="boxed">DERBY-1130</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1130">DERBY-1130</a>.</p>
 <p>
@@ -868,7 +869,7 @@ document.write("Last Published: " + docu
 </p>
 <p>When upgrading an application to run against Derby 10.2, make sure the database name is set only as a DataSource property when using Derby's client DataSources.</p>
 <hr>
-<a name="N102AB"></a><a name="DERBY-1295"></a>
+<a name="DERBY-1295"></a>
 <h3 class="boxed">DERBY-1295</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1295">DERBY-1295</a>.</p>
 <p>
@@ -892,7 +893,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Fix applications which rely on the previous, non-standard behavior.</p>
 <hr>
-<a name="N102CF"></a><a name="DERBY-1314"></a>
+<a name="DERBY-1314"></a>
 <h3 class="boxed">DERBY-1314</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1314">DERBY-1314</a>.</p>
 <p>
@@ -921,7 +922,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Use execute() instead of executeUpdate()/executeQuery() to invoke a stored procedure which does not return exactly 0 or 1 ResultSet objects.</p>
 <hr>
-<a name="N102FA"></a><a name="DERBY-1323"></a>
+<a name="DERBY-1323"></a>
 <h3 class="boxed">DERBY-1323</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1323">DERBY-1323</a>.</p>
 <p>
@@ -946,7 +947,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Fix applications which rely on this non-standard behavior.</p>
 <hr>
-<a name="N10320"></a><a name="DERBY-1357"></a>
+<a name="DERBY-1357"></a>
 <h3 class="boxed">DERBY-1357</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1357">DERBY-1357</a>.</p>
 <p>
@@ -970,7 +971,7 @@ document.write("Last Published: " + docu
 </p>
 <p>In general, the performance of these queries should stay the same or improve. However, it is possible that performance may degrade for some queries. Any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer change, is encouraged to visit the <a class="external" href="http://wiki.apache.org/db-derby/PerformanceDiagnosisTips">performance diagnosis page</a> and to follow up with his/her findings on the Derby mailing lists.</p>
 <hr>
-<a name="N10348"></a><a name="DERBY-1384"></a>
+<a name="DERBY-1384"></a>
 <h3 class="boxed">DERBY-1384</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1384">DERBY-1384</a>.</p>
 <p>
@@ -994,7 +995,7 @@ document.write("Last Published: " + docu
 </p>
 <p>Fix applications which rely on Derby rejecting LOBs that are bigger than 1M.</p>
 <hr>
-<a name="N1036C"></a><a name="DERBY-1652"></a>
+<a name="DERBY-1652"></a>
 <h3 class="boxed">DERBY-1652</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1652">DERBY-1652</a>.</p>
 <p>
@@ -1047,7 +1048,7 @@ document.write("Last Published: " + docu
 </pre>
 <p>In the above statement, the trigger will only fire when an update is made to the "info" column instead of any column(s).</p>
 <hr>
-<a name="N103A0"></a><a name="DERBY-1867"></a>
+<a name="DERBY-1867"></a>
 <h3 class="boxed">DERBY-1867</h3>
 <p>See <a class="external" href="http://issues.apache.org/jira/browse/DERBY-1867">DERBY-1867</a>.</p>
 <p>
@@ -1071,7 +1072,7 @@ document.write("Last Published: " + docu
 </p>
 <p>If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is available in the JCE provider that is available with a particular JVM. For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.</p>
 </div>
-<a name="N103C3"></a><a name="Build Environment"></a>
+<a name="Build Environment"></a>
 <h2 class="boxed">Build Environment</h2>
 <div class="section">
 <p>Derby release 10.2.2.0 was built using the following environment:</p>
@@ -1096,7 +1097,7 @@ document.write("Last Published: " + docu
 <strong>JSR 169</strong> - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).</li>
 </ul>
 </div>
-<a name="N103F0"></a><a name="Testing"></a>
+<a name="Testing"></a>
 <h2 class="boxed">Testing</h2>
 <div class="section">
 <p>Tests were run on the following platforms. Results are listed separately for each platform.</p>
@@ -1182,7 +1183,7 @@ document.write("Last Published: " + docu
 <p>Tests for a specific platform can be run using the derbyTesting.jar file that can be found in the lib directory of the -lib or -bin distributions.</p>
 <p>Instructions on how to run the tests can be found in the <a class="external" href="http://svn.apache.org/repos/asf/db/derby/code/branches/10.2/java/testing/README.htm">testing README</a>.</p>
 </div>
-<a name="N104CC"></a><a name="Verifying+releases"></a>
+<a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>

Modified: websites/production/db/content/derby/releases/release-10.3.3.0.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.3.3.0.html (original)
+++ websites/production/db/content/derby/releases/release-10.3.3.0.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.3.3.0 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.3.3.0 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -523,7 +523,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="IMPORTANT+NOTICE"></a>
+</div>
+<a name="IMPORTANT+NOTICE"></a>
 <h2 class="boxed">IMPORTANT NOTICE</h2>
 <div class="section">
 <p>If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly<br> recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid<br> any chance of database corruption due to an issue with multiple threads<br> accessing a database that is documented in <a class="external" href="http://issues.apache.org/jira/browse/DERBY-3347">DERBY-3347</a>.<br>
@@ -547,7 +548,7 @@ document.write("Last Published: " + docu
 <br> http://db.apache.org/derby/derby_mail.html<br>
 </p>
 </div>
-<a name="N10076"></a><a name="Distributions"></a>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby from one of our mirrors. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -580,7 +581,7 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.3.3.0/derby_ui_plugin_1.1.1.zip">derby_ui_plugin_1.1.1.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.3.3.0/derby_ui_plugin_1.1.1.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.3.3.0/derby_ui_plugin_1.1.1.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using the 10 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N10122"></a><a name="Release Notes for Derby 10.3.3.0"></a>
+<a name="Release Notes for Derby 10.3.3.0"></a>
 <h2 class="boxed">Release Notes for Derby 10.3.3.0</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.3.3.0 and the preceding release 10.3.2.1.</p>
@@ -598,7 +599,7 @@ document.write("Last Published: " + docu
 <a href="#Build Environment">Build Environment</a>
 </li>
 </ul>
-<a name="N1013B"></a><a name="Overview"></a>
+<a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs.</p>
 <p>Derby functionality includes:</p>
@@ -608,7 +609,7 @@ document.write("Last Published: " + docu
 <li>Network client JDBC drivers</li>
 <li>Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)</li>
 </ul>
-<a name="N1014E"></a><a name="Issues"></a>
+<a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <p>The following issues are addressed by Derby release 10.3.3.0. These issues are not addressed in the preceding 10.3.2.1 release.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4" border="2">
@@ -806,12 +807,12 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 <hr>
-<a name="N10308"></a><a name="Note+for+DERBY-3347"></a>
+<a name="Note+for+DERBY-3347"></a>
 <h4>Note for DERBY-3347</h4>
-<a name="N1030E"></a><a name="Summary+of+Change"></a>
+<a name="Summary+of+Change"></a>
 <h5>Summary of Change</h5>
 <p>A bug that could cause unrecoverable database corruption has been fixed.</p>
-<a name="N10314"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>A bug that could cause database corruption was introduced in the 10.3 codeline and affects the following releases:</p>
 <ul>
@@ -825,42 +826,42 @@ ERROR XSDG2: Invalid checksum on Page Pa
 ERROR XSDG3: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@1afb0c7 could not be accessed
 ERROR XSLA1: Log Record has been sent to the stream, but it cannot be applied to the store (Object null). This may cause recovery problems also.
 </pre>
-<a name="N10323"></a><a name="Incompatibilities+with+Previous+Release"></a>
+<a name="Incompatibilities+with+Previous+Release"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None.</p>
-<a name="N10329"></a><a name="Rationale+for+Change"></a>
+<a name="Rationale+for+Change"></a>
 <h5>Rationale for Change</h5>
 <p>Database corruption is bad.</p>
-<a name="N1032F"></a><a name="Application+Changes+Required"></a>
+<a name="Application+Changes+Required"></a>
 <h5>Application Changes Required</h5>
 <p>No changes are required. However, since the database corruption may go unnoticed for a while, users may want to check the consistency of their databases after upgrading Derby. The process is described on the following wiki page: <a class="external" href="http://wiki.apache.org/db-derby/DatabaseConsistencyCheck">http://wiki.apache.org/db-derby/DatabaseConsistencyCheck</a> . If a corruption is detected, restoring the database from backup is the only reliable way to recover.</p>
 <hr>
-<a name="N1033A"></a><a name="Note+for+DERBY-3301"></a>
+<a name="Note+for+DERBY-3301"></a>
 <h4>Note for DERBY-3301</h4>
-<a name="N10340"></a><a name="Summary+of+Change-N10340"></a>
+<a name="Summary+of+Change-N10337"></a>
 <h5>Summary of Change</h5>
 <p>Queries with nested EXIST, ANY or IN clauses now return correct results.</p>
-<a name="N10346"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10346"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1033D"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, applications that executed SQL statements containing nested EXISTS, ANY or IN clauses could see fewer rows than those satisfying the query. In particular, rows that had the same value for one of the selected columns as another row might not have been returned.</p>
-<a name="N1034C"></a><a name="Incompatibilities+with+Previous+Release-N1034C"></a>
+<a name="Incompatibilities+with+Previous+Release-N10343"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None.</p>
-<a name="N10352"></a><a name="Rationale+for+Change-N10352"></a>
+<a name="Rationale+for+Change-N10349"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behavior violated the ANSI SQL standard. The new behavior is correct.</p>
-<a name="N10358"></a><a name="Application+Changes+Required-N10358"></a>
+<a name="Application+Changes+Required-N1034F"></a>
 <h5>Application Changes Required</h5>
 <p>Typically none, but applications must handle that the correct results are now returned.</p>
 <hr>
-<a name="N1035F"></a><a name="Note+for+DERBY-2351"></a>
+<a name="Note+for+DERBY-2351"></a>
 <h4>Note for DERBY-2351</h4>
-<a name="N10365"></a><a name="Summary+of+Change-N10365"></a>
+<a name="Summary+of+Change-N1035C"></a>
 <h5>Summary of Change</h5>
 <p>An ORDER BY clause of a DISTINCT query which specifies to order by a column which was not in the DISTINCT list is now rejected, because the intent of the query is ambiguous. Previously, Derby instead produced non-distinct results. Also, an ORDER BY clause which specifies a table-name-qualified column alias is now rejected as invalid, where previously it was accepted.</p>
-<a name="N1036B"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1036B"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10362"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N1036F"></a><a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
+<a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
 <h5>New rules for DISTINCT and ORDER BY</h5>
 <p>Applications which specify certain combinations of SELECT DISTINCT with ORDER BY will now receive an error message, whereas formerly such applications received non-distinct results.</p>
 <p>As an example, take the following:</p>
@@ -869,7 +870,7 @@ ERROR XSLA1: Log Record has been sent to
 </p>
 <p>The query above is now rejected, with the error message:</p>
 <p>If the AGE column is included in the DISTINCT list in the above query, there is no ambiguity</p>
-<a name="N10387"></a><a name="New+column+alias+rules"></a>
+<a name="New+column+alias+rules"></a>
 <h5>New column alias rules</h5>
 <p>Applications which specify a column alias for a column in the SELECT statement, and which specify an ORDER BY clause which specifies that column alias qualified by the table name, will now receive an error indicating that the ORDER BY clause is invalid.</p>
 <p>As an example, take the following:</p>
@@ -879,7 +880,7 @@ ERROR XSLA1: Log Record has been sent to
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by idcolumn1, idcolumn2;</p>
 <p>or</p>
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.id, t1.id;</p>
-<a name="N1039D"></a><a name="Rationale+for+Change-N1039D"></a>
+<a name="Rationale+for+Change-N10394"></a>
 <h5>Rationale for Change</h5>
 <p>When the query ambiguously specifies both DISTINCT and ORDER BY, Derby was unsure whether to return the rows properly ordered, but non-distinct, or to return a distinct set of rows, but in an unknown order. Since no clear resolution of the ambiguity could be found, we chose instead to reject the query.</p>
 <p>The rules for resolving column references in ORDER BY clauses have been enhanced to consider column aliases and column names more fully. Derby now uses different resolution rules depending on whether the ORDER BY column reference is table.column, or just column:</p>
@@ -889,11 +890,11 @@ ERROR XSLA1: Log Record has been sent to
 </ul>
 <br>
 <br>
-<a name="N103AC"></a><a name="Application+Changes+Required-N103AC"></a>
+<a name="Application+Changes+Required-N103A3"></a>
 <h5>Application Changes Required</h5>
 <p>A query which specifies ordering by a non-distinct column should instead include the ORDER BY column in the DISTINCT list, to resolve the ambiguity about which values of that column should be used to distinctly identify the resulting rows.</p>
 <p>A query which specifies table-name.alias-name should be rewritten to specify either simply alias-name, or table-name.column-name.</p>
-<a name="N103B4"></a><a name="Build+Environment"></a>
+<a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <p>Derby release 10.3.3.0 was built using the following environment:</p>
 <ul>
@@ -915,7 +916,7 @@ ERROR XSLA1: Log Record has been sent to
 <strong>JSR 169</strong> - Java ME support was built using Java ME CDC/Foundation Specification 1.1 libraries from IBM WebSphere Everyplace Micro Environment 6.1</li>
 </ul>
 </div>
-<a name="N103DD"></a><a name="Verifying+releases"></a>
+<a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>

Modified: websites/production/db/content/derby/releases/release-10.4.1.3.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.4.1.3.html (original)
+++ websites/production/db/content/derby/releases/release-10.4.1.3.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.4.1.3 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.4.1.3 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -538,7 +538,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="Distributions"></a>
+</div>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby from one of our mirrors. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -571,11 +572,11 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.4.1.3/derby_ui_plugin_1.1.2.zip">derby_ui_plugin_1.1.2.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.4.1.3/derby_ui_plugin_1.1.2.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.4.1.3/derby_ui_plugin_1.1.2.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using the 10 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N100BC"></a><a name="Release Notes for Derby 10.4.1.3"></a>
+<a name="Release Notes for Derby 10.4.1.3"></a>
 <h2 class="boxed">Release Notes for Derby 10.4.1.3</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.4.1.3 and the preceding release 10.3.2.1.</p>
-<a name="N100C4"></a><a name="Overview"></a>
+<a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs.</p>
 <p>Derby functionality includes:</p>
@@ -585,7 +586,7 @@ document.write("Last Published: " + docu
 <li>Network client JDBC drivers</li>
 <li>Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)</li>
 </ul>
-<a name="N100D7"></a><a name="New+Features"></a>
+<a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <p>This is a feature release. The following new features were added:</p>
 <ul>
@@ -600,7 +601,7 @@ document.write("Last Published: " + docu
 <li>Caching of the isolation level and the current schema in the client driver.</li>
 <li>Implement a new multi-threaded buffer manager to get better scalability on machines with multiple CPUs or multiple cores.</li>
 </ul>
-<a name="N100F7"></a><a name="Bug+Fixes"></a>
+<a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <p>The following issues are addressed by Derby release 10.4.1.3. These issues are not addressed in the preceding 10.3.2.1 release.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4" border="2">
@@ -821,7 +822,7 @@ document.write("Last Published: " + docu
 <td><a class="external" href="http://issues.apache.org/jira/browse/DERBY-1573">DERBY-1573</a></td><td>Unsafe synchronization in NetworkServerControlImpl</td>
 </tr>
 </table>
-<a name="N102F9"></a><a name="Issues"></a>
+<a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <p>Compared with the previous release (10.3.2.1), Derby release 10.4.1.3 introduces the following new features and incompatibilities. These merit your special attention.</p>
 <ul>
@@ -855,12 +856,12 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 <hr>
-<a name="N1032F"></a><a name="Note+for+DERBY-3585"></a>
+<a name="Note+for+DERBY-3585"></a>
 <h4>Note for DERBY-3585</h4>
-<a name="N10335"></a><a name="Summary+of+Change"></a>
+<a name="Summary+of+Change"></a>
 <h5>Summary of Change</h5>
 <p>Shutting down the Network Server now supports user authentication, and in fact requires credentials when authentication is enabled.</p>
-<a name="N1033B"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Previously, a network server running with user authentication didn't check for user credentials for server shutdown. Any client could shut down the server by calling NetworkServerControl with a shutdown command-line argument or by invoking the shutdown() method (provided the shutdown was initiated on the host running the server). While this generated a console warning (Connection refused : Invalid authentication.), the server shutdown proceeded and could also result in open databases not being properly closed.</p>
 <p>Now, class NetworkServerControl supports user and password information as command-line and constructor arguments. When running a network server with user authentication, a server shutdown now requires user credentials; if the user authentication check fails, the client sees an authentication error and the running server remains intact. Note that Derby does not yet restrict the shutdown privilege to specific users: the server can be shut down by any user on the server machine who presents valid credentials.</p>
@@ -875,7 +876,7 @@ document.write("Last Published: " + docu
 </ul>
 <br>
 <br>
-<a name="N10351"></a><a name="Incompatibilities+with+Previous+Release"></a>
+<a name="Incompatibilities+with+Previous+Release"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>If running a network server without user authentication (the default) no command-line or API incompatibilities will be experienced.</p>
 <p>However, some incompatibilities were introduced if running a network server with user authentication:</p>
@@ -892,90 +893,90 @@ document.write("Last Published: " + docu
 </ol>
 <br>
 <br>
-<a name="N10394"></a><a name="Rationale+for+Change"></a>
+<a name="Rationale+for+Change"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behavior represented a security issue, because any client could shut down a network server running with user authentication from the same host without needing to provide user credentials.</p>
-<a name="N1039A"></a><a name="Application+Changes+Required"></a>
+<a name="Application+Changes+Required"></a>
 <h5>Application Changes Required</h5>
 <p>Application code and scripts will need to be adjusted to provide user credentials for shutting down a network server that runs with user authentication.</p>
 <hr>
-<a name="N103A1"></a><a name="Note+for+DERBY-3460"></a>
+<a name="Note+for+DERBY-3460"></a>
 <h4>Note for DERBY-3460</h4>
-<a name="N103A7"></a><a name="Summary+of+Change-N103A7"></a>
+<a name="Summary+of+Change-N1039E"></a>
 <h5>Summary of Change</h5>
 <p>The two following reserved keywords are introduced: <span class="codefrag">NONE</span> and <span class="codefrag">CURRENT_ROLE</span>.</p>
-<a name="N103B3"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103B3"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103AA"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N103B7"></a><a name="Incompatibilities+with+Previous+Release-N103B7"></a>
+<a name="Incompatibilities+with+Previous+Release-N103AE"></a>
 <h5>Incompatibilities with Previous Release</h5>
-<a name="N103BB"></a><a name="Rationale+for+Change-N103BB"></a>
+<a name="Rationale+for+Change-N103B2"></a>
 <h5>Rationale for Change</h5>
-<a name="N103BF"></a><a name="Application+Changes+Required-N103BF"></a>
+<a name="Application+Changes+Required-N103B6"></a>
 <h5>Application Changes Required</h5>
 <hr>
-<a name="N103C4"></a><a name="Note+for+DERBY-3301"></a>
+<a name="Note+for+DERBY-3301"></a>
 <h4>Note for DERBY-3301</h4>
-<a name="N103CA"></a><a name="Summary+of+Change-N103CA"></a>
+<a name="Summary+of+Change-N103C1"></a>
 <h5>Summary of Change</h5>
 <p>Queries with nested EXIST, ANY or IN clauses now return correct results.</p>
-<a name="N103D0"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103D0"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103C7"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, applications that executed SQL statements containing nested EXISTS, ANY or IN clauses could see fewer rows than those satisfying the query. In particular, rows that had the same value for one of the selected columns as another row might not have been returned.</p>
-<a name="N103D6"></a><a name="Incompatibilities+with+Previous+Release-N103D6"></a>
+<a name="Incompatibilities+with+Previous+Release-N103CD"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None.</p>
-<a name="N103DC"></a><a name="Rationale+for+Change-N103DC"></a>
+<a name="Rationale+for+Change-N103D3"></a>
 <h5>Rationale for Change</h5>
 <p>The previous behavior violated the ANSI SQL standard. The new behavior is correct.</p>
-<a name="N103E2"></a><a name="Application+Changes+Required-N103E2"></a>
+<a name="Application+Changes+Required-N103D9"></a>
 <h5>Application Changes Required</h5>
 <p>Typically none, but applications must handle that the correct results are now returned.</p>
 <hr>
-<a name="N103E9"></a><a name="Note+for+DERBY-3026"></a>
+<a name="Note+for+DERBY-3026"></a>
 <h4>Note for DERBY-3026</h4>
-<a name="N103EF"></a><a name="Summary+of+Change-N103EF"></a>
+<a name="Summary+of+Change-N103E6"></a>
 <h5>Summary of Change</h5>
 <p>The <span class="codefrag">frameworks</span> directory (and its contents) has been removed.</p>
-<a name="N103F8"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103F8"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N103EF"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p></p>
-<span class="codefrag">frameworks</span><a name="N103FF"></a><a name="Incompatibilities+with+Previous+Release-N103FF"></a>
+<span class="codefrag">frameworks</span><a name="Incompatibilities+with+Previous+Release-N103F6"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Applications or commands referencing files in the <span class="codefrag">frameworks</span> directory will fail.</p>
-<a name="N10408"></a><a name="Rationale+for+Change-N10408"></a>
+<a name="Rationale+for+Change-N103FF"></a>
 <h5>Rationale for Change</h5>
 <p>In the 10.2.1.6 release, new and improved scripts were added in a new <span class="codefrag">bin</span> directory, intended to replace the scripts in the <span class="codefrag">frameworks</span> directory. The new scripts follow Apache conventions, and all scripts are located in a single directory, making them easier to find. Removing the old and deprecated scripts and the <span class="codefrag">frameworks</span> directory itself will eliminate a potential source of confusion and annoyance among users.</p>
 <p>The <span class="codefrag">frameworks</span> directory has been deprecated since the 10.2.1.6 release, and has not been maintained since then. The 10.2.1.6 release notes announced the deprecation of the scripts in the <span class="codefrag">frameworks</span> directory, and an additional file (<span class="codefrag">frameworks.DEPRECATED.txt</span>) was added in the top-level directory of the 10.3.1.4 release, with the purpose of alerting users about this change. A warning message was also added to the scripts in the <span class="codefrag">frameworks</span> directory at the same time.</p>
-<a name="N10425"></a><a name="Application+Changes+Required-N10425"></a>
+<a name="Application+Changes+Required-N1041C"></a>
 <h5>Application Changes Required</h5>
 <p>All references to the <span class="codefrag">frameworks</span> directory or its contents must be updated. The scripts in the <span class="codefrag">bin</span> directory may be used instead of the old scripts.</p>
 <hr>
-<a name="N10432"></a><a name="Note+for+DERBY-3013"></a>
+<a name="Note+for+DERBY-3013"></a>
 <h4>Note for DERBY-3013</h4>
-<a name="N10438"></a><a name="Summary+of+Change-N10438"></a>
+<a name="Summary+of+Change-N1042F"></a>
 <h5>Summary of Change</h5>
 <p>The column default value can now also be specified as CURRENT_USER or SESSION_USER.</p>
-<a name="N1043E"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1043E"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10435"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>None</p>
-<a name="N10444"></a><a name="Incompatibilities+with+Previous+Release-N10444"></a>
+<a name="Incompatibilities+with+Previous+Release-N1043B"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>None</p>
-<a name="N1044A"></a><a name="Rationale+for+Change-N1044A"></a>
+<a name="Rationale+for+Change-N10441"></a>
 <h5>Rationale for Change</h5>
 <p>Extend Derby's support for standard SQL constructions.</p>
-<a name="N10450"></a><a name="Application+Changes+Required-N10450"></a>
+<a name="Application+Changes+Required-N10447"></a>
 <h5>Application Changes Required</h5>
 <p>None.</p>
 <hr>
-<a name="N10457"></a><a name="Note+for+DERBY-2351"></a>
+<a name="Note+for+DERBY-2351"></a>
 <h4>Note for DERBY-2351</h4>
-<a name="N1045D"></a><a name="Summary+of+Change-N1045D"></a>
+<a name="Summary+of+Change-N10454"></a>
 <h5>Summary of Change</h5>
 <p>An ORDER BY clause of a DISTINCT query which specifies to order by a column which was not in the DISTINCT list is now rejected, because the intent of the query is ambiguous. Previously, Derby instead produced non-distinct results. Also, an ORDER BY clause which specifies a table-name-qualified column alias is now rejected as invalid, where previously it was accepted.</p>
-<a name="N10463"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10463"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1045A"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
-<a name="N10467"></a><a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
+<a name="New+rules+for+DISTINCT+and+ORDER+BY"></a>
 <h5>New rules for DISTINCT and ORDER BY</h5>
 <p>Applications which specify certain combinations of SELECT DISTINCT with ORDER BY will now receive an error message, whereas formerly such applications received non-distinct results.</p>
 <p>As an example, take the following:</p>
@@ -984,7 +985,7 @@ document.write("Last Published: " + docu
 </p>
 <p>The query above is now rejected, with the error message:</p>
 <p>If the AGE column is included in the DISTINCT list in the above query, there is no ambiguity</p>
-<a name="N1047F"></a><a name="New+column+alias+rules"></a>
+<a name="New+column+alias+rules"></a>
 <h5>New column alias rules</h5>
 <p>Applications which specify a column alias for a column in the SELECT statement, and which specify an ORDER BY clause which specifies that column alias qualified by the table name, will now receive an error indicating that the ORDER BY clause is invalid.</p>
 <p>As an example, take the following:</p>
@@ -994,7 +995,7 @@ document.write("Last Published: " + docu
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by idcolumn1, idcolumn2;</p>
 <p>or</p>
 <p>select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.id, t1.id;</p>
-<a name="N10495"></a><a name="Rationale+for+Change-N10495"></a>
+<a name="Rationale+for+Change-N1048C"></a>
 <h5>Rationale for Change</h5>
 <p>When the query ambiguously specifies both DISTINCT and ORDER BY, Derby was unsure whether to return the rows properly ordered, but non-distinct, or to return a distinct set of rows, but in an unknown order. Since no clear resolution of the ambiguity could be found, we chose instead to reject the query.</p>
 <p>The rules for resolving column references in ORDER BY clauses have been enhanced to consider column aliases and column names more fully. Derby now uses different resolution rules depending on whether the ORDER BY column reference is table.column, or just column:</p>
@@ -1004,29 +1005,29 @@ document.write("Last Published: " + docu
 </ul>
 <br>
 <br>
-<a name="N104A4"></a><a name="Application+Changes+Required-N104A4"></a>
+<a name="Application+Changes+Required-N1049B"></a>
 <h5>Application Changes Required</h5>
 <p>A query which specifies ordering by a non-distinct column should instead include the ORDER BY column in the DISTINCT list, to resolve the ambiguity about which values of that column should be used to distinctly identify the resulting rows.</p>
 <p>A query which specifies table-name.alias-name should be rewritten to specify either simply alias-name, or table-name.column-name.</p>
 <hr>
-<a name="N104AD"></a><a name="Note+for+DERBY-2065"></a>
+<a name="Note+for+DERBY-2065"></a>
 <h4>Note for DERBY-2065</h4>
-<a name="N104B3"></a><a name="Summary+of+Change-N104B3"></a>
+<a name="Summary+of+Change-N104AA"></a>
 <h5>Summary of Change</h5>
 <p>Error code changed for embedded connection when a connection with an open transaction is attempted closed.</p>
-<a name="N104B9"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N104B9"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N104B0"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>In the previous release, calling Connection.close() on a connection with an open transaction raised an error with error code 25001 with the client driver, whereas the embedded driver raised error code 25000. The embedded driver has now been changed to raise the same error code as the client driver, i.e. 25001, as specified by the SQL standard.</p>
-<a name="N104BF"></a><a name="Incompatibilities+with+Previous+Release-N104BF"></a>
+<a name="Incompatibilities+with+Previous+Release-N104B6"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Embedded applications that are dependent on the error code <em>ever</em> being "25000" could start failing. Embedded applications that are dependent on the error code <em>never</em> being "25001" could start failing.</p>
-<a name="N104CB"></a><a name="Rationale+for+Change-N104CB"></a>
+<a name="Rationale+for+Change-N104C2"></a>
 <h5>Rationale for Change</h5>
 <p>Harmonize error codes raised by the client and embedded drivers, thereby also making the embedded driver compatible with the SQL standard.</p>
-<a name="N104D1"></a><a name="Application+Changes+Required-N104D1"></a>
+<a name="Application+Changes+Required-N104C8"></a>
 <h5>Application Changes Required</h5>
 <p>Applications that are dependent on the error code must be changed to expect the new code.</p>
-<a name="N104D7"></a><a name="Build+Environment"></a>
+<a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <p>Derby release 10.4.1.3 was built using the following environment:</p>
 <ul>
@@ -1048,7 +1049,7 @@ document.write("Last Published: " + docu
 <strong>JSR 169</strong> - J2ME support was built using java.sun.com/j2me (cdc-1_1-fr-ri, jdbc_cdc1.0).</li>
 </ul>
 </div>
-<a name="N10500"></a><a name="Verifying+releases"></a>
+<a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>

Modified: websites/production/db/content/derby/releases/release-10.4.2.0.html
==============================================================================
--- websites/production/db/content/derby/releases/release-10.4.2.0.html (original)
+++ websites/production/db/content/derby/releases/release-10.4.2.0.html Wed Sep 28 01:33:43 2016
@@ -3,9 +3,8 @@
 <head>
 <META http-equiv="Content-Type" content="text/html; charset=UTF-8">
 <meta content="Apache Forrest" name="Generator">
-<meta name="Forrest-version" content="0.8">
+<meta name="Forrest-version" content="0.9">
 <meta name="Forrest-skin-name" content="pelt">
-<meta name="generator" content="">
 <title>Apache Derby 10.4.2.0 Release</title>
 <link type="text/css" href="../skin/basic.css" rel="stylesheet">
 <link media="screen" type="text/css" href="../skin/screen.css" rel="stylesheet">
@@ -485,6 +484,7 @@ document.write("Last Published: " + docu
           &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache Derby 10.4.2.0 Release</h1>
+<div id="front-matter">
 <div id="minitoc-area">
 <ul class="minitoc">
 <li>
@@ -523,7 +523,8 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 </div>
-<a name="N10010"></a><a name="Distributions"></a>
+</div>
+<a name="Distributions"></a>
 <h2 class="boxed">Distributions</h2>
 <div class="section">
 <p>Use the links below to download a distribution of Apache Derby from one of our mirrors. You should <strong>always</strong> <a href="#Verifying+releases">verify the integrity</a> of distribution files downloaded from a mirror.</p>
@@ -556,11 +557,11 @@ document.write("Last Published: " + docu
 <a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.4.2.0/derby_ui_plugin_1.1.2.zip">derby_ui_plugin_1.1.2.zip</a> [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.4.2.0/derby_ui_plugin_1.1.2.zip.asc">PGP</a>] [<a class="external" href="http://archive.apache.org/dist/db/derby/db-derby-10.4.2.0/derby_ui_plugin_1.1.2.zip.md5">MD5</a>]</p>
 <p>Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the <a href="http://db.apache.org/derby/integrate/plugin_howto.html">Using the 10 Core and 1.1 UI Derby plug-ins</a> page.</p>
 </div>
-<a name="N100BC"></a><a name="Release Notes for Derby 10.4.2.0"></a>
+<a name="Release Notes for Derby 10.4.2.0"></a>
 <h2 class="boxed">Release Notes for Derby 10.4.2.0</h2>
 <div class="section">
 <p>These notes describe the difference between Derby release 10.4.2.0 and the preceding release 10.4.1.3.</p>
-<a name="N100C4"></a><a name="Overview"></a>
+<a name="Overview"></a>
 <h3 class="boxed">Overview</h3>
 <p>Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs.</p>
 <p>Derby functionality includes:</p>
@@ -570,10 +571,10 @@ document.write("Last Published: " + docu
 <li>Network client JDBC drivers</li>
 <li>Command line tools: ij (SQL scripting), dblook (schema dump), and sysinfo (system info)</li>
 </ul>
-<a name="N100D7"></a><a name="New+Features"></a>
+<a name="New+Features"></a>
 <h3 class="boxed">New Features</h3>
 <p>This is a maintenance release. No new features were added.</p>
-<a name="N100DF"></a><a name="Bug+Fixes"></a>
+<a name="Bug+Fixes"></a>
 <h3 class="boxed">Bug Fixes</h3>
 <p>The following issues are addressed by Derby release 10.4.2.0. These issues are not addressed in the preceding 10.4.1.3 release.</p>
 <table class="ForrestTable" cellspacing="1" cellpadding="4" border="2">
@@ -791,7 +792,7 @@ document.write("Last Published: " + docu
 <td><a class="external" href="http://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a></td><td>A connection request that has a default schema that is being created by another transaction will fail to connect</td>
 </tr>
 </table>
-<a name="N102DA"></a><a name="Issues"></a>
+<a name="Issues"></a>
 <h3 class="boxed">Issues</h3>
 <p>Compared with the previous release (10.4.1.3), Derby release 10.4.2.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
 <ul>
@@ -805,46 +806,46 @@ document.write("Last Published: " + docu
 </li>
 </ul>
 <hr>
-<a name="N102F1"></a><a name="Note+for+DERBY-3701"></a>
+<a name="Note+for+DERBY-3701"></a>
 <h4>Note for DERBY-3701</h4>
-<a name="N102F7"></a><a name="Summary+of+Change"></a>
+<a name="Summary+of+Change"></a>
 <h5>Summary of Change</h5>
 <p>An error message will be logged to derby.log if the Network Server tracing file cannot be created. Starting with version 10.5, the Network Server will attempt to create the trace directory if it does not exist. Any intervening directories in the given path will also be created if possible.</p>
-<a name="N102FD"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>Before the fix for DERBY-3110, if derby.drda.traceAll was set to true and the derby.drda.traceDirectory was set to a non-existent directory, no tracing would occur and no error would occur. After the fix for DERBY-3110, an error "java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept connections" would occur and the client would hang and no tracing would occur. With this fix for version 10.5 and higher, the Network Server will attempt to create the trace directory if possible. For 10.4.2 (and the next release on the 10.3 branch), the Network Server will still not try to create the directory. For all these releases the Network Server will print an error on session connect if there is any problem creating the trace file, but the Network Server will not cause the session connection to fail. Users who have trace turned on and the trace directory set to a non-existent directory may now see exceptions in the derby.log on connect indicating that the trace file is not found <strong>
 or</strong> with 10.5 or higher they may see tracing occur where it did not before.</p>
-<a name="N10306"></a><a name="Incompatibilities+with+Previous+Release"></a>
+<a name="Incompatibilities+with+Previous+Release"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Tracing properties will not be ignored or cause the client to hang if the trace directory is set to a non-existent directory.</p>
-<a name="N1030C"></a><a name="Rationale+for+Change"></a>
+<a name="Rationale+for+Change"></a>
 <h5>Rationale for Change</h5>
 <p>The tracing properties should not be summarily ignored or cause the client to hang if the trace directory does not exist.</p>
-<a name="N10312"></a><a name="Application+Changes+Required"></a>
+<a name="Application+Changes+Required"></a>
 <h5>Application Changes Required</h5>
 <p>Applications that counted on the derby.drda.traceAll property being ignored if derby.drda.traceDirectory was set to a non-existent directory, need to turn tracing off or they may now see many errors in the derby.log or large amounts of tracing.</p>
 <hr>
-<a name="N10319"></a><a name="Note+for+DERBY-48"></a>
+<a name="Note+for+DERBY-48"></a>
 <h4>Note for DERBY-48</h4>
-<a name="N1031F"></a><a name="Summary+of+Change-N1031F"></a>
+<a name="Summary+of+Change-N10316"></a>
 <h5>Summary of Change</h5>
 <p>In Derby, a user's <strong>initial default schema</strong> is named the same as the user name, or APP if a user is not provided at connect time. This schema is implicitly auto-created the first time a schema object is created in that schema.</p>
 <p>Previously, this auto-creation would be performed as part of the user transaction. This would sometimes lead to locking issues as described in this issue. With this change, the auto-creation is now performed and committed immediately in a separate sub-transaction.</p>
-<a name="N1032A"></a><a name="Symptoms+Seen+by+Applications+Affected+by+Change-N1032A"></a>
+<a name="Symptoms+Seen+by+Applications+Affected+by+Change-N10321"></a>
 <h5>Symptoms Seen by Applications Affected by Change</h5>
 <p>The initial default schema will be present in cases where it previously would not yet have been created: If the user transaction that creates a schema object leading to auto-creation of the initial default schema rolls back for some reason after having created the schema, up till now the auto-creation of the initial default schema would be rolled back as well. Since it is now created and committed in a sub-transaction, the schema creation will not be rolled back: the default schema will persist.</p>
-<a name="N10330"></a><a name="Incompatibilities+with+Previous+Release-N10330"></a>
+<a name="Incompatibilities+with+Previous+Release-N10327"></a>
 <h5>Incompatibilities with Previous Release</h5>
 <p>Most applications should not be impacted by this change, but there are some corner cases as described below:</p>
 <p>If the application tests for the existence of the initial default schema by querying Derby system tables, the results could now be different than in earlier releases, if the test is made after a rollback as described in the previous section.</p>
 <p>Since the initial default schema will now potentially exist in cases where it would previously not exist, schema operations may be impacted, e.g. where before a DROP SCHEMA &lt;default schema name&gt; RESTRICT would fail due to it not yet existing, it could now work (if empty), depending on when the drop attempt is made.</p>
-<a name="N1033A"></a><a name="Rationale+for+Change-N1033A"></a>
+<a name="Rationale+for+Change-N10331"></a>
 <h5>Rationale for Change</h5>
 <p>Implicit schema creation is now performed in its own transaction to avoid deadlocks with other connections accessing the same schema.</p>
 <p>Doing this is a separate transaction avoids holding dictionary locks longer than necessary, cf. <a class="external" href="https://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a> and thus reduces the chance for deadlocks.</p>
-<a name="N10346"></a><a name="Application+Changes+Required-N10346"></a>
+<a name="Application+Changes+Required-N1033D"></a>
 <h5>Application Changes Required</h5>
 <p>Verify that the application code does not rely on the initial default schema being absent after a rollback.</p>
-<a name="N1034C"></a><a name="Build+Environment"></a>
+<a name="Build+Environment"></a>
 <h3 class="boxed">Build Environment</h3>
 <p>Derby release 10.4.2.0 was built using the following environment:</p>
 <ul>
@@ -866,7 +867,7 @@ document.write("Last Published: " + docu
 <strong>JSR 169</strong> - J2ME libraries were supplied by phoneme.dev.java.net (CDC, Foundation Profile, and Personal Basis Profile meeting the 1.1.2 specifications). JSR169 libraries were supplied by java.sun.com.</li>
 </ul>
 </div>
-<a name="N10375"></a><a name="Verifying+releases"></a>
+<a name="Verifying+releases"></a>
 <h2 class="boxed">Verifying releases</h2>
 <div class="section">
 <p>It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.</p>


Loading...