You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Kathey Marsden <km...@sbcglobal.net> on 2007/11/28 20:11:35 UTC
Release notes for 10.3.2.1 (was Re: svn commit: r599095 - in /db/derby/code/branches/10.3:
CHANGES.html RELEASE-NOTES.html releaseSummary.xml)
I checked in the release notes for 10.3.2.1. Let me know right away if
you see any issues.
Happily, the release note generator is happy with the new DERBY-2967
release note, so no manual intervention was needed this time.
Sending CHANGES.html
Sending RELEASE-NOTES.html
Sending releaseSummary.xml
Transmitting file data ...
Committed revision 599095.
Kathey
kmarsden@apache.org wrote:
> Author: kmarsden
> Date: Wed Nov 28 11:03:54 2007
> New Revision: 599095
>
> URL: http://svn.apache.org/viewvc?rev=599095&view=rev
> Log:
> Release notes for 10.3.2.1
>
>
> Modified:
> db/derby/code/branches/10.3/CHANGES.html
> db/derby/code/branches/10.3/RELEASE-NOTES.html
> db/derby/code/branches/10.3/releaseSummary.xml
>
> Modified: db/derby/code/branches/10.3/CHANGES.html
> URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/CHANGES.html?rev=599095&r1=599094&r2=599095&view=diff
> ==============================================================================
> --- db/derby/code/branches/10.3/CHANGES.html (original)
> +++ db/derby/code/branches/10.3/CHANGES.html Wed Nov 28 11:03:54 2007
> @@ -1,8 +1,8 @@
> <html>
> -<title>Changes for Derby 10.3.2.0</title>
> +<title>Changes for Derby 10.3.2.1</title>
> <body>
> <h1>
> -<a name="Changes for Derby 10.3.2.0"></a>Changes for Derby 10.3.2.0</h1>
> +<a name="Changes for Derby 10.3.2.1"></a>Changes for Derby 10.3.2.1</h1>
> <blockquote></blockquote>
> <ul>
> <li>
> @@ -12,12 +12,15 @@
> <h2>
> <a name="CHANGES"></a>CHANGES</h2>
> <blockquote>
> -<p>The following table lists issues in JIRA which were fixed between Derby release 10.3.2.0 and the preceding release 10.3.1.4. This includes issues for the product source, documentation and tests</p>
> +<p>The following table lists issues in JIRA which were fixed between Derby release 10.3.2.1 and the preceding release 10.3.1.4. This includes issues for the product source, documentation and tests</p>
> <table border="2">
> <tr>
> <td><b>Issue Id</b></td><td><b>Description</b></td>
> </tr>
> <tr>
> +<td><a href="http://issues.apache.org/jira/browse/DERBY-3232">DERBY-3232</a></td><td>Top-level index.html in releases incorrectly indicates support for JDBC 2.1 in 10.3 releases</td>
> +</tr>
> +<tr>
> <td><a href="http://issues.apache.org/jira/browse/DERBY-3216">DERBY-3216</a></td><td>do row level lock space reclamation in btree of indiv rows.</td>
> </tr>
> <tr>
> @@ -40,6 +43,9 @@
> </tr>
> <tr>
> <td><a href="http://issues.apache.org/jira/browse/DERBY-3174">DERBY-3174</a></td><td>NetworkServerControlApiTest fails with java.security.AccessControlException if not run as first test</td>
> +</tr>
> +<tr>
> +<td><a href="http://issues.apache.org/jira/browse/DERBY-3172">DERBY-3172</a></td><td>ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown</td>
> </tr>
> <tr>
> <td><a href="http://issues.apache.org/jira/browse/DERBY-3159">DERBY-3159</a></td><td>SYSCS_SET_USER_ACCESS fails if the user name contains characters not allowed in regular identifiers. </td>
>
> Modified: db/derby/code/branches/10.3/RELEASE-NOTES.html
> URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/RELEASE-NOTES.html?rev=599095&r1=599094&r2=599095&view=diff
> ==============================================================================
> --- db/derby/code/branches/10.3/RELEASE-NOTES.html (original)
> +++ db/derby/code/branches/10.3/RELEASE-NOTES.html Wed Nov 28 11:03:54 2007
> @@ -1,10 +1,10 @@
> <html>
> -<title>Release Notes for Derby 10.3.2.0</title>
> +<title>Release Notes for Derby 10.3.2.1</title>
> <body>
> <h1>
> -<a name="Release Notes for Derby 10.3.2.0"></a>Release Notes for Derby 10.3.2.0</h1>
> +<a name="Release Notes for Derby 10.3.2.1"></a>Release Notes for Derby 10.3.2.1</h1>
> <blockquote>
> -<p>These notes describe the difference between Derby release 10.3.2.0 and the preceding release 10.3.1.4.</p>
> +<p>These notes describe the difference between Derby release 10.3.2.1 and the preceding release 10.3.1.4.</p>
> </blockquote>
> <ul>
> <li>
> @@ -67,12 +67,15 @@
> <h2>
> <a name="Bug Fixes"></a>Bug Fixes</h2>
> <blockquote>
> -<p>The following issues are addressed by Derby release 10.3.2.0. These issues are not addressed in the preceding 10.3.1.4 release.</p>
> +<p>The following issues are addressed by Derby release 10.3.2.1. These issues are not addressed in the preceding 10.3.1.4 release.</p>
> <table border="2">
> <tr>
> <td><b>Issue Id</b></td><td><b>Description</b></td>
> </tr>
> <tr>
> +<td><a href="http://issues.apache.org/jira/browse/DERBY-3232">DERBY-3232</a></td><td>Top-level index.html in releases incorrectly indicates support for JDBC 2.1 in 10.3 releases</td>
> +</tr>
> +<tr>
> <td><a href="http://issues.apache.org/jira/browse/DERBY-3216">DERBY-3216</a></td><td>do row level lock space reclamation in btree of indiv rows.</td>
> </tr>
> <tr>
> @@ -88,6 +91,9 @@
> <td><a href="http://issues.apache.org/jira/browse/DERBY-3175">DERBY-3175</a></td><td>NullPointerException on INSERT after ALTER TABLE ... DROP COLUMN</td>
> </tr>
> <tr>
> +<td><a href="http://issues.apache.org/jira/browse/DERBY-3172">DERBY-3172</a></td><td>ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown</td>
> +</tr>
> +<tr>
> <td><a href="http://issues.apache.org/jira/browse/DERBY-3159">DERBY-3159</a></td><td>SYSCS_SET_USER_ACCESS fails if the user name contains characters not allowed in regular identifiers. </td>
> </tr>
> <tr>
> @@ -248,17 +254,31 @@
> <h2>
> <a name="Issues"></a>Issues</h2>
> <blockquote>
> -<p>Compared with the previous release (10.3.1.4), Derby release 10.3.2.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
> -<hr>
> +<p>Compared with the previous release (10.3.1.4), Derby release 10.3.2.1 introduces the following new features and incompatibilities. These merit your special attention.</p>
> <ul>
> -<h3 class="boxed">DERBY-2967</h3>
> +<li>
> +<a href="#Note for DERBY-2967">
> +<p>Note for DERBY-2967:
> + Databases with territory based collation might see the behavior of LIKE predicate in WHERE clause has changed.
> +</p>
> +</a>
> +</li>
> +</ul>
> +<hr>
> +<h3>
> +<a name="Note for DERBY-2967"></a>Note for DERBY-2967</h3>
> +<blockquote>
> +
>
> <h4>Summary of Change</h4>
> +
> <p>
> Databases with territory based collation might see the behavior of LIKE predicate in WHERE clause has changed.
> </p>
>
> +
> <h4>Symptoms Seen by Applications Affected by Change</h4>
> +
> <p>
> In territory based databases, the LIKE predicate will now comply with SQL specification(Derby already follows SQL specification for UCS_BASIC databases). SQL specification for LIKE predicate requires that database should do one character comparison at a time. Prior to the fix that went in as part of DERBY-2967, Derby did string comparison rather than character comparison for LIKE. This causes a problem with territory based database because the collation element(s) for a string of characters may not be same as the collation element(s) for inidivdual characters that make up that string.
> In addition, the metacharacter _ in the pattern in a LIKE predicate will now consume exactly one character rather than working on number of collation elements.
> @@ -269,22 +289,26 @@
> </p>
>
>
> +
> <h4>Rationale for Change</h4>
> +
> <p>
> The previous behavior violated the SQL specification. The new behavior is correct.
> </p>
>
> -</ul>
> +
> +
> +</blockquote>
> </blockquote>
> <h2>
> <a name="Build Environment"></a>Build Environment</h2>
> <blockquote>
> -<p>Derby release 10.3.2.0 was built using the following environment:</p>
> +<p>Derby release 10.3.2.1 was built using the following environment:</p>
> <ul>
> <li>
> <b>Branch</b> - Source code came from the 10.3 branch.</li>
> <li>
> -<b>Machine</b> - Cygwin on Microsoft Windows XP Professional Version 2002 Service Pack 2.</li>
> +<b>Machine</b> - MKS Toolkit 8.1 on Microsoft Windows XP Professional Version 2002 Service Pack 2.</li>
> <li>
> <b>Ant</b> - Apache Ant version 1.7.0 compiled on December 13 2006.</li>
> <li>
> @@ -297,7 +321,7 @@
> <b>Compiler</b> - The 1.4.2_07-b05 javac was used to compile all classes
> except for the JDBC4 drivers. The JDBC4 driver classes were compiled using the 1.6.0_01-b06 javac.</li>
> <li>
> -<b>JSR 169</b> - J2ME support was built using IBM J9 - VM for the Java(TM) platform, Version 2.3 </li>
> +<b>JSR 169</b> - Java ME support was built using Java ME CDC/Foundation Specification 1.1 libraries from IBM WebSphere Everyplace Micro Environment 6.1 </li>
> </ul>
> </blockquote>
> </body>
>
> Modified: db/derby/code/branches/10.3/releaseSummary.xml
> URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/releaseSummary.xml?rev=599095&r1=599094&r2=599095&view=diff
> ==============================================================================
> --- db/derby/code/branches/10.3/releaseSummary.xml (original)
> +++ db/derby/code/branches/10.3/releaseSummary.xml Wed Nov 28 11:03:54 2007
> @@ -31,7 +31,7 @@
>
> E.g.: 10.3.0.4
> -->
> -<releaseID>10.3.2.0</releaseID>
> +<releaseID>10.3.2.1</releaseID>
>
> <!--
> Identifier of previous release. The release notes describe the
> @@ -80,7 +80,7 @@
> tookit you used.
> E.g.: J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).
> -->
> - <jsr169>J2ME support was built using IBM J9 - VM for the Java(TM) platform, Version 2.3 </jsr169>
> + <jsr169>Java ME support was built using Java ME CDC/Foundation Specification 1.1 libraries from IBM WebSphere Everyplace Micro Environment 6.1 </jsr169>
>
> </buildInfo>
>
>
>
>
>