Featrue: Update Derby to 10.8.2.2 (see https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5813)

commit: 691082159e23f1285222e92b5c09be38f3e60bb7 [log] [tgz]
author: Juergen G. Kissner <juergen.kissner@sap.com> Wed Feb 08 10:13:53 2012 +0000
committer: Juergen G. Kissner <juergen.kissner@sap.com> Wed Feb 08 10:13:53 2012 +0000
tree: 47bd8f512a787302413edab512ce42dea1593a14
parent: a164582a703b498f72dda5701b208971dfe71443 [diff]
diff --git a/derby/org.apache.derby/KEYS b/derby/org.apache.derby/KEYS
index f31e2a3..21dfa7f 100644
--- a/derby/org.apache.derby/KEYS
+++ b/derby/org.apache.derby/KEYS

@@ -572,3 +572,105 @@
 6hX2i0IyAJ4yGKI40y/nDimi/ZeODNW3UcnK2A==

 =Miig

 -----END PGP PUBLIC KEY BLOCK-----

+pub   1024D/8656BABD 2007-10-10

+uid                  Kristian Waagan (Apache Software Foundation) <kristwaa@apache.org>

+sig 3        8656BABD 2007-10-18  Kristian Waagan (Apache Software Foundation) <kristwaa@apache.org>

+sig 3        990ED4AA 2007-10-10  Knut Anders Hatlen <kahatlen@apache.org>

+sig          35C100F0 2007-10-10  Bernt M. Johnsen <bernt@apache.org>

+sig 3        5355D01C 2007-10-17  Dag H. Wanvik (Derby committer) <dag@apache.org>

+sig          FFCCF7B1 2007-10-17  Dyre Tjeldvoll <dyre@apache.org>

+

+-----BEGIN PGP PUBLIC KEY BLOCK-----

+Version: GnuPG v1.4.8 (SunOS)

+

+mQGiBEcMcksRBACm4ubnQWAb+KnoiCIYceDZ/MLsGBiwacT8K39LhVfWHsRwieiV

+lntDKHms69bejtm+HChVT806mbFb6DC2BYGXZF/9BrHKz8IUOJrMDhX335IRGqtk

+/JJMOIz9s6aHdpDetNCmJ9Qi/m/RZMvbdyY4uyzH41c9zbA5ZkNf3az0TwCg4wQj

+Y7iISfGi9d1i+4qkQ1DtHjcEAKUncD3WEC2ARiyGN2y8OQ+jlBgr7jZacI69sG8A

+KE/PuzA1VnrcNc56l+LSPa6F1NrN8Qb3tUWQEmHf9xjupK9wGc5U9l5kmtZT4uBj

+YaZThE3EfyKeAQ7qG/HQ8eYRyK/aM7/3PyR4BKdIPUbVr4lJWQvFCAEl/NHOQ+TP

+tsnsBACFEvQR+Q5p7P5FomZ9zhloucxAp5/kowrPbfpuhcbzIZ7oV83MyFA4lPQd

+At3run++UIurrm2Oa2rq3Uieto6TY+eO/vZKuGkL3jU3wEzvTVkuSejGL+AQloTH

+r+fnUWfkvGD9+gerOS5IUFYeR1obWCMx4LL811meTUnXhE/YzLRCS3Jpc3RpYW4g

+V2FhZ2FuIChBcGFjaGUgU29mdHdhcmUgRm91bmRhdGlvbikgPGtyaXN0d2FhQGFw

+YWNoZS5vcmc+iGMEExECACMCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCRxco

+8gIZAQAKCRArECrvhla6vVdMAKCmo5lj+jjkVxEkxvmeFlrr+eizyACgvspNnUAh

+qykuXN/fGXyNbvxI91WIRgQTEQIABgUCRwyDAwAKCRDh4fKwmQ7UquEvAKCBlUZd

+MYGQpbImrCfcwvOaqujo6ACfTVwkcZyW7KtVODnr08OoINuuvACIRgQQEQIABgUC

+RwzRRQAKCRCUUEP1NcEA8NWWAKC6vK10uj/Opi2UhE8GRivBDU+CHACgyOC3XlN0

+/nNIo98HFs+Ef0Ze73OIRgQTEQIABgUCRxXMcQAKCRDhZNinU1XQHFhXAJ9FNhWh

+0DG8E3Aydub+uvdyKxxzDgCgjlZ+0L7wtMOEqJ8XWJJrjrh2HmeIRgQQEQIABgUC

+RxY5ngAKCRB7MqOq/8z3sTUXAKCUg+wqpoejSEp3eI0Wvbh4ItdAsQCfYg7o9ZaI

+/MeQ/yTMl01w0vjJX5a0N0tyaXN0aWFuIFdhYWdhbiAocHJpdmF0ZS9wZXJzb25h

+bCkgPGtyaXN0d2FhQGdtYWlsLmNvbT6IYAQTEQIAIAIbAwYLCQgHAwIEFQIIAwQW

+AgMBAh4BAheABQJHFyjlAAoJECsQKu+GVrq9zRgAn0sh9bBsK7XiXyNqmqzBwvwC

+tEJ3AKCcLLYXms0l5nwmBXcZ5WgRVu+kVYhGBBMRAgAGBQJHDIMDAAoJEOHh8rCZ

+DtSq8bgAn218vx9PgSXTPMPfBRxHCv2MK1jPAJ9AWbSrXoP0G9RvVOaYi7+4Dw6j

+UohGBBARAgAGBQJHDNFCAAoJEJRQQ/U1wQDwg9oAn0R6aUuc/cGzUvht/II31asx

+K+0IAJ966BwOVUBCj8+HXyegHgOdBdD32ohGBBMRAgAGBQJHFcxxAAoJEOFk2KdT

+VdAcKNQAoKIZKCEeN1dgJRnIVcem9XafD7o3AJ9cdTEHxdpg3C8Xqt+gKHNhW2tV

+JYhGBBARAgAGBQJHFjmeAAoJEHsyo6r/zPexfjUAoNuH20ZmE4jjsL0IkoADeKi0

+LKevAJ9lTwkNDLe7PjXP13unI0sDtnkTmLRBS3Jpc3RpYW4gV2FhZ2FuIChTdW4g

+TWljcm9zeXN0ZW1zIEluYy4pIDxLcmlzdGlhbi5XYWFnYW5AU3VuLkNPTT6IYAQT

+EQIAIAUCRwx1IAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJECsQKu+GVrq9

+RAwAoNfKENACeZnk/l/8b7vV5WheOgRMAJ9ZTCEavsWce9qX4xkw9K5qJAQV9YhG

+BBMRAgAGBQJHDIMDAAoJEOHh8rCZDtSqDNMAni+Pu7GpQk3o+aX/SiQDnG2n11g6

+AJ9/9k8YAp/P+X40xIYL3/2XApgiT4hGBBARAgAGBQJHDNFFAAoJEJRQQ/U1wQDw

+RUUAoLrjW4sorWCv5N3NTMD/EXsDI3toAJ9xI3glzY5CrAREYl65ltYfL/ZQTIhG

+BBMRAgAGBQJHFcxxAAoJEOFk2KdTVdAc6pkAoIq2RtmuuDobXDqEIA0YbTafVD14

+AJ9uYWhEvs+PHPym1qEBnk2YmE5TyYhGBBARAgAGBQJHFjmeAAoJEHsyo6r/zPex

+GzwAn3eu1jAps+XPuUT9oeszgRZNdUcBAJ0bO+9cnADAAAAq3upsZ94a8NkSLrkC

+DQRHDHJLEAgA2m1YmG3dETrnC+e19TcIMtE2NLcpxHVZqcxvWKo7fXgs1zu182eV

+9v2pHQNFr+SDJGyr/V2LjDQqYzyDHot3To1OBmXwLk8qcr2xHLS2zMSFTSXq/aYF

+4QjaCyz4vZQQLsL8UsRAggS4hScqg54VrJ6Fd6YVQ7s9RlaVpp9+Wnx1pRcAKNd3

+KQR8QaCOTlhJG9TgmvPQSjhzoFh2Fdu36nfDtfVYbgYpSCEHkFsxbVpeFSPMEEEK

+PngA8WbYEHwNp+z55XpcJ7peZ7k0u6ywqEdkLaZsV3Sr3q2+uPNsFCpX0/DuyxjC

+vu0wpsuYKWJoRnT9xCIDKeHOaIwv5+DYSwADBQf/WGQu5+R/eNK8kcV5DqnhX/2K

+tTZiunG7Jy2K+P2DCw0M6Jy+WaNw2ZhqdXyn7d9LYwB/opkugeKwmms4GXnKbXdv

+1DId7/5py555nRFyBn3XzZWyShG141tlQmgTPN02il4u0fdVvUpmqll93saikOpB

+4wvSDUg+ifm5MZsR2YCxldL2ZoFZDlKiU0Xsm3lOdCl5TntyJIzJ1gECMc+KuSNh

+xDJamq4e1jEibVP1/0cvwLB2pZsWmJ05jYXg47Iep4z3m9sDnyX/39t+FX2Kicom

++bH/6Qje3uO5eOBEGCtOs2QFhGZSDRMcJuWiJd5oTB+HxZHkXs9drKos5LmmNIhJ

+BBgRAgAJBQJHDHJLAhsMAAoJECsQKu+GVrq9GaoAnA+d6GO7tDu2XsNPuD8gXVdq

+he01AKDHCOM0tKuYZCVZTsMQ/Z0TQWykOw==

+=Upsq

+-----END PGP PUBLIC KEY BLOCK-----

+pub   2048R/37E24863 2010-08-24

+uid                  Lily Wei (Apache committer) <lilywei@apache.org>

+sig 3        37E24863 2010-08-24  Lily Wei (Apache committer) <lilywei@apache.org>

+sig          B1669287 2010-08-24  Kathey Marsden <kmarsden@apache.org>

+sub   2048R/F98F0036 2010-08-24

+sig          37E24863 2010-08-24  Lily Wei (Apache committer) <lilywei@apache.org>

+

+-----BEGIN PGP PUBLIC KEY BLOCK-----

+Version: GnuPG v1.4.10 (MingW32)

+

+mQENBExz/rQBCADWQUf6ic7VK8wjld/+GHW1HCaA5XexAM9ogNrZOngG54uG0GdK

+06fgspQZyg8Z9Dt2YrZ7zC6S9DTcE8dfC0xgRE52cydJX2n3Qxdq7PLKC2DSUERy

+cFyJMCsGRI4t2q/Bap8bIzC1CLlDiJmwTm1plKt2VfxZ2lFEApxA8yQcyI8bC8Kz

+P1N71fu/I/hOMHmr40inA/vDhu0ayy19lpGows0mbk4BUR7j7I3ypUIJww2fBFm4

+x9fAmxV5+g5NsWTiB75Ec1IsUH4frHmOyZYqK0BHIazKKWRh4yZKS5zmi539QUGi

+M7FLjvbmR0UVRK0Sfzn/qHM0FvChL0IchXFXABEBAAG0MExpbHkgV2VpIChBcGFj

+aGUgY29tbWl0dGVyKSA8bGlseXdlaUBhcGFjaGUub3JnPokBOAQTAQIAIgUCTHP+

+tAIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQvdVZfTfiSGMfsQgAihEL

+lLyiMwStTyIHqs/ZN+RxDg23ndu70B7fWP70UCZCKdSZsMyrxgLEwovK31TnO2Br

+8msQovzEjZQ6/J0C9Bh1J3Vca98eHg43dgcT7dTHJxXkFFmPsFSGnUGG+FVwsqx4

+S3QbWNV9dncaJ5LXw0m9t49MHS0w85mwH2DWvSChNOsPKzHuvWq46X1VvxLCos8J

+t09SY93abDGVkWLeM5EhHv0Tx/gmksxUGffTK977VVL+ROuAJi+FeU13aLkW3NOM

+TniCk5xLYllmHhyfRtw1LeAKJHnHznd5mHbYgQPL6ttJfCPun0URixuuORqFLJCx

+EGmQYKydIbgL/BGwR4hGBBARAgAGBQJMdAXiAAoJEBtId+mxZpKHlSQAn2yn1IjB

+sGAgirOtNVih5pZfsCSAAJ0dR03Y9glShY/r9wa3Yw7zBQ5KSLkBDQRMc/60AQgA

+wowpCfwe+qxOWSco7L52nz88HW7grKsSmIfiFKkULCbqyDC8kp6X+bNrs7zQMnfT

+BF1hwjpC2dQHbgTt5HT5V5GszHmmbuhmOteq8Fc8grVOo75N9pgUX/WIadeQF+VP

+EsGIR07U0+yU9kaTSXGT6U14lHgcq3DnOtYpUzCRThuEDGkIO4FdR36b7iSTEavJ

+GphJ9hqIwS38QyaiQvFtRyYDKXcQQ3c5WU24dUSJ7YUOQIatsIfem9pEFuxEW8Jd

+GSsUqO2HG51c9IBjz756NI8szdylLGksg81+W8NKuE7kkYhSIHyIV0fjnrE999Pu

+MTaIzrYKI0JUPtfviJluAwARAQABiQEfBBgBAgAJBQJMc/60AhsMAAoJEL3VWX03

+4khjVZ0H/jl+btt8iGpwtutWZhH2jPuTeCfdhC56BZ1GBoZARy1ZajLKsFZJ1OzL

+fTTlxY5zMSK9y1Qz/+aodvYQhZHGTBzWsoQ75JBef37v2x6PpXZ8gHoMn7lThNFZ

+IlHvq31wB6uW7mbleYj6EuNcnJdRjffhqt2i9YTiyHpAPi9ENiFRNDZyxodVJIGc

+J2CXSelwLkMUN4SeJV4mFlZOmGmImsFDnbJ0PM0J0wSiUByqyHMJgPcKNICQ5q8f

+b4c1FOztiCYW/DxSvkiO69sKaouF/L2/+pAkVKc0UNueMuM2gGEV84rLN/p/l9+y

+J07farOS7/KiDvcc5FVfn3DtRSQCh+Y=

+=sLox

+-----END PGP PUBLIC KEY BLOCK-----


diff --git a/derby/org.apache.derby/META-INF/MANIFEST.MF b/derby/org.apache.derby/META-INF/MANIFEST.MF
index b369ff8..257aa33 100644
--- a/derby/org.apache.derby/META-INF/MANIFEST.MF
+++ b/derby/org.apache.derby/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@
 Bundle-ManifestVersion: 2
 Bundle-Name: Apache Derby JDBC
 Bundle-SymbolicName: org.apache.derby
-Bundle-Version: 10.5.1.1
+Bundle-Version: 10.8.2.2
 Import-Package: javax.sql,javax.net,
  javax.naming,javax.naming.spi,
  javax.crypto,javax.crypto.spec,

diff --git a/derby/org.apache.derby/NOTICE b/derby/org.apache.derby/NOTICE
index eb68fb3..6eb6795 100644
--- a/derby/org.apache.derby/NOTICE
+++ b/derby/org.apache.derby/NOTICE

@@ -1,14 +1,21 @@
 =========================================================================

-==  NOTICE file corresponding to section 4(d) of the Apache License,   ==

-==  Version 2.0, in this case for the Apache Derby distribution.       ==

+==  NOTICE file corresponding to section 4(d) of the Apache License,

+==  Version 2.0, in this case for the Apache Derby distribution.

+==

+==  DO NOT EDIT THIS FILE DIRECTLY. IT IS GENERATED

+==  BY THE buildnotice TARGET IN THE TOP LEVEL build.xml FILE.

+==

 =========================================================================

 

 Apache Derby

-Copyright 2004-2009 The Apache Software Foundation

+Copyright 2004-2011 The Apache Software Foundation

 

 This product includes software developed by

 The Apache Software Foundation (http://www.apache.org/).

 

+

+=========================================================================

+

 Portions of Derby were originally developed by

 International Business Machines Corporation and are

 licensed to the Apache Software Foundation under the

@@ -22,8 +29,10 @@
 

 (C) Copyright IBM Corp. 2003. 

 

+

 =========================================================================

 

+

 The portion of the functionTests under 'nist' was originally 

 developed by the National Institute of Standards and Technology (NIST), 

 an agency of the United States Department of Commerce, and adapted by

@@ -32,11 +41,14 @@
 http://www.itl.nist.gov/div897/ctg/sql_form.htm

 

 

+

 =========================================================================

 

+

 The JDBC apis for small devices and JDBC3 (under java/stubs/jsr169 and

 java/stubs/jdbc3) were produced by trimming sources supplied by the

-Apache Harmony project. The following notice covers the Harmony sources:

+Apache Harmony project. In addition, the Harmony SerialBlob and

+SerialClob implementations are used. The following notice covers the Harmony sources:

 

 Portions of Harmony were originally developed by

 Intel Corporation and are licensed to the Apache Software

@@ -46,11 +58,12 @@
 

 =========================================================================

 

+

 The Derby build relies on source files supplied by the Apache Felix

 project. The following notice covers the Felix files:

 

   Apache Felix Main

-  Copyright 2009 The Apache Software Foundation

+  Copyright 2008 The Apache Software Foundation

 

 

   I. Included Software

@@ -80,8 +93,10 @@
   - Apache License 2.0

   - BSD License

 

+

 =========================================================================

 

+

 The Derby build relies on jar files supplied by the Apache Xalan

 project. The following notice covers the Xalan jar files:

 

@@ -165,5 +180,3 @@
      - software copyright (c) 1999, Sun Microsystems., http://www.sun.com.

      - software copyright (c) 2000 World Wide Web Consortium, http://www.w3.org

 

-=========================================================================

-


diff --git a/derby/org.apache.derby/RELEASE-NOTES.html b/derby/org.apache.derby/RELEASE-NOTES.html
index cc587f8..ab1a99e 100644
--- a/derby/org.apache.derby/RELEASE-NOTES.html
+++ b/derby/org.apache.derby/RELEASE-NOTES.html

@@ -1,11 +1,11 @@
-<html>

-<title>Release Notes for Derby 10.5.1.1</title>

+<html lang="en">

+<title>Release Notes for Apache Derby 10.8.2.2</title>

 <body>

 <h1>

-<a name="Release Notes for Derby 10.5.1.1"></a>Release Notes for Derby 10.5.1.1</h1>

-<blockquote>

-<p>These notes describe the difference between Derby release 10.5.1.1 and the preceding release 10.4.2.0.</p>

-</blockquote>

+<a name="Release Notes for Apache Derby 10.8.2.2"></a>Release Notes for Apache Derby 10.8.2.2</h1>

+<div>

+<p>These notes describe the difference between Apache Derby release 10.8.2.2 and the preceding release 10.8.1.2.</p>

+</div>

 <ul>

 <li>

 <a href="#Overview">Overview</a>

@@ -22,17 +22,25 @@
 <li>

 <a href="#Build Environment">Build Environment</a>

 </li>

+<li>

+<a href="#Verifying Releases">Verifying Releases</a>

+</li>

 </ul>

 <h2>

 <a name="Overview"></a>Overview</h2>

-<blockquote>

+<div>

+

 

 <p>

-Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs.

+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>

 

 

 <p>

+Apache Derby is a pure Java relational database engine using standard SQL and

+JDBC as its APIs. More information about Derby can be found on the

+<a href="http://db.apache.org/derby/">Apache web site</a>.

 Derby functionality includes:

 </p>

 

@@ -49,1320 +57,412 @@
 

 </ul>

 

-</blockquote>

-<h2>

-<a name="New Features"></a>New Features</h2>

-<blockquote>

 

 <p>

-This is a feature release. The following features were added.

+Java and JDBC versions supported:

 </p>

 

 <ul>

-

-<li>

-

-<b>SQL Roles</b> - SQL roles (as described in SQL 2003 and errata) are useful for administering privileges for groups of users. Administering roles is generally less error-prone than administering privileges for individual users. SQL Roles are defined in Feature T331 "Basic roles" and Feature T332 "Extended roles". Derby 10.5 implements a subset of T331, plus support for CURRENT_ROLE, which is a part of T332.

-</li>

-

-<li>

-

-<b>Generated Columns</b> - Generated Columns is a feature which instructs Derby to fill a column with an expression built out of other columns in the row. Derby constructs these column values at INSERT and UPDATE time. The user declares indexes on these columns. This in turn improves SELECT performance since it lets users declare indexes on pre-computed pieces of the WHERE clause. This feature satisfies support for SQL Feature T175.

-</li>

-

-<li>

-

-<b>LOB Improvements</b> - There were many performance and usability improvements for BLOBs and CLOBs.  

-</li>

-

-<li>

-

-<b>Replication of encrypted databases</b> - With 10.5 it is possible to replicate encrypted databases. 

-</li>

-

-<li>

-

-<b>OFFSET/FETCH FIRST</b> - SQL 2008 has added new syntax to support a direct way to limit the 

-returned set of rows in a result set, through the fetch first and offset clauses. 

-</li>

-

-<li>

-

-<b>In-memory back end</b> - Initial implementation of a storage engine for Derby where all data is kept in memory. There is no documentation for this feature. This functionality itself is not yet fully implemented, but users are welcome to experiment with it. For details, see the

-<a href="http://wiki.apache.org/db-derby/InMemoryBackEndPrimer">Primer for In-memory Back Ends</a>.

-</li>

-

-<li>

-

-<b>Standard ALTER COLUMN syntax</b> - Allow standard SQL "SET" keyword in ALTER COLUMN syntax, like so:

- "ALTER TABLE ALTER [COLUMN] columnname SET DEFAULT default-value"

-</li>

-

-<li>

-

-<b>SYSCS_UTIL.SYSCS_UPDATE_STATISTICS</b> - New system procedure that updates cardinality statistics (or creates them if they do not exist) for a table's index or for all the indexes on a table, allowing a user to ensure that a query plan based on the most recent state of the table can be created.

-</li>

+  

+<li>Java SE 1.4 and higher with

+    JDBC 2.1, 3.0, 4.0 and 4.1</li>

+  

+<li>Java ME CDC/Foundation Profile 1.1 with

+    JSR-169 JDBC Optional Package for CDC/Foundation Profile.</li>

 

 </ul>

 

-</blockquote>

+</div>

+<h2>

+<a name="New Features"></a>New Features</h2>

+<div>

+

+

+<p>

+This is a bug fix release. No new features were added.

+</p>

+

+

+</div>

 <h2>

 <a name="Bug Fixes"></a>Bug Fixes</h2>

-<blockquote>

-<p>The following issues are addressed by Derby release 10.5.1.1. These issues are not addressed in the preceding 10.4.2.0 release.</p>

+<div>

+<p>The following issues are addressed by Derby release 10.8.2.2. These issues are not addressed in the preceding 10.8.1.2 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-4148">DERBY-4148</a></td><td>NullPointerException in system.sttest run with 10.5.1.0</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5452">DERBY-5452</a></td><td>Possible NPE in NsTest.printException()</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4146">DERBY-4146</a></td><td>Cannot insert row when a generated column references an identity column</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5448">DERBY-5448</a></td><td>In the 10.8 branch, back out the concurrency improvements introduced by using SequenceUpdaters to allocate identity values.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4145">DERBY-4145</a></td><td>NullPointerException on CREATE TABLE when generated column depends on another generated column</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5447">DERBY-5447</a></td><td>Deadlock in AutomaticIndexStatisticsTest.testShutdownWhileScanningThenDelete (BasePage.releaseExclusive and Observable.deleteObserver (BaseContainerHandle))</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4141">DERBY-4141</a></td><td>XAExceptions thrown by Derby can have errorCode 0</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5445">DERBY-5445</a></td><td>Enhance existing concurrency test to stress sequence generators to also stress identity columns</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4135">DERBY-4135</a></td><td>Failure in BlobClob4BlobTest due to wrong results being returned</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5444">DERBY-5444</a></td><td>SpawnedProcess.complete may fail to destroy the process when a timeout is specified</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4128">DERBY-4128</a></td><td>Failure in ServerPropertiesTest due to java.security.AccessControlException on the server side, in 10.4 to 10.5.1. soft upgrade mode</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5438">DERBY-5438</a></td><td>Empty MAPS table in toursdb</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4127">DERBY-4127</a></td><td>ArrayIndexOutOfBoundsException in DatabaseMetaDataTest when run in Soft Upgrade mode</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5426">DERBY-5426</a></td><td>Improve the error raised by too much contention on a sequence/identity.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4126">DERBY-4126</a></td><td>You can't invoke a table function which is stored in a jar file inside the database</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5421">DERBY-5421</a></td><td>NullPointerException during system.nstest.utils.Dbutil.update_one_row</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4125">DERBY-4125</a></td><td>The in-memory storage back end doesn't work on Windows</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5419">DERBY-5419</a></td><td>Make Derby run on Oracle Java ME Embedded Client</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4122">DERBY-4122</a></td><td>ClassCastException in SQLClob when running in soft upgrade mode (10.4.2.0 -&gt; 10.5.1.0)</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5418">DERBY-5418</a></td><td>Network server session's close method neglects to close down any open trace file</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4121">DERBY-4121</a></td><td>Documentation: more UPDATE_STATISTICS fixes needed for Reference Manual and Tuning Derby</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5414">DERBY-5414</a></td><td>SysDiagVTIMappingTest.test_5391() failed: java.text.ParseException: Unparseable date: "Thu Sep 15 14:00:16 CEST 2011"</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4119">DERBY-4119</a></td><td>Compress on a large table fails with IllegalArgumentException - Illegal Capacity</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5413">DERBY-5413</a></td><td>NetworkServerControl#main can exit with status 1 without printing an error message to console</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4117">DERBY-4117</a></td><td>dblook script fails when URL contains special characters</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5412">DERBY-5412</a></td><td>MemoryLeakFixesTest.testRepeatedDatabaseCreationWithAutoStats() fails on phoneME: java.lang.InternalError: Number of class names exceeds vm limit.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4116">DERBY-4116</a></td><td>SYSCS_UTIL.SYSCS_UPDATE_STATISTICS should update the store estimated row count for the table</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5409">DERBY-5409</a></td><td>GrantRevokeDDLTest fails under Java 7</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4104">DERBY-4104</a></td><td>Documentation: update documentation files to 10.5</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5408">DERBY-5408</a></td><td>parameters for message 2200H - sequence generator does not cycle - is out of sync in non-English messages</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4103">DERBY-4103</a></td><td>Allow unlimited growth for in-memory conglomerates</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5404">DERBY-5404</a></td><td>Document DBO restriction for four diagnostic VTIs</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4096">DERBY-4096</a></td><td>'testRunTimeStatistics(org.apache.derbyTesting.functionTests.tests.lang.OffsetFetchNextTest)junit.framework.AssertionFailedError' on Windows</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5402">DERBY-5402</a></td><td>Assignment instead of comparison in Driver20.getPropertyInfo</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4095">DERBY-4095</a></td><td>Trigger  fails with ERROR 38000: The exception 'java.sql.SQLException: ResultSet not open  during VTIResultSet.getNextRowCore()</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5398">DERBY-5398</a></td><td>NullPointerException in storemore/bug3498.sql</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4094">DERBY-4094</a></td><td>Enforce absolute paths in the in-memory back end internal storage structure</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5396">DERBY-5396</a></td><td>DRDAStatement and DRDAConnThread swallow IOExceptions</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4093">DERBY-4093</a></td><td>Improve handling of the database temporary directory</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5395">DERBY-5395</a></td><td>By default, only the DBO should be allowed to run several of the diagnostic VTIs.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4088">DERBY-4088</a></td><td>DDMReader readBytes ArrayIndexOutOfBoundsException</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5394">DERBY-5394</a></td><td>Reduce chance of OOME with XAMemTest.testDerby4137_TransactionTimeoutSpecifiedNotExceeded in low memory suite</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4084">DERBY-4084</a></td><td>Determine the subSubProtocol name for the in-memory back end</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5393">DERBY-5393</a></td><td>Remove old in-memory database purge mechanism</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4079">DERBY-4079</a></td><td>Add support for SQL:2008 &lt;result offset clause&gt; and &lt;fetch first clause&gt; to limit result set cardinality</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5391">DERBY-5391</a></td><td>The syscs_diag.error_log_reader() and syscs_diag.statement_duration() vtis do not work on derby error logs created since 10.7.1</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4078">DERBY-4078</a></td><td>Document the SQL Standard routine matching rules which Derby now supports</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5390">DERBY-5390</a></td><td>NPE in BasicDatabase.stop in replication slave mode (dd.clearSequenceCaches)</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4073">DERBY-4073</a></td><td>Creation/configuration of ClientXDataSource fails because of two setSsl methods</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5389">DERBY-5389</a></td><td>SequenceGeneratorTest failures with weme 6.2 sane build ASSERT FAILED Identity being changed on a live cacheable</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4072">DERBY-4072</a></td><td>shutdown with incorrect permission on log files shows java.lang.NullPointerException  at org.apache.derby.impl.store.raw.log.LogToFile.flush(LogToFile.java:3964).  Should give bettter message.</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5385">DERBY-5385</a></td><td>Improve documentation for OFFSET/FETCH NEXT</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4071">DERBY-4071</a></td><td>AssertFailure when selecting rows from a table with CHARACTER and VARCHAR columns</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5384">DERBY-5384</a></td><td>Reference Guide talks about a DriverManager method which does not exist.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4063">DERBY-4063</a></td><td>Constraint causes wrong query result when using exists</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5376">DERBY-5376</a></td><td>Documentation should state authentication/authorization requirements more strongly</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4061">DERBY-4061</a></td><td>InputStream returned from Blob.getBinaryStream(long, long) terminates the stream by returning 0, should return -1</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5372">DERBY-5372</a></td><td>Need to document that the != and &lt;&gt; operators are pushed into Restricted table functions (once the work on DERBY-5369 wraps up)</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4060">DERBY-4060</a></td><td>Blob.getBinaryStream(long,long) is off by one for the pos+len check</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5367">DERBY-5367</a></td><td>Stale data retrieved when using new collation=TERRITORY_BASED:PRIMARY feature</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4059">DERBY-4059</a></td><td>If space reclamation cannot obtain container lock it will not retry getting the lock</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5362">DERBY-5362</a></td><td>HTML frameset files lack closing newline character</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4050">DERBY-4050</a></td><td>Multithreaded clob update causes growth in table that does not get reclaimed</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5361">DERBY-5361</a></td><td>Document use of URLs with SQLJ.INSTALL_JAR</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4049">DERBY-4049</a></td><td>SELECT statement topic in Reference Manual should reflect current WHERE clause behavior</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5354">DERBY-5354</a></td><td>Remove unnecessary dita.regex build target</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4048">DERBY-4048</a></td><td>Update Statistics code in AlterTableConstantAction should use execute transaction rather than compile transaction</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5352">DERBY-5352</a></td><td>Derby table functions stored in a jar file inside the database which implement VTICosting or RestrictedVTI fail with ClassNotFoundException</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4042">DERBY-4042</a></td><td>org.apache.derby.impl.load.Import needs to escape single quotes</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5350">DERBY-5350</a></td><td>Devguide needs update for definer's rights</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4040">DERBY-4040</a></td><td>SQLChar.getLength returns wrong length for some data values</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5339">DERBY-5339</a></td><td>Sample domain names should follow RFC 2606 conventions</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4028">DERBY-4028</a></td><td>two rows can be inserted with the same value in a column that a unique constraint on that column should prevent</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5336">DERBY-5336</a></td><td>Repeated database creation causes OutOfMemoryError</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4027">DERBY-4027</a></td><td>An attempt was made to access an out of range slot on a page</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5334">DERBY-5334</a></td><td>Incorrect permission arguments given for SYSCS_UTIL.SYSCS_SET_USER_ACCESS</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4025">DERBY-4025</a></td><td>CHAR data type documentation fails to describe the maximum allowed length</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5333">DERBY-5333</a></td><td>Intermittent assert failure in testInterruptShutdown: thread's interrupted flag lost after shutdown</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4024">DERBY-4024</a></td><td>Replace felix.jar file with the felix sources</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5331">DERBY-5331</a></td><td>Incorrect use of CharsetEncoder in DDMWriter</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4022">DERBY-4022</a></td><td>Remove dependency of junit targets on deprecated jdk16 variable</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5329">DERBY-5329</a></td><td>Document who is allowed to run which system procedures/functions.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4017">DERBY-4017</a></td><td>Removed deprecated jdk16 variable from the machinery which builds javadoc</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5325">DERBY-5325</a></td><td>Checkpoint fails with ClosedChannelException in InterruptResilienceTest</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4016">DERBY-4016</a></td><td>Document syntax change for ALTER TABLE in Reference Manual</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5318">DERBY-5318</a></td><td>Use assertDirectoryDeleted in ReplicationRun and remove dead code</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4014">DERBY-4014</a></td><td>Update Derby Jira Report XML VTI to access more fields</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5314">DERBY-5314</a></td><td>Enable i18n tests in non-English locales</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4013">DERBY-4013</a></td><td>Allow standard SQL syntax: ALTER TABLE ALTER [COLUMN] &lt;col&gt; SET DEFAULT &lt;default&gt;</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5312">DERBY-5312</a></td><td>InterruptResilienceTest failed with ERROR 40XD1: Container was opened in read-only mode.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4012">DERBY-4012</a></td><td>'largedata/LobLimits.java' fails with "EXPECTED SQL Exception: (XJ001) Java exception: 'A truncation error was encountered trying to shrink CLOB 'XXXX' to length 104857600.: org.apache.derby.iapi.services.io.DerbyIOException'."</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5307">DERBY-5307</a></td><td>Document the behavior of the derby.language.sequence.preallocator property.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4010">DERBY-4010</a></td><td>PassThroughException should not reimplement initCause()/getCause()</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5304">DERBY-5304</a></td><td>test_derby_4779 (lang.GeneratedColumnsTest) fails with ibm 1.4.2; ERROR 42X50; No method was found that matched the method call java.lang.Integer.signum(int)</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4008">DERBY-4008</a></td><td>Only send RDBNAM on ACCSEC if EBCDIC conversion is possible</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5299">DERBY-5299</a></td><td>Document what you should expect to see if you enable authentication/authorization on a database which was created without those safeguards.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4006">DERBY-4006</a></td><td>ALTER COLUMN ... WITH DEFAULT NULL does not change the default</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5292">DERBY-5292</a></td><td>SQLAuthorisation and views</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-4004">DERBY-4004</a></td><td> Remove required RDBNAM from ACCSEC. Use SECCHK RDBNAM if none is provided on ACCSEC</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5291">DERBY-5291</a></td><td>test failure: NullPointerException with J2ME (weme 6.2) in testDerby4137_TransactionTimeoutSpecifiedNotExceeded(org.apache.derbyTesting.functionTests.tests.memory.XAMemTest)</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3997">DERBY-3997</a></td><td>ORDER BY causes column to be returned</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5289">DERBY-5289</a></td><td>Unable to boot 10.5.1.1 database - fails during soft/hard upgrade process for a new version number while trying to drop jdbc metadata</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3996">DERBY-3996</a></td><td>Change eol style to native on jsr169 stubs</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5284">DERBY-5284</a></td><td>A derby crash at exactly right time during a btree split can cause a corrupt db which can not be booted.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3990">DERBY-3990</a></td><td>ResultSetStreamTest fails on case sensitive file systems, and isn't run as part of any suite</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5280">DERBY-5280</a></td><td>Large batch of DDL in a database procedure dies on a transaction severity error.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3989">DERBY-3989</a></td><td>Set the Java 5 compilation path based on the Java 6 compilation path if a Java 5 environment can't be found but a Java 6 environment can be</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5278">DERBY-5278</a></td><td>AssertionFailedError in IndexSplitDeadlockTest.testBTreeForwardScan_fetchRows_resumeAfterWait_unique_split()</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3988">DERBY-3988</a></td><td>Set the Java 6 complilation path based on the Java 5 compilation path so that the JDBC4 support is always built</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5276">DERBY-5276</a></td><td>Reference manual has wrong length for BIGINT columns in system tables</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3985">DERBY-3985</a></td><td>Replace BUILDING.txt with a simlified up-to-date BUILDING.html</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5274">DERBY-5274</a></td><td>getColumns() doesn't work with auto generated identity columns that start with large numbers</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3984">DERBY-3984</a></td><td>Separate out the small number of build targets which really require JDK1.4 features from the bulk of the targets which ought to compile cleanly against small device libraries</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5271">DERBY-5271</a></td><td>Client may hang if the server crashes due to a java.lang.Error</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3983">DERBY-3983</a></td><td>User Guide documentation on the limitations of small-device support is stale</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5264">DERBY-5264</a></td><td>OOM issue using XA with timeouts with Java 1.4</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3982">DERBY-3982</a></td><td>Add a facility to override the default set of old versions to be tested in the upgrade tests.</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5262">DERBY-5262</a></td><td>Running JUnit tests with Java 1.4.2 fails if the package private tests are on the classpath</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3981">DERBY-3981</a></td><td>Improve distribution of hash codes in SQLBinary and SQLChar</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5258">DERBY-5258</a></td><td>btree post commit releases latch before committing/aborting purges, possibly allowing other operation on page</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3978">DERBY-3978</a></td><td>Clob.truncate(long) in the client driver doesn't update the cached Clob length</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5255">DERBY-5255</a></td><td>Fix more difficult table problems</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3977">DERBY-3977</a></td><td>Clob.truncate with a value greater than the Clob length raises different exceptions in embedded and client driver</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5254">DERBY-5254</a></td><td>The keywords introduced by the CREATE SEQUENCE work are treated as reserved rather than unreserved.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3975">DERBY-3975</a></td><td>SELECT DISTINCT may return duplicates with territory-based collation</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5253">DERBY-5253</a></td><td>Engine code references org.apache.derby.shared.common.sanity.SanityManager</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3972">DERBY-3972</a></td><td>Update test harness to run with DesktopEE JRE</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5252">DERBY-5252</a></td><td>make GrantRevokeTest pass in non-English locale</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3970">DERBY-3970</a></td><td>PositionedStoreStream doesn't initialize itself properly</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5251">DERBY-5251</a></td><td>make ErrorCodeTest pass in non-English locale</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3969">DERBY-3969</a></td><td>NPE if you declare a constraint on a generated column and omit the datatype</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5249">DERBY-5249</a></td><td>A table created with 10.0.2.1 with constraints cannot be dropped with 10.5 due to NullPointerException with insane build or ASSERT FAILED Failed to find sharable conglomerate descriptor for index conglomerate  with sane build</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3966">DERBY-3966</a></td><td>Do not require JRE 1.4 libraries at compile time since SUN's JDK 1.4 went out of support and can be used on JRE 1.4 without any problem</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5247">DERBY-5247</a></td><td>Warnings regarding XPath displayed when generating JavaDoc</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3964">DERBY-3964</a></td><td>NullPointerException when re-evaluating generated column during ON DELETE SET NULL referential action</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5243">DERBY-5243</a></td><td>assert failure in test testRAFReadWriteMultipleThreads: interrupted flag cleared</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3959">DERBY-3959</a></td><td>Reference Manual needs information on generated columns</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5239">DERBY-5239</a></td><td>Remove usages of DriverManager to obtain an Embedded Connection in Derby Server</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3958">DERBY-3958</a></td><td>ImportExportProcedures imports ./testData/ImportExport/position_info.del using US-ASCII but the file contains non-ascii characters</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5238">DERBY-5238</a></td><td>VARCHAR size typos in some documentation topics</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3956">DERBY-3956</a></td><td>Remove method TemplateRow.checkPartialColumnTypes</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5236">DERBY-5236</a></td><td>Client driver silently truncates strings that exceed 32KB</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3950">DERBY-3950</a></td><td>You should get an error if you try to override a generated column via an INSERT driven by an inner ResultSet</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5233">DERBY-5233</a></td><td>Interrupt of create table or index (i.e. a container) will throw XSDF1 under NIO - connection survives</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3948">DERBY-3948</a></td><td>Don't allow references to generated columns in the NEW transition variables of triggered actions of BEFORE triggers</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5226">DERBY-5226</a></td><td>SQLJ system procedures should be documented in Reference Manual</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3945">DERBY-3945</a></td><td>Generation clauses which mention user-coded functions may produce different resuls depending on who performs the triggering INSERT/UPDATE</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5223">DERBY-5223</a></td><td>Thread's interrupted flag not always preserved after Derby returns from JDBC API call</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3943">DERBY-3943</a></td><td>testReplication_Local_3_p2_StateTests_smallInsert_immediateStopMaster_DISABLED() causes hang in teardown()</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5222">DERBY-5222</a></td><td>Compatibility tests fail to delete database directory</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3938">DERBY-3938</a></td><td>Document that you can change the length of varbinary as well as varchar columns</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5217">DERBY-5217</a></td><td>make ImportExportIJTest pass in non-English locale</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3936">DERBY-3936</a></td><td>Add CharacterStreamDescriptor</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5215">DERBY-5215</a></td><td>Localize messages introduced or changed in 10.7 and 10.8</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3935">DERBY-3935</a></td><td>Introduce interface for a position aware stream</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5212">DERBY-5212</a></td><td>Reference Manual: language on authentication/authorization needs changes for several URL attribute topics</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3934">DERBY-3934</a></td><td>Improve performance of reading modified Clobs</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5211">DERBY-5211</a></td><td>Make SysinfoCPCheckTest pass in non-English locale</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3932">DERBY-3932</a></td><td>Add tests of generated columns when sql authorization is turned on</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5205">DERBY-5205</a></td><td>Documentation: toc.html files need lang attribute</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3931">DERBY-3931</a></td><td>GeneratedColumnsTest fails with "'F_MINUS' is not recognized as a function or procedure." on cvm/phoneME</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5204">DERBY-5204</a></td><td>Misplaced p tags in release notes</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3930">DERBY-3930</a></td><td>SQL roles: Add VTI for CONTAINED_ROLES</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5203">DERBY-5203</a></td><td>Documentation of drop=true attribute contains error</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3923">DERBY-3923</a></td><td>Make the datatype optional when declaring columns with generation clauses</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5198">DERBY-5198</a></td><td>XPLAIN table documentation needs some cleanup</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3922">DERBY-3922</a></td><td>Enable the adding of generated columns via ALTER TABLE</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5191">DERBY-5191</a></td><td>Documentation needed for connection URL attribute retrieveMessageText</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3917">DERBY-3917</a></td><td>RolesConferredPrivilegesTest  fails with  'java.lang.NoClassDefFoundError: java.sql.DriverManager'  with weme 6.1</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5184">DERBY-5184</a></td><td>Tables in documentation need introductions and formatting fixes</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3911">DERBY-3911</a></td><td>BTreeController.reclaim_deleted_rows() may hide exceptions</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5158">DERBY-5158</a></td><td>Incomprehensible error message on client if attempting rollback after database has been shut down.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3909">DERBY-3909</a></td><td>Race condition in NetXAResource.removeXaresFromSameRMchain()</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5120">DERBY-5120</a></td><td>Row from SYSDEPENDS gets deleted when a table has update triggers defined on it and an upate is made to the table</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3907">DERBY-3907</a></td><td>Save useful length information for Clobs in store</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5108">DERBY-5108</a></td><td>Intermittent failure in AutomaticIndexStatisticsTest.testShutdownWhileScanningThenDelete on Windows</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3905">DERBY-3905</a></td><td>Failed tests should save the database off to the fail directory</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5098">DERBY-5098</a></td><td>embedded/in-memory: SQLNonTransientConnectionException: No current connection   due to invalid page format</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3904">DERBY-3904</a></td><td>NPE on left join with aggregate</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5097">DERBY-5097</a></td><td>testMTSelect(org.apache.derbyTesting.functionTests.tests.store.AutomaticIndex StatisticsMultiTest)junit.framework.AssertionFailedError: failed to get statisti cs for table MTSEL (#expected=2, timeout=0) on AIX IBM JDK 1.5</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3903">DERBY-3903</a></td><td>'The class 'org.apache.derby.diag.EnabledRoles' does not exist or is inaccessible.' in new roles tests (DERBY-3886)</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5084">DERBY-5084</a></td><td>convert ijConnName.sql to a ScriptTest junit test</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3902">DERBY-3902</a></td><td>some messages are referenced but never used - MessageBundleTest output</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5044">DERBY-5044</a></td><td>ALTER TABLE DROP COLUMN will not detect triggers defined on other tables with their trigger action using the column being dropped</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3901">DERBY-3901</a></td><td>SQL roles: Move upgrade logic from 10.4 to 10.5</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-5014">DERBY-5014</a></td><td>Tests should restore the timeout values to default after they are done running.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3897">DERBY-3897</a></td><td>SQLSessionContext not correctly initialized in some non-method call nested contexts</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4984">DERBY-4984</a></td><td>ALTER TABLE DROP COLUMN may leave triggers invalid even if they are not using the column getting dropped.</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3895">DERBY-3895</a></td><td>Needs update of master for 'derbyall/derbynetmats/DerbyNet/derbynetmats/holdCursorJDBC30'?</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4779">DERBY-4779</a></td><td>NPE while inserting into a table which has a generated column and an insert trigger</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3894">DERBY-3894</a></td><td>Reference Manual: supported functions should be listed in JDBC escape syntax topic</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4670">DERBY-4670</a></td><td>ThreadDump class included in insane jars</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3890">DERBY-3890</a></td><td>Replication: NPE for startSlave of encrypted database</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4669">DERBY-4669</a></td><td>ClassLoaderBootTest fails if derbyclient.jar comes before derby.jar on the classpath</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3889">DERBY-3889</a></td><td>LOBStreamControl.truncate() doesn't delete temporary files</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4647">DERBY-4647</a></td><td>BaseTestCase.execJavaCmd() does not work with weme 6.2</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3886">DERBY-3886</a></td><td>SQL roles: ij show enabled and settable roles</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4637">DERBY-4637</a></td><td>The Developer's Guide implies that, for in-memory database names, Derby does not resolve relative and absolute paths to the same in-memory database</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3883">DERBY-3883</a></td><td>LOBStreamControl.replaceBytes() leaves temporary files open</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4617">DERBY-4617</a></td><td>Sysinfo.testSysinfoLocale failed with IB47 M 1.6 on Windows 7 64bit</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3880">DERBY-3880</a></td><td>NPE on a query with having clause involving a join</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4443">DERBY-4443</a></td><td>Wrap rollback in exception handlers in try-catch</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3879">DERBY-3879</a></td><td>Getting Started Guide has typo and version problems</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4408">DERBY-4408</a></td><td>missing DOCTYPE and META tags in toc.html and index.html pages</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3878">DERBY-3878</a></td><td>Replication: stopSlave does not close serversocket when master has crashed.</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4275">DERBY-4275</a></td><td>Query executions fail when compressing a table using SYSCS_UTIL.SYSCS_COMPRESS_TABLE</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3877">DERBY-3877</a></td><td>SQL roles: build support for dblook</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4260">DERBY-4260</a></td><td>Make derbynet/NetworkServerControlClientCommandTest run regardless of the locale</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3875">DERBY-3875</a></td><td>Derby cannot replace a database after encountering corruption</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4200">DERBY-4200</a></td><td>client side OutOfMemoryError running derbnetclientmats:jdbcapi/derbyStress</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3874">DERBY-3874</a></td><td>Document numeric function ATAN2(float1,float2)</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-4137">DERBY-4137</a></td><td>OOM issue using XA with timeouts</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3872">DERBY-3872</a></td><td>NullPoinerException thrown when INTEGER function used as a predicate in a WHERE clause of a SELECT .. GROUP BY ..  HAVING statement</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-3870">DERBY-3870</a></td><td>Concurrent Inserts of rows with XML data results in an exception</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3871">DERBY-3871</a></td><td>EmbedBlob.setBytes returns incorrect insertion count</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-3337">DERBY-3337</a></td><td>convert jdbcapi/derbyStress.java to JUnit</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3869">DERBY-3869</a></td><td>intermittent hang pinging  server on Linux</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-2625">DERBY-2625</a></td><td>SEVERE error involving column-width property</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3865">DERBY-3865</a></td><td>NPE in testSemantics(.....lang.RolesTest) on JavaME / CVM</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-2623">DERBY-2623</a></td><td>SEVERE error involving column-number property</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3864">DERBY-3864</a></td><td>Remove utility class PrivilegedFileOps</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-2254">DERBY-2254</a></td><td>Assert during log file switch: log file position exceeded max log file size</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3863">DERBY-3863</a></td><td>improve test importExportIJ.sql</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-1903">DERBY-1903</a></td><td>Convert  largedata/LobLimits.java to junit</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3859">DERBY-3859</a></td><td>Reset the current role when EmbedPooledConnection creates a new logical connection</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-1780">DERBY-1780</a></td><td>Document all supplied system procedures in the Server and Administration Guide (e.g. class loading utils and import/export)</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3855">DERBY-3855</a></td><td>The Tuning guide should mention that LIKE transformations/optimizations are disabled when using territory-based collations</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-1046">DERBY-1046</a></td><td>JVMInfo is duplicated in derbyclient.jar</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3850">DERBY-3850</a></td><td>Remove unneeded workarounds for DERBY-177 and DERBY-3693</td>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-484">DERBY-484</a></td><td>Documentation for derby.database.classpath in developers guide is misleading</td>

 </tr>

 <tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3847">DERBY-3847</a></td><td>Tuning Guide lacks information on turning off Derby property settings</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3845">DERBY-3845</a></td><td>Problems running  org.apache.derbyTesting.system.optimizer.RunOptimizerTest</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3841">DERBY-3841</a></td><td>'testTimeSlice_*(NetworkServerControlApiTest.java)' fails on Jvm1.5/vista, Jvm1.4/SunOS 5.11</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3840">DERBY-3840</a></td><td>The test code executes java processes by just executing java instead of using a full path. This may cause the wrong java to be picked up.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3837">DERBY-3837</a></td><td>need to test getting appropriate error message when os files are read-only</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3835">DERBY-3835</a></td><td>Convert derbynet/getCurrentProperties to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3832">DERBY-3832</a></td><td>Convert derbynet/timeslice.java to Junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3831">DERBY-3831</a></td><td>RuntimeStatisticsParser can not distinguish names of table or index well and truly</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3828">DERBY-3828</a></td><td>Convert jdbcapi/SURTest_ij.sql to JUnit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3827">DERBY-3827</a></td><td>Add Apache 2.0 license headers to a number of files</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3826">DERBY-3826</a></td><td>Remove the update-with-jdbc4 script, which is dead code now</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3825">DERBY-3825</a></td><td>StoreStreamClob.getReader(charPos) performs poorly</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3818">DERBY-3818</a></td><td>client Insert/retrieval of 18MB  Clob is extremely slow  in MultiByteClobTest</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3816">DERBY-3816</a></td><td>Administration Guide topics on unsupported DB2 driver should be removed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3813">DERBY-3813</a></td><td>Derby tests for the existance of BigDecimal methods toPlainString and bdPrecison but does not check if they were found before using them.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3812">DERBY-3812</a></td><td>failure in testAttributeDrdaStreamOutBufferSize(org.apache.derbyTesting.functionTests.tests.management.NetworkServerMBeanTest)junit.framework.AssertionFailedError: expected:&lt;0&gt; but was:&lt;131072&gt;</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3810">DERBY-3810</a></td><td>Create a simple Clob performance regression test</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3807">DERBY-3807</a></td><td>traces of removed ij functionality of ij.unicodeEscape should be removed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3805">DERBY-3805</a></td><td>Create a simple Blob performance regression test</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3803">DERBY-3803</a></td><td>'org.apache.derbyTesting.functionTests.tests.lang.XMLTypeAndOpsTest' failures on JVM 1.5 on trunk, 10.4 and 10.3</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3802">DERBY-3802</a></td><td>Convert "org.apache.derbyTesting.functionTests.tests.lang.optimizerOverrides.sql" to junit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3800">DERBY-3800</a></td><td>Convert derbynet/maxthreads to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3799">DERBY-3799</a></td><td>NullPointerException when accessing a clob through a pooled connection</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3798">DERBY-3798</a></td><td>Remove unnecessary call to Hashtable.get() in TableScanResultSet.getNextRowCore()</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3797">DERBY-3797</a></td><td>Convert jdbcapi/metadataMultiConn to JUnit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3796">DERBY-3796</a></td><td>Convert derbynet/OutBufferedStream to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3793">DERBY-3793</a></td><td>Remove unnecessary methods from InternalClob interface</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3791">DERBY-3791</a></td><td>Excessive memory usage when fetching small Clobs</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3787">DERBY-3787</a></td><td>Document the new system stored procedure SYSCS_UTIL.SYSCS_UPDATE_STATISTICS which was added as part of DERBY-269</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3786">DERBY-3786</a></td><td>Assert failure in CacheEntry.unkeepForRemove when running stress.multi</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3784">DERBY-3784</a></td><td>ImportExportTest doesn't detect lack of expected errors</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3783">DERBY-3783</a></td><td>LOBStreamControl shouldn't throw SQLException</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3782">DERBY-3782</a></td><td>Client Configuration.java imports engine class  org.apache.derby.iapi.services.info.JVMInfo</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3781">DERBY-3781</a></td><td>PositionedStoreStream.reposition(pos) with pos greater than length leaves the stream object in an inconsistent state</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3780">DERBY-3780</a></td><td>Run junit tests with -Dfile.encoding="UTF-16" to expose encoding issues and analyze failures</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3779">DERBY-3779</a></td><td>Add client side JDBC statement pool documentation</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3777">DERBY-3777</a></td><td>SecureServerTest, SSLTest are failed on Zos with exit code 143 starting network server</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3776">DERBY-3776</a></td><td>testGetBytes under BlobClob4BlobTest failed on Zos  with encoding issue</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3775">DERBY-3775</a></td><td>BlobStoredProcedureTest failed on Zos: AssertionFailedError: Error SYSIBM.BLOBGETPOSITIONFROMLOCATOR returns the wrong value for the position of the Blob  expected:&lt;8&gt; but was:&lt;-1&gt;</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3774">DERBY-3774</a></td><td>jdbc4/ClobTest fails on Zos with AssertionFailedError: Streams differ at index 0 expected:&lt;200&gt; but was:&lt;72&gt;</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3773">DERBY-3773</a></td><td>ImportExportLobTest failed on Zos  Clobs differ at index 1 expected:&lt;99&gt; but was:&lt;196&gt;</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3771">DERBY-3771</a></td><td>testClasspathChecker under SysinfoCPCheckTest failed on Zos</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3770">DERBY-3770</a></td><td>Create a utility class for skipping data in an InputStream</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3769">DERBY-3769</a></td><td>Make LOBStoredProcedure on the server side smarter about the read buffer size</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3768">DERBY-3768</a></td><td>Make EmbedBlob.length use skip instead of read</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3767">DERBY-3767</a></td><td>Convert "org.apache.derbyTesting.functionTests.tests.lang.nulls.sql" to junit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3766">DERBY-3766</a></td><td>EmbedBlob.setPosition is highly ineffective for streams</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3764">DERBY-3764</a></td><td>Union Query fail on Derby 10.4.1.3</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3763">DERBY-3763</a></td><td>Rename BaseJDBCTestCase.usingDerbyNet</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3762">DERBY-3762</a></td><td>Convert "org.apache.derbyTesting.functionTests.tests.lang.arithmetic.sql" to junit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3760">DERBY-3760</a></td><td>Convert "org.apache.derbyTesting.functionTests.tests.lang.miscerrors.sql" to junit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3759">DERBY-3759</a></td><td>Convert "org.apache.derbyTesting.functionTests.tests.lang.ungroupedAggregatesNegative.sql" to junit.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3758">DERBY-3758</a></td><td>Convert "org.apache.derbyTesting.functionTests.tests.lang.precedence.sql" to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3755">DERBY-3755</a></td><td>ij's help text lacks the optional [HOLD | NOHOLD] syntax for GET CURSOR</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3754">DERBY-3754</a></td><td> Convert "org.apache.derbyTesting.functionTests.tests.lang.connect.sql" to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3751">DERBY-3751</a></td><td>Convert case.sql to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3750">DERBY-3750</a></td><td>Convert  "org.apache.derbyTesting.functionTests.tests.lang.constant Expression.sql" to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3745">DERBY-3745</a></td><td>Derby can leak classloaders in an app server environment</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3743">DERBY-3743</a></td><td>Revoking EXECUTE privilege on a function if used in a CHECK constraint: implementation problem</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3742">DERBY-3742</a></td><td>Move test code from CompressedNumber to a unit test</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3741">DERBY-3741</a></td><td>SQL LENGTH function materializes CLOB into memory</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3739">DERBY-3739</a></td><td>Skip and read methods in ArrayInputStream may overflow</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3738">DERBY-3738</a></td><td>Add more tests for legal/illegal commands in the different replication states</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3736">DERBY-3736</a></td><td>Revoking a column level privilege from a user, a prepared statement relying on that privilege can still be executed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3735">DERBY-3735</a></td><td>Incorrect position calculation in PositionedStoreStream with read(byte[],...)</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3734">DERBY-3734</a></td><td>Maximum value allowed for derby.storage.fileCacheSize (100) is too low for large system.  Increase the maximum value and redocument the property.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3732">DERBY-3732</a></td><td>SQL Length function materializes BLOB  into memory</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3731">DERBY-3731</a></td><td>Improve calculation of refSize in ClassSize.java</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3730">DERBY-3730</a></td><td>Bundle-SymbolicName: needed in Derby manifest for OSGi 4 environment</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3728">DERBY-3728</a></td><td>Fix error handling in PrivilegedFileOpsForTests</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3726">DERBY-3726</a></td><td>Don't call RAFContainer.padFile() from instances of RAFContainer4</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3725">DERBY-3725</a></td><td>add more information to the XSDB1:ERROR XSDB1: Unknown page format at page  error</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3723">DERBY-3723</a></td><td>Reset current schema to default (user name) when creating a new logical connection in the client driver</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3722">DERBY-3722</a></td><td>Add circularity check for the GRANT role statement</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3718">DERBY-3718</a></td><td>NPE when firing a trigger</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3717">DERBY-3717</a></td><td>convert derbynet/getCurrentProperties.java to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3715">DERBY-3715</a></td><td>java/testing/README.htm refers to a non-existing test</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3711">DERBY-3711</a></td><td>convert store/aes.sql to junit test &amp; add unrestricted test cases.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3708">DERBY-3708</a></td><td>setting tracedirectory from the command line does not work</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3707">DERBY-3707</a></td><td>STATUS file changes June 2008</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3706">DERBY-3706</a></td><td>NetworkServer console messages should print a time stamp</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3705">DERBY-3705</a></td><td>In Net Client mode, negative values for stream length are accepted without an exception for PreparedStatement.setAsciiStream()</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3704">DERBY-3704</a></td><td>If an IOException is encountered during establishment of the connection, Network Server should print the root exception to the console instead of a generic message</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3703">DERBY-3703</a></td><td>Make it possible to build the JSR169 support with the jdk1.4 libraries</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3702">DERBY-3702</a></td><td>Remove xml-apis.jar because we no longer have to compile against jdk1.3</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3701">DERBY-3701</a></td><td>java.lang.Exception: DRDA_UnableToAccept.S:Unable to accept connections and client hang if tracing is turned on but traceDirectory does not exist</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3700">DERBY-3700</a></td><td>Get rid of tools/java/empty.jar</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3696">DERBY-3696</a></td><td>Delete superfluous test lang/longStringColumn.java</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3695">DERBY-3695</a></td><td>NullPointerException when invoking statement event listeners if one of the listeners is null</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3694">DERBY-3694</a></td><td>'Method resolution for signature java.lang.String.valueOf(int) was ambiguous. (No single maximally specific method.)' in 'testFunctionNullHandling(org.apache.derbyTesting.functionTests.tests.lang.RoutineTest)'  on JavaME</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3693">DERBY-3693</a></td><td>Deadlocks accessing DB metadata</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3692">DERBY-3692</a></td><td>'javax.transaction.xa.XAException' ++  in  'J2EEDataSourceTest'</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3690">DERBY-3690</a></td><td>EmbedPooledConnection doesn't reset schema when creating a new logical connection</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3686">DERBY-3686</a></td><td>convert predicatePushdown.sql  to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3685">DERBY-3685</a></td><td>weme 6.1 Base connection pooling suitejunit.framework.AssertionFailedError: java.lang.NullPointerException</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3684">DERBY-3684</a></td><td>Wire the vti demo into the build.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3682">DERBY-3682</a></td><td>SYSCS_BULK_INSERT doesn't quote identifiers or strings properly</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3681">DERBY-3681</a></td><td>When authenticating a user at connect time, verify that the user provided is not also a defined role name.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3678">DERBY-3678</a></td><td>StackOverflowException in deadlock trace</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3674">DERBY-3674</a></td><td>'ALTER TABLE' is not allowed on the System table '"SYSCS_DIAG"."TRANSACTION_TABLE"' in derbyall - store/TransactionTable.sql</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3673">DERBY-3673</a></td><td>Add checks that a new role isn't already a user authorization id</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3668">DERBY-3668</a></td><td>Remove JDBC 3.0-specific topics from Reference Manual and merge implementation notes as needed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3667">DERBY-3667</a></td><td>SQL roles: Make CURRENT_ROLE check that the role is still valid</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3666">DERBY-3666</a></td><td>Make role descriptor a dependency Provider</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3665">DERBY-3665</a></td><td>Master file for derbynet/testProperties.java needs update for 10.3.2.2 to 10.3.3.0 version change.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3663">DERBY-3663</a></td><td>Convert store/streamingColumn to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3661">DERBY-3661</a></td><td>Typo yields redundant test case in GrantRevokeTest</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3659">DERBY-3659</a></td><td>revive tests with ldap references to be runnable as junit tests</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3658">DERBY-3658</a></td><td>LOBStateTracker should not use SYSIBM.CLOBRELEASELOCATOR when the database is soft-upgraded from 10.2</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3657">DERBY-3657</a></td><td>Comment in template security policy incorrectly says that JMX is not enabled by default</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3655">DERBY-3655</a></td><td>errror in nightly regression test: LobStreamsTest:encryptedjunit.framework.AssertionFailedError: f:\jartest\JarResults.2008-04-29\ibm16_suites.All\system\singleUse\oneuse1e\tmp\lob6165.tmp</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3653">DERBY-3653</a></td><td>Convert datetime.sql to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3652">DERBY-3652</a></td><td>Derby does not follow the SQL Standard when trying to map SQL routines to Java methods.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3649">DERBY-3649</a></td><td>can't call a stored function with an aggregate argument without getting the following error: ERROR 42Y29</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3642">DERBY-3642</a></td><td>Update and rectify the Derby tutorial</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3640">DERBY-3640</a></td><td>Add an example for table function in Derby Reference Manual</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3638">DERBY-3638</a></td><td>java/testing/Readme.htm location of derbyTesting.jar</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3633">DERBY-3633</a></td><td>tools/derbyrunjartest.java fails with 'No command given.' (expecting 'No arguments given.')</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3631">DERBY-3631</a></td><td>UDF used with aggregate arguments results in error 30000</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3629">DERBY-3629</a></td><td>Tools Guide should document continuation marker for ij</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3625">DERBY-3625</a></td><td>XSDA3 error in concateTests in lang.LangHarnessJavaTest caused by bug in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE()</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3623">DERBY-3623</a></td><td>Convert deadlockMode.java to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3622">DERBY-3622</a></td><td>SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE needs a better description in the reference manual</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3619">DERBY-3619</a></td><td>Implement more load types for org.apache.derbyTesting.perf.clients.Runner</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3618">DERBY-3618</a></td><td>Perform thread dump with ASSERTS with jdk 1.5 or higher</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3615">DERBY-3615</a></td><td>Making the instructions more clear in documentation(BUILDING.txt) regarding setting JRE lib path for a Windows system</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3613">DERBY-3613</a></td><td>SELECT DISTINCT field FROM TABLE_NAME GROUP BY field,  field2</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3612">DERBY-3612</a></td><td>Developer's Guide needs correction on garbage collection</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3602">DERBY-3602</a></td><td>If derbytesting.jar is in a different directory than the derby jars SystemPrivilegesPermissionTest fails with java.security.AccessControlException</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3601">DERBY-3601</a></td><td>Optimize LOBStateTracker for non-locator servers</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3597">DERBY-3597</a></td><td>Incorporate DERBY-3310 and DERBY-3494 write-ups into NormalizeResultSetNode javadoc</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3596">DERBY-3596</a></td><td>Creation of logical connections from a pooled connection causes resource leak on the server</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3589">DERBY-3589</a></td><td>AllocPage.createPage() doesn't initialize minimumRecordSize correctly</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3588">DERBY-3588</a></td><td>suites.All fails to run on Jvm 1.5 when built with JDK 1.5 (Failed to invoke suite(): .jdbc4._Suite)</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3587">DERBY-3587</a></td><td>Convert jdbcapi/testRelative.java to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3586">DERBY-3586</a></td><td>Remove am.Connection.reset(LogWriter,ClientBaseDataSource,boolean) and called methods</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3584">DERBY-3584</a></td><td>Replication tests shall not be run on Java ME</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3582">DERBY-3582</a></td><td>IndexOutOfBoundsError in ClockPolicy.moveHand</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3581">DERBY-3581</a></td><td>Changing certain properties on client DataSource objects causes existing connections to reflect the new values</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3580">DERBY-3580</a></td><td>Remove unused method Connection.resetConnection(LogWriter, String, Properties)</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3579">DERBY-3579</a></td><td>The Developer's Guide incorrectly describes the behavior of transactions inside procedures and functions</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3578">DERBY-3578</a></td><td>DrdaStreamOutBufferSize attribute of NetworkServerMBean should be of type int instead of String</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3576">DERBY-3576</a></td><td>Merge EngineBlob and EngineClob into a single interface</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3574">DERBY-3574</a></td><td>With client, attempting to get the lob length after commit  or connection close if there  was a call to length() before commit does not throw an exception</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3572">DERBY-3572</a></td><td>directory error in the file "java/testing/README.htm"</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3571">DERBY-3571</a></td><td>LOB locators are not released if the LOB columns are not accessed by the client</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3570">DERBY-3570</a></td><td>Implement DETERMINISTIC keyword for procedures and functions</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3568">DERBY-3568</a></td><td>Convert jdbcapi/savepointJdbc30_JSR169.java and jdbcapi/savepointJdbc30_XA.java to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3567">DERBY-3567</a></td><td>AsynchronousLogShipper#forceFlush should time out</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3566">DERBY-3566</a></td><td>Alter column set data type not allowed in soft upgrade with unique constraint</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3562">DERBY-3562</a></td><td>Number of log files (and log dir size) on the slave increases continuously</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3561">DERBY-3561</a></td><td>testStartStopManagementFromApplication(org.apache.derbyTesting.functionTests.tests.management.ManagementMBeanTest)junit.framework.AssertionFailedError: expected:&lt;2&gt; but was:&lt;5&gt;</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3558">DERBY-3558</a></td><td>regression test failure in testDerbyJarAttributeAlpha - Security Exception</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3556">DERBY-3556</a></td><td>change derby.tests.trace property to print the name of the test before it runs it</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3554">DERBY-3554</a></td><td>Change Collation test to run DatabaseMetaDataTest, BatchUpdateTest,GroupByExpressionTest, and UpdateableResultSetTest for only one locale</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3551">DERBY-3551</a></td><td>Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3549">DERBY-3549</a></td><td>Unable to start slave mode after authentication failure on a previous startSlave attempt</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3548">DERBY-3548</a></td><td>NoClassDefFoundError failure in SystemPrivilegesPermissionTest for weme6.1</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3546">DERBY-3546</a></td><td>Failed to get database schemas of a JAR database</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3544">DERBY-3544</a></td><td>If NetworkServer fails to shutdown when run as a separate process by NetworkServerTestSetup, test run will hang</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3543">DERBY-3543</a></td><td>NetworkServerControl with options but no command does not give usage message</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3538">DERBY-3538</a></td><td>NullPointerException during execution for query with LEFT OUTER JOIN whose inner table selects all constants.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3531">DERBY-3531</a></td><td>DatabasePermission uses a JDK 1.4 method that is not present in J2ME/CDC/Foundation.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3527">DERBY-3527</a></td><td>The slave will not notice that a network cable is unplugged and will therefore reject failover/stopSlave commands</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3526">DERBY-3526</a></td><td>AsynchronousLogShipper#workToDo is blocked while the log shipper sends a log chunk</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3525">DERBY-3525</a></td><td>Remove unneeded code to get JDBC level in BrokeredConnection and BrokeredStatement classes</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3521">DERBY-3521</a></td><td>Functionality for skipping testsuites on certain platforms fails for the new management testsuite on phoneME advanced</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3520">DERBY-3520</a></td><td>convert views.sql to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3515">DERBY-3515</a></td><td>23 timeouts encountered while running management junit suite as part of full nightly runs.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3509">DERBY-3509</a></td><td>The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3508">DERBY-3508</a></td><td>Log receiver thread fails with NPE at failover when master has died</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3506">DERBY-3506</a></td><td>Add JMX testing with a security manager and investigate testing with JMX authentication.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3503">DERBY-3503</a></td><td>Change stress.multi to dump thread stacks before killing off testers with jdk 1.5 and higher</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3494">DERBY-3494</a></td><td>Move the setup of NormalizeResultSetNode into the NormalizeResultSetNode</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3489">DERBY-3489</a></td><td>Error message XRE04 does not include the right port number.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3469">DERBY-3469</a></td><td>Clob.length() doesn't detect a closed underlying connection in a consistent way</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3462">DERBY-3462</a></td><td>Require new permissions in o.a.d.security.SystemPermission to allow control to Derby's JMX management and to ensure information is not leaked through JMX</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3447">DERBY-3447</a></td><td>Shutdown on a database without stopping replication hangs</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3446">DERBY-3446</a></td><td>Make ResultSet.getStatement return the correct statement when created by a logical statement</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3431">DERBY-3431</a></td><td>DatabaseMetaData.getConnection returns the wrong connection when using connection pooling</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3420">DERBY-3420</a></td><td>The -ca option should be removed from ij and from the ij command usage line</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3409">DERBY-3409</a></td><td>Remove JDBC 2.0-specific topics from Reference Manual and merge implementation notes as needed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3408">DERBY-3408</a></td><td>Wrong message when using SHOW in ij.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3401">DERBY-3401</a></td><td>Removing a ConnectionEventListener from a PooledConnection during its connectionClosed() callback causes other ConnectionEventListener callbacks to be missed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3397">DERBY-3397</a></td><td>Derby 10.3.1.4 and 10.3.2.1 break scrollable result sets? Hibernate Query.setFirstResult and/or setMaxResults</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3390">DERBY-3390</a></td><td>SQLException thrown from user function kills network connection</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3385">DERBY-3385</a></td><td>Tests for JMX Management and Monitoring</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3381">DERBY-3381</a></td><td>"ERROR XSDA3: Limitation: Record cannot be updated or inserted due to lack of space on the page...." in suites.All</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3379">DERBY-3379</a></td><td>"No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3373">DERBY-3373</a></td><td>SQL "distinct" and "order by" needed together</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3360">DERBY-3360</a></td><td>Invalid method java.lang.Integer &gt;&gt; void &lt;init&gt;(short) because java.lang.NoSuchMethodException: java.lang.Integer.&lt;init&gt;(short)</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3354">DERBY-3354</a></td><td>Select from large lob table with embedded gives OutOfMemoryError</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3347">DERBY-3347</a></td><td>ERROR XSDB3: Container information cannot change once written</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3338">DERBY-3338</a></td><td>CancelQueryTask.forgetContext() could be simplified.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3327">DERBY-3327</a></td><td>SQL roles: Implement authorization stack (and SQL session context to hold it)</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3320">DERBY-3320</a></td><td>Database creation and boot should fail if collation=TERRITORY_BASED and the selected locale is not supported</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3319">DERBY-3319</a></td><td>Logical connections do not check if a transaction is active on close</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3310">DERBY-3310</a></td><td>ASSERT in MergeSort.checkColumnTypes() disallow legal type conversions</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3307">DERBY-3307</a></td><td>NPE in PooledConnction event notification handling if a null listener is added</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3270">DERBY-3270</a></td><td>Delayed (on-demand) creation of current user schema makes select from view belonging to other schema fail.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3266">DERBY-3266</a></td><td>Not possible for non-db-owner to create a temporary table. "Get ERROR 42507: User 'USERB' can not perform the operation in schema 'SESSION'."</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3227">DERBY-3227</a></td><td>Remove final from all getConnection() methods in EmbeddedDataSource</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3223">DERBY-3223</a></td><td>SQL roles: make use of privileges granted to roles in actual privilege checking</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3219">DERBY-3219</a></td><td>Group by query with many aggregate columns and case statements fails with: ERROR XSDA7: Restore of a serializable or SQLData object of class , attempted to read more data than was originally stored</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3200">DERBY-3200</a></td><td>Developer's Guide: Add examples showing use of SQL authorization with user authentication</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3193">DERBY-3193</a></td><td>SQL roles: Add documentation</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3180">DERBY-3180</a></td><td>error XSDA3 when test is executing SYSCS_INPLACE_COMPRESS_TABLE in specific situation</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3151">DERBY-3151</a></td><td>Reduce dependency on NetworkServerControl in TestConfiguration</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3137">DERBY-3137</a></td><td>SQL roles: add catalog support</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3130">DERBY-3130</a></td><td>Reduce memory footprint of StoredRecordHeader</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3116">DERBY-3116</a></td><td>totalSpace not properly initialized in AllocPage</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3097">DERBY-3097</a></td><td>Unnecessary if statement can be removed from BaseActivation.getColumnFromNow</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3063">DERBY-3063</a></td><td>Extend the system function mechanism to support functions with multiple arguments</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3043">DERBY-3043</a></td><td>'Schema &lt;schemaname&gt; does not exist' when constraint used in table definition</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-3035">DERBY-3035</a></td><td>Cannot restore backups without BACKUP.HISTORY file</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2991">DERBY-2991</a></td><td>Index split deadlock</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2958">DERBY-2958</a></td><td>need to mention ClientDriver In Derby reference manual's java.sql.Driver interface section</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2892">DERBY-2892</a></td><td>Closing a resultset after retrieving a large &gt; 32665 bytes value with Network Server does not release locks</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2861">DERBY-2861</a></td><td>Thread safety issue in TableDescriptor</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2822">DERBY-2822</a></td><td>Add caching of store stream length in StoreStreamClob, if appropriate</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2750">DERBY-2750</a></td><td>Convert lang/declareGlobalTempTableJava.java to JUnit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2747">DERBY-2747</a></td><td>Reply incorrectly handles read() returning -1</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2514">DERBY-2514</a></td><td>convert lang/closed.java to junit</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2498">DERBY-2498</a></td><td>NullPointerException on ClientDataSource.getConnection() when ds.setdatabaseName was invalid</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2389">DERBY-2389</a></td><td>DOCS - Move Derby system and properties info from Tuning Guide into Reference Manual</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2388">DERBY-2388</a></td><td>DOCS - Reorder JDBC Reference section in Ref Manual</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2353">DERBY-2353</a></td><td>intermittent NPEs during DELETE ops in a reasonably large transaction</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2351">DERBY-2351</a></td><td>ORDER BY with expression with distinct in the select list returns incorrect result</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2320">DERBY-2320</a></td><td>Example in DEGREES function is not  appropriate.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2207">DERBY-2207</a></td><td>Improve usability of Derby's client/server security by implementing ANSI Roles</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-2085">DERBY-2085</a></td><td>Misleading error message for non-matching ORDER BY clause in queries with GROUP BY.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1944">DERBY-1944</a></td><td> jdbcapi/ParameterMappingTest.java test does not execute test for setObject(Blob/Clob) in DerbyNetClient</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1932">DERBY-1932</a></td><td>Reference Manual updates - JDBC Reference section</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1848">DERBY-1848</a></td><td>jdbcapi/SetQueryTimeoutTest.java fails on IBM  wctme 5.7</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1764">DERBY-1764</a></td><td>Rewrite stress.multi as a JUnit test</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1726">DERBY-1726</a></td><td>Make i18n/LocalizedDisplay.sql and i18n/LocalizedConnectionAttribute.sql behave equally on different platforms</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1670">DERBY-1670</a></td><td>Remove optional osgi.jar download by including equivalent jar from the apache incubator felix project in the Derby's svn</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1458">DERBY-1458</a></td><td>Add MessageBundleTest to build script to verify that there are no orphaned message ids</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1416">DERBY-1416</a></td><td>Message id J029 (CONN_RESTORE_FROM) does not have a matching message text</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1415">DERBY-1415</a></td><td>Message id J030 in reference.MessageId.java does not have a matching message</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1412">DERBY-1412</a></td><td>Possible values for derby.storage.rowLocking Derby engine is not currently documented eventhough the property is</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1411">DERBY-1411</a></td><td>DRDAConnThread uses SQLState.NO_SUCH_DATABASE, which has no matching message</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1387">DERBY-1387</a></td><td>Add JMX extensions to Derby</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1331">DERBY-1331</a></td><td>Derby's "set schema" behavior is not compliant with SQL 2003 Foundation spec.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1107">DERBY-1107</a></td><td>For existing databases JDBC metadata queries do not get updated properly  between maintenance versions.</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-1062">DERBY-1062</a></td><td>Change the internal implemetation of SYSCS_INPLACE_COMPRESS_TABLE to share existing alter table</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-961">DERBY-961</a></td><td>Error 22001 can include 'XX-RESOLVE-XX' which should be removed</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-719">DERBY-719</a></td><td>Calling SYSCS_INPLACE_COMPRESS_TABLE on SYS.SYSTABLES results in a lock timeout, with only a single connection active</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-576">DERBY-576</a></td><td>xaHelper in ij creates global id that is not the same across platforms</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-503">DERBY-503</a></td><td>Documentation should recommend using .newInstance() to instantiate JDBC driver</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-481">DERBY-481</a></td><td>implement SQL generated columns</td>

-</tr>

-<tr>

-<td><a href="http://issues.apache.org/jira/browse/DERBY-269">DERBY-269</a></td><td>Provide some way to update index cardinality statistics (e.g. reimplement update statistics)</td>

-</tr>

-<tr>

-<td><a 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>

+<td><a href="https://issues.apache.org/jira/browse/DERBY-159">DERBY-159</a></td><td>When Derby runs in Network Server mode, client does not receive warnings generated by Derby - should get documented</td>

 </tr>

 </table>

-</blockquote>

+</div>

 <h2>

 <a name="Issues"></a>Issues</h2>

-<blockquote>

-<p>Compared with the previous release (10.4.2.0), Derby release 10.5.1.1 introduces the following incompatibilities. These merit your special attention.</p>

+<div>

+<p>Compared with the previous release (10.8.1.2), Derby release 10.8.2.2 introduces the following new features and incompatibilities. These merit your special attention.</p>

 <ul>

 <li>

-<a href="#Note for DERBY-4073">

-<p>Note for DERBY-4073: 

-The method <tt>setSsl(int)</tt> has been removed from the client data source classes.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-4050">

-<p>Note for DERBY-4050: 

-Table growth may result from multi-threaded Clob updates before the fix for DERBY-4050.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-4042">

-<p>Note for DERBY-4042: 

-Format of file name arguments to the import procedures changed for

-files with single quotes (') in their names.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-4008">

-<p>Note for DERBY-4008: 

-  After the change for DERBY-4008, applications may see a different error message when attempting to connect a 10.5 client to older revision servers (e.g. 10.4 and 10.3) with multibyte database names.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-3977">

-<p>Note for DERBY-3977: 

-A different exception is thrown by the embedded driver when trying to truncate a Clob with a too large length argument.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-3701">

-<p>Note for DERBY-3701: 

-  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>

-</li>

-<li>

-<a href="#Note for DERBY-3652">

-<p>Note for DERBY-3652: 

-Derby now follows the SQL Standard rules for matching functions and procedures to Java methods.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-3420">

-<p>Note for DERBY-3420: 

-The <i>-ca</i> command line option has been removed from ij.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-3347">

-<p>Note for DERBY-3347: 

-A bug that could cause unrecoverable database corruption has been fixed.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-3327">

-<p>Note for DERBY-3327: 

-The effect of setting the current default schema (<code>SET SCHEMA

-schemaname</code>) inside nested connection of a stored procedure or

-function has been changed to comply with SQL standard semantics.</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-3319">

-<p>Note for DERBY-3319: 

-Exception is thrown when connection with uncommitted operations is closed.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-2351">

-<p>Note for DERBY-2351: 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>

-</li>

-<li>

-<a href="#Note for DERBY-2085">

-<p>Note for DERBY-2085: 

-Derby has improved the error message which is issued when an invalid

-column reference is found in a grouped query. Derby now issues message

-42Y36 instead of 42Y30. Furthermore, the wording of message 42Y36 has

-been expanded to further explain the behavior.

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-1062">

-<p>Note for DERBY-1062: 

-Applications will see a different error code and message when they attempt to call SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE on a table that does not exist. 

-

-</p>

-</a>

-</li>

-<li>

-<a href="#Note for DERBY-48">

-<p>Note for DERBY-48: 

-In Derby, a user's <b>initial default schema</b> 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>

-</a>

+<a href="#Note for DERBY-5395"><span>Note for DERBY-5395: 

+Now, only the database owner may view several diagnostic VTIs: <i>syscs_diag.statement_cache</i>, <i>syscs_diag.transaction_table</i>, <i>syscs_diag.error_log_reader( )</i>, and <i>syscs_diag.statement_duration()</i>.

+</span></a>

 </li>

 </ul>

 <hr>

 <h3>

-<a name="Note for DERBY-4073"></a>Note for DERBY-4073</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

+<a name="Note for DERBY-5395"></a>Note for DERBY-5395</h3>

+<div>

 

 

 <h4>Summary of Change</h4>

 

 <p>

-The method <tt>setSsl(int)</tt> has been removed from the client data source classes.

+Now, only the database owner may view several diagnostic VTIs: <i>syscs_diag.statement_cache</i>, <i>syscs_diag.transaction_table</i>, <i>syscs_diag.error_log_reader( )</i>, and <i>syscs_diag.statement_duration()</i>.

 </p>

 

 

@@ -1382,1729 +482,174 @@
 <h4>Symptoms Seen by Applications Affected by Change</h4>

 

 <p>

-The application will either fail to compile, or experience a <tt>NoSuchMethodError</tt>.

-Only applications invoking the removed method are affected.

+Previously in a database with SQL authorization enabled, any user

+could select from those diagnostic VTIs. Now only the database owner

+can.

 </p>

 

 

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

 

 <h4>Incompatibilities with Previous Release</h4>

 

 <p>

-The method <tt>setSsl(int)</tt> can no longer be used to configure SSL

-with the client data sources.

+Application designers should ensure that only the database owner

+selects from these VTIs. For most applications this should not be a

+problem since the VTIs are intended to be used in production only as

+technical support tools.

 </p>

 

 

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

 

 <h4>Rationale for Change</h4>

 

 <p>

-Having two <tt>setSsl</tt>-methods caused choice problems for some applications

-using Derby data sources and also configuring the data source through

-introspection, since there were two methods called setSsl;

-<tt>setSsl(int)</tt> and <tt>setSsl(String)</tt>. 

+These VTIs reveal sensitive information which only authorized persons

+should see.

 </p>

 

 

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

 

 <h4>Application Changes Required</h4>

 

 <p>

-Use <tt>setSsl(String)</tt> instead of <tt>setSsl(int)</tt>.

+Table functions with definer's rights can be used to grant other users

+access to the information in these VTIs. For instance, the following

+technique can be used to let ordinary users view the non-sensitive data in <i>syscs_diag.statement_cache</i>:

 </p>

 

 

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-4050"></a>Note for DERBY-4050</h3>

-<blockquote>

-

-<!-- 

-

--->

-

-

-<h4>Summary of Change</h4>

-

 <p>

-Table growth may result from multi-threaded Clob updates before the fix for DERBY-4050.

-</p>

-

-

-<!-- 

-

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-Before the fix for DERBY-4050, applications may have seen growth in the size of the database, particularly the size of the dat files for Clob tables, when doing updates to the Clob tables from multiple threads.  The fix for DERBY-4050 will prevent future growth but will not reclaim space consumed by the bug in the past.  To reclaim the space, a full offline compress of the clob table is needed. See the Derby documentation for usage of  <A HREF="http://db.apache.org/derby/docs/10.4/ref/rrefaltertablecompress.html"> SYSCS_UTIL.SYSCS_COMPRESS_TABLE </A>

-

- 

-

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-none

-</p>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-DERBY-4050 fixes a bug in space reclamation. 

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-The compress table should only need to be run once if the fix for DERBY-4050 has been applied.  No application changes should be required.

-</p>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-4042"></a>Note for DERBY-4042</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-Format of file name arguments to the import procedures changed for

-files with single quotes (') in their names.

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-In the previous release, applications that imported data from a file

-whose file name contained a single quote (') character would fail

-unless they replaced each single quote in the file name argument to

-the import procedure with two single quotes. Now this has changed and

-Derby does not understand the file name argument unless it has the

-same number of single quote characters as the actual file

-name. Applications that worked around the problems in earlier releases

-by adding extra single quotes, will now see exceptions like the

-following:

+First, create a static Java method which selects only the

+non-sensitive columns:

 </p>

 

 

 <pre>

-ERROR XIE04: Data file not found: Rock''n''roll.csv

+import java.sql.DriverManager;

+import java.sql.ResultSet;

+import java.sql.SQLException;

+

+public class SafeCacheViewer

+{

+    public  static  ResultSet   safeCacheViewer()   throws SQLException

+    {

+        return DriverManager.getConnection( "jdbc:default:connection" ).prepareStatement

+            ( "select id, schemaName, valid, compiled_at from syscs_diag.statement_cache" ).executeQuery();

+    }

+}

 </pre>

 

 

 <p>

-Applications that do not import files whose names contain single

-quotes will not be affected by this change.

-</p>

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-Previous releases required file name arguments to the import

-procedures to double each occurrence of a single quote in the file

-name, like this when importing a file

-called <tt>C:/Chip's/TERMS.dat</tt>:

+Then the database owner should register the method as a table function

+enjoying definer's rights, and grant EXECUTE

+privilege on it to PUBLIC:

 </p>

 

 

 <pre>

-PreparedStatement ps = conn.prepareStatement(

-    "CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(null,'MY_TABLE',?,null,null,null,0)");

-ps.setString(1, "C:/Chip''s/TERMS.dat");

-ps.execute();

+create function safeCacheViewer()

+returns table

+(

+    id char( 36 ),

+    schemaName varchar( 128 ),

+    valid boolean,

+    compiled_at timestamp

+)

+language java parameter style derby_jdbc_result_set reads sql data

+external security definer

+external name 'SafeCacheViewer.safeCacheViewer';

+

+grant execute on function safeCacheViewer to public;

 </pre>

 

 

 <p>

-In this release the above code would result in the following exception:

+Finally, other users can select data from the table function as

+follows (here test_dbo is the schema of the database owner):

 </p>

 

 

 <pre>

-ERROR XIE04: Data file not found: C:/Chip''s/TERMS.dat

+select * from table( test_dbo.safeCacheViewer() ) s;

 </pre>

 

 

-<p>

-In this release, applications must use the actual name of the file,

-like this:

-</p>

 

-

-<pre>

-PreparedStatement ps = conn.prepareStatement(

-    "CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE(null,'MY_TABLE',?,null,null,null,0)");

-ps.setString(1, "C:/Chip's/TERMS.dat");

-ps.execute();

-</pre>

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-It is more intuitive if the file name arguments match the actual file

-names. Also, in the previous releases there were some combinations of

-single quotes and other special characters (like double quotes) that

-it was not possible to get to work even with the workaround.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-Applications that work around the issue in previous releases by adding

-extra single quotes to the file name arguments, must be changed so

-that they do not add extra single quote characters.

-</p>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-4008"></a>Note for DERBY-4008</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-  After the change for DERBY-4008, applications may see a different error message when attempting to connect a 10.5 client to older revision servers (e.g. 10.4 and 10.3) with multibyte database names.

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-In previous releases  when attempting to connect to network server using a multibyte database name the connect would fail with the the exception:<BR>

-

-<code>

-SQLSTATE:22005

-java.sql.SQLDataException: Unicode string cannot convert to Ebcdic string

-</code>

-

-<BR>

-This message will not change for 10.5 clients connecting to 10.5 servers.

-

-After the change for DERBY-4008 the error message may change when connecting 10.5 clients to older revision server. Instead the message will be:<BR>

-

-<code>

-SQLSTATE:08006

-java.sql.SQLNonTransientConnectionException: A network protocol error was encountered and the connection has been terminated: A PROTOCOL Data Stream Syntax Error was detected.  Reason: 0x8,464. Plaintext connection attempt to an SSL enabled

-server?

-</code>

-<BR>

-

-with a chained SQLException: <BR>

-

-<code>

-SQLSTATE:22005

-java.sql.SQLDataException: Unicode string cannot convert to Ebcdic string

-</code>

-<BR>

-

-The protocol error will also show on the server console.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-The client error message when attempting to connect with multibyte database names will change with mixed revision client/server as described in the previous section.

-</p>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-This change was made in preparation for fixing DERBY-728 to allow multibyte characters in the database name.  The change in error message with back revision servers was considered an acceptable change and necessary to fix DERBY-728.

-

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-To reveert to the previous error message, users can upgrade their server to the latest on the 10.3 or 10.4 branch, or upgrade their server to 10.5. Otherwise applications expecting the old error message should upon gettting the SQLState: 08006 message retrieve the chained exception with SQLExcepiton.getNextMessage() and then process the message as before.

-

-

-</p>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3977"></a>Note for DERBY-3977</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-A different exception is thrown by the embedded driver when trying to truncate a Clob with a too large length argument.

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-In the previous release, the embedded driver would throw an exception with

-SQLState XJ076 when trying to truncate a Clob with a length argument bigger

-than the Clob length. Now, it will throw the same exception as the client

-driver, XJ079. The error messages also differ:

-</p>

-

-

-<pre>

-Before: XJ076: The position argument '18149' exceeds the size of the BLOB/CLOB.

-Now: XJ079: The length specified '18149' exceeds the size of the BLOB/CLOB.

-</pre>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-Applications catching a specific exception based on SQLState may behave

-differently. The incompatibility can only be seen if the application calls

-<code>Clob.truncate</code> with the embedded driver.

-</p>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-To make the embedded and the client driver consistent.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-Look for SQLState XJ079 instead of XJ076 when <code>Clob.truncate()</code> is called.

-</p>

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3701"></a>Note for DERBY-3701</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<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>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<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 <b> or </b> with 10.5 or higher they may see tracing occur where it did not before.

-

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<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>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-

-The tracing properties should not be summarily ignored or cause the client to hang if the trace directory does not exist.  

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<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>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3652"></a>Note for DERBY-3652</h3>

-<blockquote>

-

-

-<h4>Summary of Change</h4>

-

-<p>

-Derby now follows the SQL Standard rules for matching functions and procedures to Java methods.

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-In previous releases, Derby matched SQL routines to Java methods using

-an irregular set of rules which were hard to describe. At the same

-time, the user documentation falsely claimed that Derby followed the

-signature matching rules in the ANSI/ISO SQL Standard. Derby now

-conforms to the Standard behavior. In general, the Standard behavior

-is easier to understand and it is now possible to be confident that a

-function or procedure definition will match the desired Java

-method. In certain corner cases, however, methods which used to

-resolve will no longer resolve. The Standard resolution rules are

-described in the Derby Reference Guide.

-</p>

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-Routines may resolve differently. Here are the differences listed in

-declining order of likelihood:

-</p>

-

-

-<ol>

-

-<li>

-<b>Ambiguity</b> - Some SQL routines may match multiple Java

-methods now. This raises an error according to the Standard. This is

-most likely to affect the following matches:

- <ul>

-   

-<li>Matching INTEGER to Java <i>int</i> and <i>Integer</i>.</li>

- 

-</ul>

-

-</li>

-

-<li>

-<b>Failure</b> - Some SQL routines may fail to match Java

-methods. This is most likely to affect the following matches:

- <ul>

-   

-<li>SMALLINT no longer matches <i>int</i>.</li>

-   

-<li>INTEGER no longer matches <i>long</i>.</li>

-   

-<li>BIGINT no longer matches <i>float</i>.</li>

-   

-<li>REAL no longer matches <i>double</i>.</li>

-   

-<li>VARCHAR no longer matches <i>Object</i>.</li>

-   

-<li>NUMERIC no longer matches <i>Object</i>.</li>

- 

-</ul>

-

-</li>

-

-<li>

-<b>Change</b> - Some SQL routines may resolve to different Java

-methods now.</li>

-

-<li>

-<b>Success</b> - Some SQL routines may now resolve even though

-previously they did not resolve to Java methods. This is most likely

-to affect the following matches:

- <ul>

-   

-<li>BLOB now matches <i>Blob</i>.</li>

-   

-<li>CLOB now matches <i>Clob</i>.</li>

- 

-</ul>

-

-</li>

-

-</ol>

-

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-The previous behavior violated the SQL Standard and was very hard to explain. The new behavior

-is correct and easy to describe.

-</p>

-

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-This release includes a lint tool, <i>SignatureChecker</i>. If your

-application uses SQL functions and/or procedures, you should run this

-tool against your databases in order to find routines which no longer

-match. To run the tool, make sure that your classpath contains the 10.5 jar files, including <i>derbytools.jar</i>.

-</p>

-

-

-

-<p>

-On a J2SE platform, run the lint tool as follows (where

-CONNECTION_URL_TO_DATABASE is the connection URL you would use in

-order to obtain a connection via <i>DriverManager.getConnection()</i>):

-</p>

-

-

-<blockquote>

-<pre>

-  java org.apache.derby.tools.SignatureChecker CONNECTION_URL_TO_DATABASE

-</pre>

-</blockquote>

-

-

-<p>

-Alternatively, you can invoke the tool via <i>derbyrun.jar</i>. E.g.:

-</p>

-

-

-<blockquote>

-<pre>

-  java -jar derbyrun.jar SignatureChecker "jdbc:derby:myDB" 

-</pre>

-</blockquote>

-

-

-<p>

-On a J2ME platform, run the lint tool as follows (where

-DATABASE_NAME is the database name you would set via

-<i>EmbeddedSimpleDataSource.setDatabaseName()</i>):

-</p>

-

-

-<blockquote>

-<pre>

-  java org.apache.derby.tools.SignatureChecker DATABASE_NAME

-</pre>

-</blockquote>

-

-

-<p>

-The tool examines every routine registered in the database and

-prints out results like the following:

-</p>

-

-

-<blockquote>

-<pre>

-Found a matching method for: "APP"."DOINSERT"( )

-Found a matching method for: "APP"."DOINSERTANDCOMMIT"( )

-Found a matching method for: "APP"."APPENDFOOANDBAR"( VARCHAR )

-Unresolvable routine: "APP"."IDONTEXIST"( VARCHAR , INTEGER ).

-Detailed reason: No method was found that matched the method call z.iDontExist(java.lang.String, int),

-tried all combinations of object and primitive types and any possible

-type conversion for any parameters the method call may have.

-The method might exist but it is not public and/or static, or the parameter types are not method invocation convertible.

-Found a matching method for: "APP"."RUNDDL"( VARCHAR )

-Unresolvable routine: "APP"."TABFUNCDOESNTEXIST"( VARCHAR , BIGINT ).

-Detailed reason: No method was found that matched the method call

-org.apache.derbyTesting.functionTests.tests.lang.TableFunctionTest.appendFooAndBar(java.lang.String, long),

-tried all combinations of object and primitive types and any possible

-type conversion for any parameters the method call may have.

-The method might exist but it is not public and/or static, or the parameter types are not method invocation convertible.

-</pre>

-</blockquote>

-

-

-<p>

-In the example above, the lint tool found matches for all routines

-except for the functions <i>app.iDontExit</i> and <i>app.tabFuncDoesntExist</i>.

-If the lint tool cannot find a match for one of your functions or

-procedures, it tells you what signature it expected to find. You need to adjust your application in one of

-the following ways:

-</p>

-

-

-<ol>

-

-<li>

-<b>Method</b> - Change the signature of your Java method to match

-  the signature suggested by the lint tool.</li>

-

-<li>

-<b>Routine</b> - Drop and recreate your function/procedure so that

-  its arguments and return type match your Java method according to

-  the Standard rules described in the Reference Guide.</li>

-

-</ol>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3420"></a>Note for DERBY-3420</h3>

-<blockquote>

-

-

-<h4>Summary of Change</h4>

-

-<p>

-The <i>-ca</i> command line option has been removed from ij.

-</p>

-

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-Applications which attempt to pass JDBC connection attributes using the -ca

-flag to ij will be rejected, with a usage message such as:

-<blockquote>

-Usage: java org.apache.derby.tools.ij [-p propertyfile] [inputfile]

-</blockquote>

-

-</p>

-

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-Applications which attempt to pass JDBC connection attributes using the -ca

-flag to ij will fail, as that flag is no longer recognized by ij.

-</p>

-

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-It used to be that you could not specify both client and embedded attributes

-in the connection URL. Since Derby now supports such combinations of

-attributes in the connection URL, the community decided that the -ca option

-doesn't really add value and so it has been removed.

-</p>

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-Applications should include connection attributes in the connection URL. For

-example:

-<blockquote>

-    connect 'jdbc:derby:myDB;territory=no_NO;collation=TERRITORY_BASED;create=true';

-</blockquote>

-

-</p>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3347"></a>Note for DERBY-3347</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-A bug that could cause unrecoverable database corruption has been fixed.

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-A bug that could cause database corruption was introduced in the 10.3

-codeline and affects the following releases:

-</p>

-

-

-<ul>

-  

-<li>Apache Derby 10.3.1.4</li>

-  

-<li>Apache Derby 10.3.2.1</li>

-

-</ul>

-

-

-<p>

-Users who are hit by this bug may experience exceptions at various

-times during execution of SQL statements, booting or shutdown of a

-database, or during checkpointing. It may result in a number of

-different error messages, including any of these:

-</p>

-

-

-<pre>

-ERROR XSDB3: Container information cannot change once written: was 0, now 80

-ERROR XSDG1: Page Page(1039,Container(0, 5856)) could not be written to disk, please check if disk is full.

-ERROR XSDG2: Invalid checksum on Page Page(0,Container(0, 1313))

-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>

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-None.

-</p>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-Database corruption is bad.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<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 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>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3327"></a>Note for DERBY-3327</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-The effect of setting the current default schema (<code>SET SCHEMA

-schemaname</code>) inside nested connection of a stored procedure or

-function has been changed to comply with SQL standard semantics.</p>

-

-<p>

-Previously, setting the schema in a nested connection would have an

-effect on the current default schema also in the SQL connection of the

-caller. The SQL standard requires that the value of the default

-current schema at the time of the call be reestablished when the call

-is completed. This is now implemented.</p>

-

-<p>

-If the current schema is dropped by a stored procedure or function,

-the current schema as well as the saved values of the callers will be

-reset to the initial default schema of the root connection.</p>

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-The current default schema of a connection which calls a stored

-procedure or function which sets the current schema may be different

-after the return.

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-<h4>Rationale for Change</h4>

-

-<p>

-SQL standard compliance.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-If the application relies on a stored procedure to change the current

-default schema, this must now be done in the calling connection instead.

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-3319"></a>Note for DERBY-3319</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-Exception is thrown when connection with uncommitted operations is closed.

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-In the previous release, applications could close a connection

-obtained from Derby's implementations of

-<code>javax.sql.DataSource</code> or

-<code>javax.sql.ConnectionPoolDataSource</code>, even if the

-connection had uncommitted operations. Now, Derby raises an

-<code>SQLException</code> when an attempt to close a connection with

-an active transaction is made. The exception will have SQLState 25001,

-and its message will say the following:

-</p>

-

-

-<pre>

-java.sql.SQLException: Cannot close a connection while a transaction is still active.

-</pre>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-Applications that close connections with active transactions now fail.

-</p>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-The previous behaviour was not consistent with the behaviour of

-connection objects obtained from <code>java.sql.DriverManager</code>,

-which already raise an exception in such a situation. The previous

-behaviour could also cause resource leaks because there is no way to

-free the resources held by an active transaction once its connection

-object has been closed.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-Users must call <code>commit()</code> or <code>rollback()</code>, or

-use auto-commit, before attempting to close a connection with

-uncommitted operations.

-</p>

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-2351"></a>Note for DERBY-2351</h3>

-<blockquote>

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-<h4>Summary of Change</h4>

-

-<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>

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<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>

-

-<p style="font-family: monospace;">

-create table person (name varchar(10), age int);<br>

-insert into person values ('John', 10);<br>

-insert into person values ('John', 30);<br>

-insert into person values ('Mary', 20);<br>

-

-<br>

-SELECT DISTINCT name FROM person ORDER BY age;<br>

-

-</p>

-

-<p>The query above is now rejected, with the error message:</p>

-

-<blockquote>

-	ERROR 42879: The ORDER BY clause may not contain column 'AGE',

-	since the query specifies DISTINCT and that column does not appear

-	in the query result.

-</blockquote>

-

-<p>If the AGE column is included in the DISTINCT list in the above query,

-there is no ambiguity</p>

-

-<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>

-

-<p style="font-family: monospace;">  create table t1 (i int, j int);<br>

-  select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.idcolumn1, t1.idcolumn2;</p>

-

-<p>This query is now rejected, as there is no column named 'idcolumn1'

-in table 't1'. The error message is:</p>

-

-<blockquote>

-	ERROR 42X04: Column 'T1.IDCOLUMN1' is either not in any table in

-	the FROM list or appears within a join specification and is outside

-	the scope of the join specification or appears in a HAVING clause

-	and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE 

-	statement then 'T1.IDCOLUMN1' is not a column in the target table.

-</blockquote>

-

-<p>Valid forms of the query above are:</p>

-

-<p style="font-family: monospace;">

-  select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by idcolumn1, idcolumn2;</p>

-

-<p>or</p>

-

-<p style="font-family: monospace;">

-  select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.id, t1.id;</p>

-

-

-<h4>Rationale for Change</h4>

-

-<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:

-<ul>

-	

-<li>if the table name is provided, we match against the

-	underlying table name, and don't consider any aliases</li>

-	

-<li>if the table name is NOT provided, we first match against

-	the alias name, if present, and if no alias name matches

-	then we match against the underlying source column name. </li>

-

-</ul>

-

-</p>

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-<h4>Application Changes Required</h4>

-

-<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>

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-2085"></a>Note for DERBY-2085</h3>

-<blockquote>

-

-<h4>Summary of Change</h4>

-

-<p>

-Derby has improved the error message which is issued when an invalid

-column reference is found in a grouped query. Derby now issues message

-42Y36 instead of 42Y30. Furthermore, the wording of message 42Y36 has

-been expanded to further explain the behavior.

-</p>

-

-<p>

-Consider the table

-</p>

-

-<blockquote>

-<code>

-CREATE TABLE t (i INT, j INT)

-</code>

-</blockquote>

-

-<p>

-and consider the following query:

-</p>

-

-<blockquote>

-<code>

-SELECT i FROM t GROUP BY i ORDER BY j

-</code>

-</blockquote>

-

-<p>

-In Derby releases 10.2, 10.3, and 10.4,

-this query gives the following error message:

-</p>

-

-<blockquote>

-<code>

-

-ERROR 42Y30: The SELECT list of a grouped query contains at least one invalid expression. If a SELECT list has a GROUP BY, the list may only contain valid grouping expressions and valid aggregate expressions.

-</code>

-</blockquote>

-

-<p>

-This is misleading since there is no invalid expression in the SELECT

-list. It is the ORDER BY clause that is wrong.

-In Derby 10.5, this query will now give the following error message, which is

-a revised version of the message issued by 10.1 (that is, Derby 10.5 behaves

-more like Derby 10.1 in this respect):

-</p>

-

-<blockquote>

-<code>

-ERROR 42Y36: Column reference 'J' is invalid, or is part of an invalid expression.  For a SELECT list with a GROUP BY, the columns and expressions being selected may only contain valid grouping expressions and valid aggregate expressions.

-</code>

-</blockquote>

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-An application which issued a grouped select statement with an invalid

-column reference in the order by clause may now receive a different error

-message than it did in 10.4.

-</p>

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-We feel that message 42Y36 is more helpful to the user in explaining the

-problem with the invalid query.

-</p>

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-1062"></a>Note for DERBY-1062</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-Applications will see a different error code and message when they attempt to call SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE on a table that does not exist. 

-

-</p>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<p>

-Applications will see a different error code and message when they attempt to call SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE on a table that does not exist. 

-The new error code and message will be 

-ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'MissingTableName' because it does not exist. 

-The old error code and message used to be 

-ERROR 42X05: Table/View 'MissingTableName' does not exist. 

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<p>

-The SQL exception code in the previous release was 42X05 and error message was "Table/View 'MissingTableName' does not exist."

-</p>

-

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<p>

-To avoid duplication of code, the error handling is now done by a generic routine in ALTER TABLE rather than a routine specific to SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE. This change to use ALTER TABLE code to implement SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE was made in 10.5 release and that is the reason behind the change in error code behavior.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-If the application is looking for 42X05, it should be changed to look for 42Y55.

-</p>

-

-

-

-</blockquote>

-<hr>

-<h3>

-<a name="Note for DERBY-48"></a>Note for DERBY-48</h3>

-<blockquote>

-

-<!-- 

-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.

-

-  For instance:

-

-  Applications may no longer open two InputStreams on the same ResultSet column.

--->

-

-

-<h4>Summary of Change</h4>

-

-<p>

-In Derby, a user's <b>initial default schema</b> 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>

-

-

-<!-- 

-  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.

-

-  For instance:

-

-  In the previous release, applications were able to open two

-  InputStreams on the same column. Depending on how these streams

-  interacted, the value siphoned out of the column was erratic. Now

-  Derby raises a SQLException when the application attempts to create

-  the second InputStream.

--->

-

-

-<h4>Symptoms Seen by Applications Affected by Change</h4>

-

-<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>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.

-

-  For instance:

-

-  Applications which open two InputStreams on the ResultSet column now

-  fail.

--->

-

-

-<h4>Incompatibilities with Previous Release</h4>

-

-<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>

-

-<!-- 

-  DESCRIBE WHY THE CHANGE WAS MADE.

-

-  For instance:

-

-  The previous behavior violated the JDBC standard. The new behavior

-  is correct.

--->

-

-

-<h4>Rationale for Change</h4>

-

-<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 href="https://issues.apache.org/jira/browse/DERBY-48">DERBY-48</a>

-and thus reduces the chance for deadlocks.

-</p>

-

-

-<!-- 

-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR

-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.

-

-  For instance:

-

-  Users must recode applications which open multiple streams on the same column.

--->

-

-

-<h4>Application Changes Required</h4>

-

-<p>

-Verify that the application code does not rely on the initial default schema

-being absent after a rollback.

-</p>

-

-

-

-</blockquote>

-</blockquote>

+</div>

+</div>

 <h2>

 <a name="Build Environment"></a>Build Environment</h2>

-<blockquote>

-<p>Derby release 10.5.1.1 was built using the following environment:</p>

+<div>

+<p>Derby release 10.8.2.2 was built using the following environment:</p>

 <ul>

 <li>

-<b>Branch</b> - Source code came from the 10.5 branch.</li>

+<b>Branch</b> - Source code came from the 10.8 branch.</li>

 <li>

-<b>Machine</b> - Microsoft Windows XP Professional Version 2002 Service Pack 2.</li>

+<b>Machine</b> - Windows XP Professional Version 2002 Service Pack 3</li>

 <li>

 <b>Ant</b> - Apache Ant version 1.7.0 compiled on December 13 2006.</li>

 <li>

-<b>JDK 1.4</b> - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)

-Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142-20061124 (SR7)</li>

+<b>JDK 1.4</b> - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142ifx-20110211 (SR13 FP8+PM31983)).</li>

 <li>

-<b>Java 6</b> - Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3))

-IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20081105_25433</li>

+<b>Java 6</b> - Java(TM) SE Runtime Environment (build pwi3260sr9fp1-2011-0208_03(SR9 FP1) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623).</li>

 <li>

-<b>Compiler</b> - The 1.6 compiler was used to compile all classes, but java 1.4.2 classes were used to compile appropriate 1.4.2 support</li>

+<b>Compiler</b> - The 1.6.0-b105 javac was used to compile all classes.</li>

 <li>

-<b>JSR 169</b> - J2ME support was built using IBM's j9 jvm from WEME6.1</li>

+<b>JSR 169</b> - Java ME support was built using libraries from IBM's j9 jvm from WEME 6.2.</li>

 </ul>

-</blockquote>

+</div>

+<h2>

+<a name="Verifying Releases"></a>Verifying Releases</h2>

+<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>

+

+

+<p>The PGP signatures can be verified using

+<a href="http://www.pgpi.org/">PGP</a> or

+<a href="http://www.gnupg.org/">GPG</a>.

+First download the Apache Derby

+<a href="http://svn.apache.org/repos/asf/db/derby/code/trunk/KEYS">KEYS</a>

+as well as the <code>asc</code> signature file for the particular

+distribution. It is important that you get these files from the ultimate

+trusted source - the main ASF distribution site, rather than from a mirror.

+Then verify the signatures using ...</p>

+

+

+<pre>

+% pgpk -a KEYS

+% pgpv db-derby-X.Y.tar.gz.asc

+

+<em>or</em>

+

+% pgp -ka KEYS

+% pgp db-derby-X.Y.tar.gz.asc

+

+<em>or</em>

+

+% gpg --import KEYS

+% gpg --verify db-derby-X.Y.tar.gz.asc

+

+</pre>

+

+

+<p>To verify the MD5 signature on the files, you need to use a program

+called <code>md5</code> or <code>md5sum</code>, which is

+included in many unix distributions.  It is also available as part of

+<a href="http://www.gnu.org/software/textutils/textutils.html">GNU

+Textutils</a>.  Windows users can get binary md5 programs from <a href="http://www.fourmilab.ch/md5/">here</a>, <a href="http://www.pc-tools.net/win32/freeware/console/">here</a>, or

+<a href="http://www.slavasoft.com/fsum/">here</a>.</p>

+

+

+<p>We strongly recommend that you verify your downloads with both PGP and MD5.</p>

+

+

+

+</div>

 </body>

 </html>


diff --git a/derby/org.apache.derby/derby.jar b/derby/org.apache.derby/derby.jar
index 2820dbd..b595559 100644
--- a/derby/org.apache.derby/derby.jar
+++ b/derby/org.apache.derby/derby.jar
Binary files differ

diff --git a/derby/org.apache.derby/derbyclient.jar b/derby/org.apache.derby/derbyclient.jar
index 1c319c0..8a7cecf 100644
--- a/derby/org.apache.derby/derbyclient.jar
+++ b/derby/org.apache.derby/derbyclient.jar
Binary files differ

diff --git a/derby/org.apache.derby/pom.xml b/derby/org.apache.derby/pom.xml
index 9acbc8e..82e59ad 100644
--- a/derby/org.apache.derby/pom.xml
+++ b/derby/org.apache.derby/pom.xml

@@ -23,6 +23,6 @@
   </parent>

 

   <artifactId>org.apache.derby</artifactId>

-    <version>10.5.1.1</version>

+    <version>10.8.2.2</version>

   <packaging>eclipse-plugin</packaging>

 </project>
commit	691082159e23f1285222e92b5c09be38f3e60bb7	[log] [tgz]
author	Juergen G. Kissner <juergen.kissner@sap.com>	Wed Feb 08 10:13:53 2012 +0000
committer	Juergen G. Kissner <juergen.kissner@sap.com>	Wed Feb 08 10:13:53 2012 +0000
tree	47bd8f512a787302413edab512ce42dea1593a14
parent	a164582a703b498f72dda5701b208971dfe71443 [diff]