summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEike Stepper2007-09-29 02:59:30 (EDT)
committerEike Stepper2007-09-29 02:59:30 (EDT)
commitfe421bda93d4468dcf067c539ae849415bb6e329 (patch)
treee8c3d99aa774a26b1002087eefb3c5dd12edbfe5
parentf783d10889d20861843839a7fa159598f0e829ff (diff)
downloadcdo-fe421bda93d4468dcf067c539ae849415bb6e329.zip
cdo-fe421bda93d4468dcf067c539ae849415bb6e329.tar.gz
cdo-fe421bda93d4468dcf067c539ae849415bb6e329.tar.bz2
[204887] Provide CDOServer product
https://bugs.eclipse.org/bugs/show_bug.cgi?id=204887
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby-server.bat2
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/CHANGES.html1730
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/KEYS536
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/LICENSE202
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/NOTICE31
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/RELEASE-NOTES.html4115
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/NetworkServerControl.bat38
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/dblook.bat38
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/derby_common.bat81
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/ij.bat38
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setEmbeddedCP.bat33
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkClientCP.bat33
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkServerCP.bat32
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/startNetworkServer.bat39
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/stopNetworkServer.bat37
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/sysinfo.bat38
-rw-r--r--features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/lib/derbynet.jarbin0 -> 213274 bytes
17 files changed, 7023 insertions, 0 deletions
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby-server.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby-server.bat
new file mode 100644
index 0000000..d5413e2
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby-server.bat
@@ -0,0 +1,2 @@
+@echo off
+call %~dp0\derby\bin\startNetworkServer.bat
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/CHANGES.html b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/CHANGES.html
new file mode 100644
index 0000000..0b13386
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/CHANGES.html
@@ -0,0 +1,1730 @@
+<html>
+<title>Changes for Derby 10.3.1.4</title>
+<body>
+<h1>
+<a name="Changes for Derby 10.3.1.4"></a>Changes for Derby 10.3.1.4</h1>
+<blockquote></blockquote>
+<ul>
+<li>
+<a href="#CHANGES">CHANGES</a>
+</li>
+</ul>
+<h2>
+<a name="CHANGES"></a>CHANGES</h2>
+<blockquote>
+<p>The following table lists issues in JIRA which were fixed between Derby release 10.3.1.4 and the preceding release 10.2.2.0. This includes issues for the product source, documentation and tests</p>
+<table border="2">
+<tr>
+<td><b>Issue Id</b></td><td><b>Description</b></td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2973">DERBY-2973</a></td><td>With collation TERRITORY_BASED, insert into table after changing type of column causes assert failure and loss of connection</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2966">DERBY-2966</a></td><td>rs.moveToInsertRow() causes loss of connection with TERRITORY_BASED collation.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2963">DERBY-2963</a></td><td>AccessControlException: Access denied java.net.SocketPermission &lt;client ip&gt; accept,resolve</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2960">DERBY-2960</a></td><td>Group by substr() on collated database causes ERROR XJ001: Java exception: 'ASSERT FAILED col1.getClass() (class org.apache.derby.iapi.types.SQLVarchar) expected to be the same as col2.getClass() (class org.apache.derby.iapi.types.CollatorSQLVarchar):</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2959">DERBY-2959</a></td><td>create table ... as select ... from systemtable with no data fails even when there is no character string type involved. This happens in a territory based database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2955">DERBY-2955</a></td><td>ERROR 42ZA2 creating table with check constraint with literal comparison</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2951">DERBY-2951</a></td><td>BatchUpdateTest.testAssociatedParams test fails with collation with exception: Java exception: 'ASSERT FAILED type of inserted column[0] = org.apache.derby.iapi.types.CollatorSQLChartype of template column[0] = org.apache.derby.iapi.types.SQLChar: </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2941">DERBY-2941</a></td><td>With 10.2, 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-2932">DERBY-2932</a></td><td>Connection.createClob() and Connection.createBlob() throw a procedure not found exception and do not switch to non-locator code upon soft upgrade</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2931">DERBY-2931</a></td><td>jdbcapi/ConcurrencyTest not able to drop table in soft upgrade mode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2925">DERBY-2925</a></td><td>Prevent export from overwriting existing files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2924">DERBY-2924</a></td><td>Manual copyright topics need to be updated to current year</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2923">DERBY-2923</a></td><td>Incorrect reading of nullable Blob/Clob columns during soft upgrade with client/server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2918">DERBY-2918</a></td><td>Errors in regression tests run against 10.3.1.1 release candidate</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2915">DERBY-2915</a></td><td>upgrade test fixture noConnnectionAfterHardUpgrade fails with 10.3.1.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2908">DERBY-2908</a></td><td>10.3.1.0 / 1.1.0 Derby eclipse plugin gives security error referring to user.dir read permission because derby.system.home is set to '.'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2896">DERBY-2896</a></td><td>DatabaseMetaData.getTables() fails in TERRORITY_BASED collation database with SQLState 42818: Comparisions between CHAR and CHAR not allowed.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2891">DERBY-2891</a></td><td>Clob.getCharacterStream(long,long) ignores position parameter for large (&gt;32k) CLOBs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2890">DERBY-2890</a></td><td>Simplify handling of maxPos in UpdatableBlobStream and ClobUpdatableReader</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2885">DERBY-2885</a></td><td>Wrong connection object used in EmbedConnection.clearLOBMapping()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2882">DERBY-2882</a></td><td>Remove references to JDK 1.2 and 1.3 in the documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2879">DERBY-2879</a></td><td>CREATE TABLE AS &lt;subquery&gt; does not maintain the collation for character types.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2874">DERBY-2874</a></td><td>NetworkServer not accepting connections with default security manager on Ipv6 machines</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2870">DERBY-2870</a></td><td>iepnegativetests_ES.sql fails: new canon needed?</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2868">DERBY-2868</a></td><td>BUILDING.txt doesn't mention junit.jar in list of jars installed in tools/java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2863">DERBY-2863</a></td><td>Collation doc corrections/improvements</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2862">DERBY-2862</a></td><td>ParameterMetaDataJdbc30 fails for weme6.1, which prevents rest of suites.All from completing.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2860">DERBY-2860</a></td><td>Documentation problems for IMPORT/EXPORT LOBs feature</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2858">DERBY-2858</a></td><td>Export exceptions swallow useful information</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2849">DERBY-2849</a></td><td>Add a documentation for derby.jdbc.xaTransactionTimeout system/database property</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2847">DERBY-2847</a></td><td>More clarification issues for the release notes.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2846">DERBY-2846</a></td><td>Fix wrong Javadoc in LOB related Update sensitive streams on the NetworkClient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2842">DERBY-2842</a></td><td>derbynet/testconnection.java fails with '...Connection refused: connect' expecting 'Connection refused'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2840">DERBY-2840</a></td><td>10.3.1.0 RELEASE-NOTES "Bug Fix" section's contents do not match the title or description</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2839">DERBY-2839</a></td><td>initial problems with the 10.3.1.0 beta candidate</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2837">DERBY-2837</a></td><td>Update docs on STRONG_PASSWORD_SUBSTITUTE_SECURITY/ENCRYPTED_USER_AND_PASSWORD_SECURITY and JCE support</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2831">DERBY-2831</a></td><td>NullPointerException creating a function in a schema that doesn't exist when the return type is a character type</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2830">DERBY-2830</a></td><td>Rename UpdateableBlobStream to UpdatableBlobStream</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2827">DERBY-2827</a></td><td>Rename ClobStreamControl to TemporaryClob</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2823">DERBY-2823</a></td><td>Rename ClobUpdateableReader to ClobUpdatableReader</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2819">DERBY-2819</a></td><td>Perform Doc Checklist for 10.3 Release</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2818">DERBY-2818</a></td><td>Rewrite ClobUpdatableReader constructors</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2817">DERBY-2817</a></td><td>Error messages for deadlocks contain less information than in 10.2</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2814">DERBY-2814</a></td><td>Specifying derby.* properties used in default policy file in derby.properties does not work</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2812">DERBY-2812</a></td><td>Assessing blob (when its linked to DVD stream, ie large blob) corrupts stream fetched prior to this access.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2811">DERBY-2811</a></td><td>Specifying -h 0.0.0.0 with default security manager bars clients from connecting from any host</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2809">DERBY-2809</a></td><td>Expressions with a parameter can be assigned the incorrect type</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2806">DERBY-2806</a></td><td>calling getByteLength on org.apache.derby.impl.jdbc.StoreStreamClob makes BinaryStream, fetched before this call, unusable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2805">DERBY-2805</a></td><td>ASSERT failure with sane build if DISTINCT and ORDER BY are present in a query that selects from a diagnostic table function.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2803">DERBY-2803</a></td><td>SSL certificate authentication succeeds unexpectedly</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2802">DERBY-2802</a></td><td>LOBStreamControl.replaceBytes can throw null pointer exception while trying to access databytes after calling init</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2800">DERBY-2800</a></td><td>Implement Clob.truncate for embedded driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2799">DERBY-2799</a></td><td>Intermittent failure in lang/deadlockMode.java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2796">DERBY-2796</a></td><td>Obscure error messages when using SSL in various combinations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2795">DERBY-2795</a></td><td>Unable to bring up server with SSL peer authentication enabled</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2794">DERBY-2794</a></td><td>Document ansi trim functionality</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2793">DERBY-2793</a></td><td>Ensure LIKE predicate follows correct rules for determing collation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2791">DERBY-2791</a></td><td>Copy/paste error in Admin Guide under Customizing the Network Server's security policy</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2789">DERBY-2789</a></td><td>DatabaseMetaData .locatorsUpdateCopy() should return true</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2788">DERBY-2788</a></td><td>Authentication tests fails with 'org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2787">DERBY-2787</a></td><td>make entry for clob in connection so that temporary file is removed when a connection is closed or transaction is commited/rolledback</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2784">DERBY-2784</a></td><td>With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2777">DERBY-2777</a></td><td>Parameters should take their collation from the context in which they are getting used rather than the current compilation schema</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2776">DERBY-2776</a></td><td>Internally generated CAST nodes should not use the collation of the current compilation schema. Instead they should use collation of target type passed to it.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2772">DERBY-2772</a></td><td>Create a procedure to empty the statement cache exposing the existing functionality.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2770">DERBY-2770</a></td><td>testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:&lt;XJ[073]&gt; but was:&lt;XJ[215]&gt;'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2768">DERBY-2768</a></td><td>Do cleanup (closing stmts., conns.) on failures in jdbcapi/BlobClob4BlobTest.java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2765">DERBY-2765</a></td><td>Make sure that all the DTDs for character string types have correct collation assigned to them.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2763">DERBY-2763</a></td><td>In the Network Client InputStreams and Readers returned from LOB's should be sensitive to underlying LOB data changes.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2758">DERBY-2758</a></td><td>ODBC metadata function "SQLForeignKeys" returns different results in 10.3.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2757">DERBY-2757</a></td><td>Do not require authentication when bringing up a security manager for the network server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2754">DERBY-2754</a></td><td>Client connections should not fail if permission is not granted to read derby.client.traceLevel and derby.client.traceDirectory</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2753">DERBY-2753</a></td><td>org.apache.derby.impl.drda.DDMWriter might swallow unexpected exceptions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2751">DERBY-2751</a></td><td>testLoadJavaClassIndirectly &amp; als fails on JVM 1.4 with "Unexpected SQL state. expected:&lt;[38000]&gt; but was:&lt;[XJ001]&gt;", "Jar file 'MY_JAVA' already exists in Schema 'EMC'"</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2748">DERBY-2748</a></td><td>TimeSlice and Socket-Timeout bounds checking wrong</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2744">DERBY-2744</a></td><td>jdbcapi/metadata.java and jdbcapi/odbc_metadata.java fail because of new procedure SYSCS_UTIL,SYSCS_GET_USER_ACCESS</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2743">DERBY-2743</a></td><td>Run 10.2 tests against 10.3 and evaluate to identify incompatibilities</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2742">DERBY-2742</a></td><td>LoopingAlphabetStream.read() returns invalid values</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2740">DERBY-2740</a></td><td>LIKE parameter marker combined with index multi-probing leads to ASSERT failure with sane jars, wrong results with insane jars.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2737">DERBY-2737</a></td><td>Change documentation on permissions needed to include read/write for system property derby.storage.jvmInstanceId </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2735">DERBY-2735</a></td><td>Add a system procedure to set a user's connection level authorization.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2730">DERBY-2730</a></td><td>Implement not implemented Embedded methods Blob.getBinaryStream(long pos, long length) and Clob. getCharacterStream(long pos, long length)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2729">DERBY-2729</a></td><td>temporary lob file should be cleaned when the transaction or connection is no longer valid.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2726">DERBY-2726</a></td><td>convert lang/AIjdbc.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2725">DERBY-2725</a></td><td>If all the operands involved in collation operation have a collation derivation of NONE, then Derby should throw an exception for that as per the SQL standards.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2724">DERBY-2724</a></td><td>Set correct collation type and derivation for result character string types from CURRENT ISOLATION, CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2723">DERBY-2723</a></td><td> Set correct collation type and derivation for result from user defined functions' that return character string type.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2722">DERBY-2722</a></td><td>Set correct collation type and derivation for result character string types from CHAR, VARCHAR and XMLSERIALIZE functions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2718">DERBY-2718</a></td><td>BlobClob4BlobTest and LobStreamTest fail creating database due to NullPointerException on weme 6.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2717">DERBY-2717</a></td><td>throw error if non-matching collation ids in like.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2716">DERBY-2716</a></td><td>lang.CollationTest2 failures on WEME 6.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2715">DERBY-2715</a></td><td>AssertionFailedError in LobStreamsTest and ClobUpdateableReaderTest on WinXP, Win2003</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2714">DERBY-2714</a></td><td>SecureServerTest spends five minutes waiting for a server to start</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2713">DERBY-2713</a></td><td>Ensure that a temporary file is not created for a lob obtained from resultset unless user updates it.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2712">DERBY-2712</a></td><td>If large clob is updated after Reader. the reader continues to point to old data</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2711">DERBY-2711</a></td><td>If large blob is updated after InputStream is fetched (using getBinaryStream), the stream continues to point ot old data</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2710">DERBY-2710</a></td><td>disable dynamic like optimization for collated databases</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2709">DERBY-2709</a></td><td>lang/ShutdownDatabaseTest, lang/StatementPlanCacheTest and lang/SysDiagVTIMappingTest keep references to closed JDBC objects</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2708">DERBY-2708</a></td><td>CanonTestCase keeps output from test in memory after it has finished</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2707">DERBY-2707</a></td><td>Inadequate clean-up in many jdbc4 tests</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2706">DERBY-2706</a></td><td>fix like clauses with trailing % </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2702">DERBY-2702</a></td><td>Enable Clob locator support between NetworkServer and NetworkClient and modify tests that experience changed behaviour due to this(enabling Clob Locators).</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2701">DERBY-2701</a></td><td>many sealing violation errors in ibm142 and ibm15 jvm test runs of junit tests.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2695">DERBY-2695</a></td><td>Add locator support of soft upgrade to 10.3</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2694">DERBY-2694</a></td><td>org.apache.derby.impl.drda.DDMWriter uses wrong algorithm to avoid spliting varchar in the middle of a multibyte char.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2693">DERBY-2693</a></td><td>Error in conrefs file reference in one Reference Manual file</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2692">DERBY-2692</a></td><td>Client driver doesn't chain exceptions received from the server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2689">DERBY-2689</a></td><td>Deadlock with GenericPreparedStatement</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2686">DERBY-2686</a></td><td>The skip method for some InputStreams and Readers return invalid values</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2684">DERBY-2684</a></td><td>NSinSameJVM regression test failure, "&gt; FAIL: Should have gotten exception"</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2673">DERBY-2673</a></td><td>If derby.system.home does not exist Derby should only attempt to create that specific folder, not any missing parents (ie. use File.mkdir(), not File.mkdirs())</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2671">DERBY-2671</a></td><td>Errors/messages early in starting the network server through NetworkServerControl.start() are not reported to the PrintWriter passed into start().</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2670">DERBY-2670</a></td><td>%a% and %aa% match too many rows in database with collation=TERRITORY_BASED and territory=no_NO</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2669">DERBY-2669</a></td><td>If no territory attribute is not specified at create database time, then we should ignore the collation attribute if specified.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2663">DERBY-2663</a></td><td>derbyall/derbytools/ij2 fails in derbyall run in the J2ME environment</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2662">DERBY-2662</a></td><td>DITA error in adminguide/cadminservlet98430.dita</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2658">DERBY-2658</a></td><td>Convert jdbcapi/parameterMetaDataJdbc30.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2657">DERBY-2657</a></td><td>Performance regression after check-in of svn 531971</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2656">DERBY-2656</a></td><td>Run suites.All against a collated database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2654">DERBY-2654</a></td><td>Document newly-supported (in embedded mode) JDBC methods for autogenerated keys.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2652">DERBY-2652</a></td><td>Clob.setCharacterStream differs between embedded and client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2647">DERBY-2647</a></td><td>.lang.ErrorCodeTest fails with 'Required Derby DataSource property {0} not set.'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2646">DERBY-2646</a></td><td>Cleanup of Clob control/support structures</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2645">DERBY-2645</a></td><td>upgrade test failures with weme 6.1.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2644">DERBY-2644</a></td><td>multiple junit failures during nightly of the form: 2) Encryption Algorithm: defaultjava.security.AccessControlException: Access denied (java.util.PropertyPermission derby.system.home read)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2642">DERBY-2642</a></td><td>Convert lang/dynamicLikeOptimization.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2641">DERBY-2641</a></td><td>Convert lang/staleplans.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2635">DERBY-2635</a></td><td>intermittent failure in T_RawStoreFactory unit test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2633">DERBY-2633</a></td><td>Authorization error codes have been moved. Translated messages must be moved accordingly.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2632">DERBY-2632</a></td><td>upgrade tests fail through BlobStoredProcedureTest and ClobStoredProcedureTest with JSR169</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2631">DERBY-2631</a></td><td>Expose existing auto-generated key functionality through more JDBC APIs in embedded mode.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2622">DERBY-2622</a></td><td>Fix build problems related to locator work</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2621">DERBY-2621</a></td><td>Fix javadoc issues related to locator work</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2619">DERBY-2619</a></td><td> A Derby source release must include the documentation source files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2616">DERBY-2616</a></td><td>intermittent network startup related errors in running junit nightly test suite</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2613">DERBY-2613</a></td><td>upgrade test problem when attempting to test 10.0.2.1 - </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2612">DERBY-2612</a></td><td>running soft upgrade of a 10.0 database vs. 10.3 software gives test error in testGetTablesModify concerning XML type</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2611">DERBY-2611</a></td><td>upgrade test incorrectly tries to test in place compress in 10.0 release.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2610">DERBY-2610</a></td><td>Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2609">DERBY-2609</a></td><td>The tests in ij7.sql are only performed in embedded mode.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2608">DERBY-2608</a></td><td>Compilation Error of manual in Apache FOP</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2607">DERBY-2607</a></td><td>DatabaseMetaData is not consistent about throwing SqlException when tablename=null</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2606">DERBY-2606</a></td><td>Derby should print the parameters to failed statements to the derby.log when it logs the error </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2605">DERBY-2605</a></td><td>You can create BOOLEAN columns in 10.3</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2604">DERBY-2604</a></td><td>Implement Clob support for locators</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2603">DERBY-2603</a></td><td>Minor erratum in page of VARCHAR in Derby Reference manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2600">DERBY-2600</a></td><td>Remove temporary code added to enable testing of CLOB locator related stored procedures.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2599">DERBY-2599</a></td><td>Set correct collation type and derivation on DataTypeDescriptor(DTD).</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2598">DERBY-2598</a></td><td>new upgrade test failures after change 528033</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2597">DERBY-2597</a></td><td>Language result sets should not reuse current isolation level across executions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2595">DERBY-2595</a></td><td>junit tests uses getExportedKeys with table name null</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2594">DERBY-2594</a></td><td>Revoking a privilege from an SQL Object should invalidate statements dependent on that object</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2593">DERBY-2593</a></td><td>Add documentation for the CREATE TABLE as subquery clause</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2591">DERBY-2591</a></td><td>DataDictionaryImpl.getSystemSQLName() may generate duplicates</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2587">DERBY-2587</a></td><td>Connection.createClob() and Connection.createBlob() need to return locator support enabled LOB objects in the NetworkClient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2586">DERBY-2586</a></td><td>BlobClob4BlobTest.tesPositionAgressive takes very long time</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2584">DERBY-2584</a></td><td>Creating a database with JPOX SchemaTool sometimes gives ArrayIndexOutOfBoundsException when getIndexInfo() is called</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2583">DERBY-2583</a></td><td>At code generation time, look at collation type to determine what kind of DVD should get generated for character types.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2581">DERBY-2581</a></td><td>Callers of SanityManager.THROWASSERT should chain the exceptions when possible</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2580">DERBY-2580</a></td><td>SanityManager.THROWASSERT(String,Throwable) ignores message argument</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2579">DERBY-2579</a></td><td>AssertFailure class should use JDK's built-in chaining of exceptions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2578">DERBY-2578</a></td><td>Change CurrentDatetimeOperatorNode to use ExpressionClassBuilder to generate code for DVD rather than going directly though TypeCompiler</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2577">DERBY-2577</a></td><td>convert jdbcapi/resultSetStream.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2570">DERBY-2570</a></td><td>Create a utility which generates Release Notes</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2568">DERBY-2568</a></td><td>'Connection refused' in jdbcapi/LobStreamsTest.junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2567">DERBY-2567</a></td><td>convert lang/errorcode.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2566">DERBY-2566</a></td><td>OutOfMemory/Sanity-assert failed when updating database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2565">DERBY-2565</a></td><td>BrokeredConnection needs to forward implementations of locator related methods in EngineConnection to the underlying physical connection</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2562">DERBY-2562</a></td><td>conver/SpillHash.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2561">DERBY-2561</a></td><td>convert lang/simpleScroll.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2560">DERBY-2560</a></td><td>Missing asserts in ProcedureInTriggerTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2558">DERBY-2558</a></td><td>client trhows ArrayIndexOutOfBounds exception instead of parameter out of range </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2556">DERBY-2556</a></td><td>Code paths for db restore do not use doPrivileged-calls, causing SecurityException</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2555">DERBY-2555</a></td><td>Remove use of doPrivileged in EncryptionKeyTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2554">DERBY-2554</a></td><td>convert lang/supersimple.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2551">DERBY-2551</a></td><td>Global Xid value garbled in syscs_diag.transaction_table.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2549">DERBY-2549</a></td><td>ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2545">DERBY-2545</a></td><td>testModifiesSql(org.apache.derbyTesting.functionTests.tests.lang.ProcedureInTriggerTest)junit.framework.ComparisonFailure: Unexpected SQL state. expected:&lt;3800[0]&gt; but was:&lt;3800[1]&gt;</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2544">DERBY-2544</a></td><td>SecurityPolicyReloadingTest( )junit.framework.AssertionFailedError: Policy file changed. Should not be able to read the property.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2543">DERBY-2543</a></td><td> testVirtualMemoryHeap junit test fails with "Virtual memory heap test failed! Got unexpected value. expected:&lt;202&gt; but was:&lt;103&gt;"</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2542">DERBY-2542</a></td><td>convert lang/scrollCursors1.sql to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2541">DERBY-2541</a></td><td>Create initial testing framework for Junit Collation testing</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2540">DERBY-2540</a></td><td>Restructure code for Blob/Clob length in client to prepare for locator implementation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2538">DERBY-2538</a></td><td>Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2537">DERBY-2537</a></td><td>implement pushing collation info to store, storing collation info in store metadata, and creating templates based on store metadata</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2536">DERBY-2536</a></td><td>Convert lang/procedureInTrigger.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2526">DERBY-2526</a></td><td>Wrong results with queries that use the JOIN ... ON syntax to join with views or other non-base table expressions.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2525">DERBY-2525</a></td><td>Convert lang/grantRevokeDDL and grantRevokeDDL2 to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2523">DERBY-2523</a></td><td>convert jdbcapi/LobTest to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2522">DERBY-2522</a></td><td>convert jdbcapi/procedureJdbc30.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2521">DERBY-2521</a></td><td>Building derby outputs (from ant) various information messages that are marked as warning severity.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2520">DERBY-2520</a></td><td>Document new restrictions of database shutdown, encryption and hard upgrade powers</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2519">DERBY-2519</a></td><td>Clean-up in BlobClob4BlobTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2517">DERBY-2517</a></td><td>convert lang/forupdate.sql to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2511">DERBY-2511</a></td><td>reference manual's description of JDBC4 features has misleading sections</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2509">DERBY-2509</a></td><td>Implement the XA transaction timeout support for client driver.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2508">DERBY-2508</a></td><td>Implement the XA transaction timeout support for embedded driver.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2506">DERBY-2506</a></td><td>Adding the locator information to FD:OCA descriptor (FDODSC) andFD:OCA data (FDODTA) of the SQLDTA objects</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2505">DERBY-2505</a></td><td>Convert derbynet/testij.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2502">DERBY-2502</a></td><td>Unclosed ResultSets choke JUnit lang _Suite on java 6</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2501">DERBY-2501</a></td><td>Batch scripts in bin\ report extraneous errors when DERBY_HOME is invalid</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2500">DERBY-2500</a></td><td>Assertion failure preparing query with AND and OR in where clause</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2497">DERBY-2497</a></td><td>convert lang/coalesceTests.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2496">DERBY-2496</a></td><td>Implement Blob support for Locators</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2495">DERBY-2495</a></td><td>Create framework for calling locator related stored procedures from client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2494">DERBY-2494</a></td><td>Convert lang/updateCursor.java test to junit test </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2493">DERBY-2493</a></td><td>Use unsynchronized collections in BackingStoreHashtable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2492">DERBY-2492</a></td><td>convert checkDataSource, checkDataSource30 and checkDriver.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2491">DERBY-2491</a></td><td>Convert distinct.sql to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2489">DERBY-2489</a></td><td>Document the policy-reloading system procedure.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2488">DERBY-2488</a></td><td>When loaded by jvm1.6 - EmbeddedConnectionPoolDataSource is not returning a JDBC 4 compliant PooledConnection object</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2484">DERBY-2484</a></td><td>Convert syscat.sql to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2480">DERBY-2480</a></td><td>DriverManager.getConnection leaks memory when connecting to a non-existent database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2478">DERBY-2478</a></td><td>'Invalid transaction state...' in jdbcapi.SetTransactionIsolationTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2476">DERBY-2476</a></td><td>convert lang/forbitdata.java test to junit test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2474">DERBY-2474</a></td><td>Convert jdbcapi/XATest.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2473">DERBY-2473</a></td><td>Compilation of reference manual translated into pt_BR seems to be failed</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2472">DERBY-2472</a></td><td>Use Throwable.initCause() to improve error reporting</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2467">DERBY-2467</a></td><td>Convert lang/updateCursor.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2466">DERBY-2466</a></td><td>Allow dynamic reloading of the security policy file</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2464">DERBY-2464</a></td><td>convert lang/ShutdownDatabase.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2462">DERBY-2462</a></td><td>org.apache.derby.impl.store.access.BackingStoreHashTableFromScan does not honor ResultSet holdability</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2461">DERBY-2461</a></td><td>Convert lang/procedure.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2459">DERBY-2459</a></td><td>Ordering on a CASE-expression casues a NullPointerException when using a UNION</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2458">DERBY-2458</a></td><td>Convert lang/unaryArithmeticDynamicParamter.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2456">DERBY-2456</a></td><td>File stream is left open when an exception occurs while setting up a character stream for data export.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2452">DERBY-2452</a></td><td>convert prepStmtMetaData.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2450">DERBY-2450</a></td><td>Clob.Position returning wrong value when operating on Reader</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2444">DERBY-2444</a></td><td>Implement not implemented methods Blob.getBinaryStream(long pos, long length) and Clob. getCharacterStream(long pos, long length) in the Network Client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2443">DERBY-2443</a></td><td>Implement ResultSet updateClob/updateBlob methods on the NetworkClient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2442">DERBY-2442</a></td><td>Remove code made redundant by DERBY-681</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2440">DERBY-2440</a></td><td>DerbyNetNewServer should specify port when it starts a server to avoid requiring 1527 to run</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2435">DERBY-2435</a></td><td>network server boot fails indicating authentication must be set up even when authentication is fully defined in derby.properties</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2434">DERBY-2434</a></td><td>HarnessJavaTest fails on UTF-8 locale.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2433">DERBY-2433</a></td><td>Error message when booting server with no authentication is misleading</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2432">DERBY-2432</a></td><td>Unimplemented transaction time out for XA transactions may cause that locks will not be released when client terminates outside a unit of work.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2431">DERBY-2431</a></td><td>Documentation for DatabaseMetaData should reflect that getColumnPrivileges and getTablePrivileges are implemented</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2430">DERBY-2430</a></td><td> setObject(int targetType, Blob source) and setObject(int targetType, Clob source) should disallow updates on all targetTypes except BLOB and CLOB respectively</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2429">DERBY-2429</a></td><td>Convert jdbcapi/resultset.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2427">DERBY-2427</a></td><td>jdbcapi/BlobStoredProcedureTest and jdbcapi/ClobStoredProcedureTest fail with weme6.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2425">DERBY-2425</a></td><td>ResultSetMetaData.getColumnDisplaySize() returns a negative value for BLOB columns for client </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2422">DERBY-2422</a></td><td>convert lang/holdCursorjava.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2418">DERBY-2418</a></td><td>TestProto.java used by testProtocol.java hardcodes port 1527</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2411">DERBY-2411</a></td><td>convert scrollCursors2.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2410">DERBY-2410</a></td><td>Convert grantRevoke.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2406">DERBY-2406</a></td><td>XAResource.end does not set the XA transaction state correctly when the XAException is thrown</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2405">DERBY-2405</a></td><td>Remove @author tags from the source files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2404">DERBY-2404</a></td><td>BadConnectionTest.java hardcodes port 1527</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2400">DERBY-2400</a></td><td>Javadoc - clean up Cloudscape references in javadoc</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2399">DERBY-2399</a></td><td>Convert setTransactionIsolation.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2395">DERBY-2395</a></td><td>Convert derbynet/csPrepStmt.java to junit test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2393">DERBY-2393</a></td><td>Change the test name from RunLangTest to RunOptimizerTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2391">DERBY-2391</a></td><td>"Derby and standards" section of Developer's Guide needs reorganization</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2390">DERBY-2390</a></td><td>DOCS - Merge Working with Derby and Getting Started Guide</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2387">DERBY-2387</a></td><td>DOCs - Reorder the topics in the Ref Manual into Alphabetical order - functions, procedures</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2386">DERBY-2386</a></td><td>timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2385">DERBY-2385</a></td><td>create the stored procedures called by LOB related JDBC methods during upgrade</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2383">DERBY-2383</a></td><td>ReuseFactory should use the constants in java.lang.Boolean</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2382">DERBY-2382</a></td><td>Convert casting.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2381">DERBY-2381</a></td><td>ParameterMappingTest fails due to ArrayIndexOutOfBoundsException executing a procedure</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2379">DERBY-2379</a></td><td>provide encryption support for temporary files used by lob if the data base is encrypted</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2378">DERBY-2378</a></td><td>SecureServerTest should not be using non-public apis</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2377">DERBY-2377</a></td><td>Document language based ordering which will be implemented by code related sub-tasks of DERBY-1478.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2376">DERBY-2376</a></td><td>Patch available to make .classpath entries portable - relative to ECLIPSE_HOME</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2375">DERBY-2375</a></td><td>jdbcapi/users2.sql and jdbcapi/secureUsers.sql fails on IBM weme 6.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2372">DERBY-2372</a></td><td>Document the secure-by-default network server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2371">DERBY-2371</a></td><td>Setting a default value for a VARCHAR column fails when column contains data</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2370">DERBY-2370</a></td><td>EXISTS may return the wrong value for sub-queries involving set operations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2369">DERBY-2369</a></td><td>NetworkServerControl.shutdown() takes at least 1.5 seconds, could be faster.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2368">DERBY-2368</a></td><td>Modify compatibility/testScript.xml to not run embedded/jvm1.3 case any more - not valid after r509863</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2366">DERBY-2366</a></td><td>Tests DerbyNetNewServer and SecureServerTest fails on weme 6.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2365">DERBY-2365</a></td><td>Brushing up pages for MAX and MIN in Derby Reference Manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2364">DERBY-2364</a></td><td>improve documentation to explain logged/unlogged operations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2361">DERBY-2361</a></td><td>Documentation should give examples for using the different security mechanisms</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2356">DERBY-2356</a></td><td>Make SSL server authentication optional</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2355">DERBY-2355</a></td><td>Wrong URL in Eclipse-Plugin Lab Example Jays.java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2350">DERBY-2350</a></td><td>Use of XML values in the action statement of a trigger throw exceptions.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2347">DERBY-2347</a></td><td>Add code to support request and return of locators over DRDA</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2346">DERBY-2346</a></td><td>Provide set methods for clob for embedded driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2345">DERBY-2345</a></td><td>truncate on a Blob does not work when the Blob is in memory</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2342">DERBY-2342</a></td><td>convert importExport.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2341">DERBY-2341</a></td><td>derby.language.statementCacheSize is ignored when it is set as a database property.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2339">DERBY-2339</a></td><td>org.apache.derbyTesting.functionTests.suites.All is extremely CPU intensive since ~svn 507489</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2336">DERBY-2336</a></td><td>Enable collation based ordering for CHAR data type.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2335">DERBY-2335</a></td><td>Compare character datatypes with different collation ordering.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2333">DERBY-2333</a></td><td>Convert parameterMapping to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2332">DERBY-2332</a></td><td>Convert old harness tests for statement caching into a single JUnit test class (with multiple fixtures)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2331">DERBY-2331</a></td><td>Disallow code in installed jars from resolving classes in the org.apache.derby.* namespace except for public apis.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2330">DERBY-2330</a></td><td>Disallow user-defined SQL routines to resolve to entry points (methods in classes) in the org.apache.derby.* namespace</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2329">DERBY-2329</a></td><td>Compatibility test fails in all combinations with 'serverTrunk', i.e. current trunk revision. (since tinderbox on svn 506771)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2328">DERBY-2328</a></td><td>Reduce monitor contention in SinglePool</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2327">DERBY-2327</a></td><td>Reduce monitor contention in LockSet</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2324">DERBY-2324</a></td><td>convert StmtCloseFunTest to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2323">DERBY-2323</a></td><td>Update Graphic in Dev Guide - Embedded deployment application overview</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2318">DERBY-2318</a></td><td>testStreams(org.apache.derbyTesting.functionTests.tests.lang.StreamsTest) failed on weme6.1 jvm/</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2315">DERBY-2315</a></td><td>compatibility/testScript.xml should include 10.2.2 in the server/client combinations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2312">DERBY-2312</a></td><td>Remove unwanted prints generated by the test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2311">DERBY-2311</a></td><td> Generate the txt and blobs required for the system tests dynamically </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2310">DERBY-2310</a></td><td>Improve the Readme.txt files in both the tests</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2309">DERBY-2309</a></td><td>Add build.xml, so that the code can get compiled using ant with the 'all' target.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2305">DERBY-2305</a></td><td>Convert tests in derbynet that will run via HarnessJavaTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2304">DERBY-2304</a></td><td>Convert derbynet/callable.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2302">DERBY-2302</a></td><td>AccessControlException for 'user.dir read' in ClientSideSystemPropertiesTest.testConnection</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2301">DERBY-2301</a></td><td>Documentation of different executeBatch error handling between embedded and DerbyNetClient needed</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2300">DERBY-2300</a></td><td>convert test lang/streams.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2299">DERBY-2299</a></td><td>convert cursor.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2296">DERBY-2296</a></td><td>getProperties method deprecated on ClientDataSource</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2295">DERBY-2295</a></td><td>DRDAProtocolTest:clientjunit.framework.AssertionFailedError</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2294">DERBY-2294</a></td><td>Missing sql script: '/org/apache/derbyTesting/functionTests/tests/lang/altertableDropColumn.sql'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2293">DERBY-2293</a></td><td>convert batchUpdate.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2283">DERBY-2283</a></td><td>convert lang/currentof.java test to junit test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2281">DERBY-2281</a></td><td>Update the Tuning Guide figure about using the statement cache</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2279">DERBY-2279</a></td><td>JDBC3 driver is loaded instead of JDBC4 when running with jdk1.7 </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2277">DERBY-2277</a></td><td>Make it possible to run the testsuite with jdk1.7</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2275">DERBY-2275</a></td><td>XSLT changes for PDF output</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2274">DERBY-2274</a></td><td>Implement testing for SSL communication</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2273">DERBY-2273</a></td><td>Implement SSL flag in datasource objects</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2272">DERBY-2272</a></td><td>SSL Documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2269">DERBY-2269</a></td><td>running tests (derbyall, or suites.All) with weme6.1 (or wctme5.7) with derbyrun.jar fails with NoClassDefFoundError: javax.naming.Referenceable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2268">DERBY-2268</a></td><td>AccessControlException when exiting junit.swingui.TestRunner</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2265">DERBY-2265</a></td><td>bad logic in jvm:guessWSHome() in old test harness affects j9 runs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2264">DERBY-2264</a></td><td>Restrict shutdown, upgrade, and encryption powers to the database owner</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2263">DERBY-2263</a></td><td>Update the copyright dita files to mark Derby logo images as non-substantive images (for accessibility)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2262">DERBY-2262</a></td><td>DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2260">DERBY-2260</a></td><td>DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2259">DERBY-2259</a></td><td>DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect information for types that cannot be searched.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2258">DERBY-2258</a></td><td>DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2257">DERBY-2257</a></td><td>Implementing the stored procedures called by the LOB related JDBC methods</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2256">DERBY-2256</a></td><td>Wrong Results: Use of decimal values in an IN-list with INTEGER left operand can lead to extra rows.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2249">DERBY-2249</a></td><td>Place holder to attach the long running test which will test Derby's improved optimizer</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2248">DERBY-2248</a></td><td>Place holder for the NetworkServer system test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2247">DERBY-2247</a></td><td>provide set methods for blob in embeded driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2244">DERBY-2244</a></td><td>DatabaseMetaData.supportsExpressionsInOrderBy() returns false</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2243">DERBY-2243</a></td><td>DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2241">DERBY-2241</a></td><td>compatibilitytest fails after DERBY-2121 change.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2237">DERBY-2237</a></td><td>Cleanup copyrights in the DITA source and generated docs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2236">DERBY-2236</a></td><td>Three tests from i18nTest fails on SLES with jdk1.4.2 when derbyrun.jar comes before derby.jar in the classpath</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2233">DERBY-2233</a></td><td>junit test derbynet/PreparedStatementTest fails with wctme5.7 (aka j9 2.2/ foundation/j2ME 1.0) and weme6.1 (aka j9 2.3 / foundation/j2ME 1.1) </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2230">DERBY-2230</a></td><td>AssertFailure: ByteCode Conditional then/else stack mismatch</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2228">DERBY-2228</a></td><td>Support Derby on J2ME/CDC/Foundation 1.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2226">DERBY-2226</a></td><td>Move column bitset computation to IndexToBaseRowNode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2224">DERBY-2224</a></td><td>Test harness should support J2ME 1.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2223">DERBY-2223</a></td><td>Let BasePage.fetchFieldFromSlot use the special single-col FetchDescriptor ctor</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2222">DERBY-2222</a></td><td>'show indexes in SCHEMANAME' does not work with the client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2220">DERBY-2220</a></td><td>Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2218">DERBY-2218</a></td><td>Null Pointer Exception when an untyped NULL subquery ("values null") appears outside of the FROM list in a SELECT query.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2217">DERBY-2217</a></td><td>Convert upgrade tests to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2216">DERBY-2216</a></td><td>Allow demo SimpleApp to work in J2ME environment</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2215">DERBY-2215</a></td><td>Nested test configuration decorators based upon ChangeConfigurationSetup do not work as expected.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2214">DERBY-2214</a></td><td>Fix Getting Started file to reflect classpath change</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2213">DERBY-2213</a></td><td>Support running Junit tests with just embedded jar file and testing jars.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2208">DERBY-2208</a></td><td>setNetworkServerCP scripts need not add derby.jar into the CLASSPATH</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2202">DERBY-2202</a></td><td>DROP PROCEDURE depends on SET SCHEMA</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2200">DERBY-2200</a></td><td>Add performance tests to Derby using the junit perf framework</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2199">DERBY-2199</a></td><td>BaseJDBCTestCase.assertSQLState should preserve the original exception</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2197">DERBY-2197</a></td><td>Remove unused code for locking rows while holding a latch</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2196">DERBY-2196</a></td><td>Run standalone network server with security manager by default</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2195">DERBY-2195</a></td><td>Nested triggers not working properly after maximum trigger count exception is thrown</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2194">DERBY-2194</a></td><td>A few more problems with Working with Derby manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2193">DERBY-2193</a></td><td>[import] ERROR 38000: StringIndexOutOfBoundsException was thrown while evaluating an expression.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2191">DERBY-2191</a></td><td>Cleanup of FormatableBitSet</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2184">DERBY-2184</a></td><td>QuickStart section of java/testing/README.htm should contain Sun JDK6 as supported java version for running tests</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2183">DERBY-2183</a></td><td>Trigger recompilation problem when trigger action has its table not qualified with a schema</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2179">DERBY-2179</a></td><td>suites.All fails after revision 483606 with ibm15</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2166">DERBY-2166</a></td><td>Implement proper handling of SocketTimeoutException in DRDAConnThread</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2158">DERBY-2158</a></td><td>test lang.UpdatableResultSetTest.testUpdateXXXWithAllDatatypes fails with wctme5.7 (j9) foundation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2157">DERBY-2157</a></td><td>SqlExceptionTest.testChainedException and .testNextException fail with wctme5.7 foundation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2155">DERBY-2155</a></td><td>checkDataSource and checkDataSource30 fail in the tinderbox test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2153">DERBY-2153</a></td><td>suites.All falls over with foundation after revision 482433; java.lang.NoClassFoundError: javax.xml.parsers.DocumentBuilderFactory</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2152">DERBY-2152</a></td><td>Support diagnostic vti tables that take parameters, such as SpaceTable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2151">DERBY-2151</a></td><td>"Fixer-upper" utility to help convert ij canon-based tests to JUnit.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2150">DERBY-2150</a></td><td>Reduce use of synchronized collections in GenericLanguageConnectionContext</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2149">DERBY-2149</a></td><td>Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2147">DERBY-2147</a></td><td>LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2141">DERBY-2141</a></td><td>BlobClob4BlobTest.testPositionBlob() fails with NullPointerException</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2140">DERBY-2140</a></td><td>BlobClob4BlobTest.testSelfDestructiveClob() fails with "ERROR X0X95: Operation 'DROP TABLE' cannot be performed on object 'TESTCLOB' because there is an open ResultSet dependent on that object."</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2138">DERBY-2138</a></td><td>Remove DataDictionaryContext and associated code</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2137">DERBY-2137</a></td><td>CALL (PROCEDURE) statement documentation in reference manual has incomplete syntax for arguments</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2135">DERBY-2135</a></td><td>add comment to messages.xml to ensure translations are kept in sync or removed when adding/removing parameters</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2124">DERBY-2124</a></td><td>Incorrect method name in error message for Connection.setTransactionIsolation method</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2123">DERBY-2123</a></td><td>Remove workaround for old JIT bug from StoredPage</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2122">DERBY-2122</a></td><td>Optimize ContainerLock.isCompatible()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2121">DERBY-2121</a></td><td>Remove JDK 1.3 build dependency in network server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2118">DERBY-2118</a></td><td>Change some boundary checks in ArrayInputStream to ASSERTs to improve performance</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2117">DERBY-2117</a></td><td>Intermittent failure in lang/compressTable.sql</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2116">DERBY-2116</a></td><td>Test files missing svn:eol-style</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2115">DERBY-2115</a></td><td>Some master files don't have the svn:eol-style property</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2114">DERBY-2114</a></td><td>Let Clock embed a HashMap rather than inherit from Hashtable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2112">DERBY-2112</a></td><td>Nullpointer on executeBatchRequestX when preparedStatement has no parameters</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2108">DERBY-2108</a></td><td>Implement SSL/TLS communication between client and server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2107">DERBY-2107</a></td><td>Move page latching out of the lock manager</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2103">DERBY-2103</a></td><td>After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2102">DERBY-2102</a></td><td>JDBC.assertFullResultSet should handle byte arrays</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2100">DERBY-2100</a></td><td>Convert derbynet/prepStmt.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2099">DERBY-2099</a></td><td>Make BasePage.getPageId() final</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2096">DERBY-2096</a></td><td>Change the Parser.parserStatement() to return the more specific StatementNode instead of QueryTreeNode.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2095">DERBY-2095</a></td><td>Add the ability to populate a database for the order entry toolkit based upon the TPC-C specification.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2093">DERBY-2093</a></td><td>Error in initSlotTable() can cause NPE or ASSERT rather than reporting page number in corrupt page message.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2089">DERBY-2089</a></td><td>jdbc4/VerifySignatures.junit is failing</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2088">DERBY-2088</a></td><td>Update the documentation templates. Add comment about changing the reference ID</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2087">DERBY-2087</a></td><td>Clean up of a database server directory after running junit tests.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2083">DERBY-2083</a></td><td>Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2067">DERBY-2067</a></td><td>Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2060">DERBY-2060</a></td><td>SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2057">DERBY-2057</a></td><td>SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE documentation or implementation error on its arguments.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2056">DERBY-2056</a></td><td>junitTests/derbyNet/CompatibilityTest.java fails with IBM JVM 142 and 15 on both Windows and Linux platforms</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2055">DERBY-2055</a></td><td>Add execution of the schema scripts for order entry</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2054">DERBY-2054</a></td><td>Rewrite 'derbynet/SuicideOfStreaming' to a JUnit test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2053">DERBY-2053</a></td><td>Dev Guide: Syntax errors in SQL tips -&gt; Tricks of the VALUES clause -&gt; Multiple rows</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2052">DERBY-2052</a></td><td>JDBC.assertRowInResultSet compares the wrong value if using trimmed strings and a SMALLINT column exists.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2050">DERBY-2050</a></td><td>Manipulating CachedItems could be more efficient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2049">DERBY-2049</a></td><td>Test jdbcapi/parameterMapping.java and lang/updatableResultSet.java are failing on J9 jvm ( J2ME Foundation Specification v1.0)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2048">DERBY-2048</a></td><td>LangScripts JUnit test fails in views.sql</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2047">DERBY-2047</a></td><td>TestDataSourceFactory doesn't work correctly outside the old harness</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2046">DERBY-2046</a></td><td>Make class org.apache.derby.iapi.store.raw.PageKey final</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2044">DERBY-2044</a></td><td>Add date, derby version and jvm version info to the report generated by the top-level ant target junitreport.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2043">DERBY-2043</a></td><td>NIST suite run as a Junit test fails on J2ME with WCTME 5.7</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2042">DERBY-2042</a></td><td>Provide documentation for new RENAME COLUMN statement</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2040">DERBY-2040</a></td><td>Setting derby.database.classpath to contain installed jars causes the database to be unbootable when a Securitymanager is installed.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2037">DERBY-2037</a></td><td>provide checking tool to flag possible errors in message translations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2036">DERBY-2036</a></td><td>junit testing with j2ME / wctme 5.7 foundation fails with java.sql.SQLException: org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2033">DERBY-2033</a></td><td>Convert lang/dcl.sql test to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2032">DERBY-2032</a></td><td>MathTrigFunctionsTest can be improved to execute in under ten seconds instead of its current eighty seconds</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2028">DERBY-2028</a></td><td>Make sure JUnit tests name their suites</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2027">DERBY-2027</a></td><td>JUnit suite All crashes with OutOfMemoryError when running LobLengthTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2025">DERBY-2025</a></td><td>convert lang/updatableResultSet.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2023">DERBY-2023</a></td><td>Ensure all tests called by jdbc40._Suite run in embedded and client as required.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2022">DERBY-2022</a></td><td>jdbcapi.LobStreamsTest runs only in client (not embedded) but its suite() method gives no reason why.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2020">DERBY-2020</a></td><td>Change file option for syncing log file to disk from rws to rwd</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2019">DERBY-2019</a></td><td>IJ's describe command does not handle quotes very well</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2018">DERBY-2018</a></td><td>NullPointerException in CREATE VIEW ... VALUES NULL;</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2007">DERBY-2007</a></td><td>Convert NIST suite to JUnit using the existing NistScripts JUnit test.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2006">DERBY-2006</a></td><td>Add JUnit and JUnitReport task as a target in Ant script</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2005">DERBY-2005</a></td><td>convert jdbcapi/Stream.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2003">DERBY-2003</a></td><td>Use a lower wait timeout in BlobClob4BlobTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2001">DERBY-2001</a></td><td>Add DITA templates for the 3 topic types into the trunk</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2000">DERBY-2000</a></td><td>A SecurityManager is not always installed when running JUnit tests/suites</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1995">DERBY-1995</a></td><td>Add base schema scripts for order entry</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1994">DERBY-1994</a></td><td>Implement data model for order entry</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1993">DERBY-1993</a></td><td>Check in the demo used by the Java in the Database session at Apachecon 2006</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1989">DERBY-1989</a></td><td>Convert jdbc4/TestDbMetaData.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1988">DERBY-1988</a></td><td>Convert jdbc4/TestJDBC40Exception.java to JUnit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1985">DERBY-1985</a></td><td>Use Calendar.setTimeInMillis(long) instead of Calendar.setTime(Date) for performance.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1983">DERBY-1983</a></td><td>Change build system so that base level is JDK 1.4</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1979">DERBY-1979</a></td><td>convert jdbcapi/characterStreams.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1976">DERBY-1976</a></td><td>Add new utility methods to BaseJDBCTestCase to make conversion of ij tests to JUnit easier.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1975">DERBY-1975</a></td><td>SQLAuthorizationPropTest cannot be run twice against the same database.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1974">DERBY-1974</a></td><td>Junit tests that require SQL authorization mode should use a different database to the default one.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1971">DERBY-1971</a></td><td>Make TestConfiguration set descriptive names for TestSuite objects it instantiates</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1965">DERBY-1965</a></td><td>NetworkServerControlImpl never closes the socket or streams it opens in setUpSocket.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1964">DERBY-1964</a></td><td>Update the documentation of SYSCS_UTIL.SYSCS_COMPRESS_TABLE for the changes that went in as part of DERBY-737</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1962">DERBY-1962</a></td><td>Convert jdbcapi/resultsetJdbc30.java to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1961">DERBY-1961</a></td><td>Investigate resource usage for different types of load on an in-memory database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1959">DERBY-1959</a></td><td>10.2 'Derby Developer's Guide' error/ambiguity.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1956">DERBY-1956</a></td><td>Remove stale code from the statement classes in the client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1955">DERBY-1955</a></td><td>Unquoted path in .bat files may cause errors (Win)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1953">DERBY-1953</a></td><td>Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1952">DERBY-1952</a></td><td>Remove the running of JUnit tests from the old derby test harness to allow faster conversion to a pure-Junit world.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1949">DERBY-1949</a></td><td>locate function documentation should clarify behavior when first parameter is empty string</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1947">DERBY-1947</a></td><td>OutOfMemoryError after repeated calls to boot and shutdown a database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1942">DERBY-1942</a></td><td>There exists difference between behavior of setNull(Types.TIME) and setTiime(null).</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1935">DERBY-1935</a></td><td>Reference Manual - Derby Limitations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1934">DERBY-1934</a></td><td>Reference Manual updates - J2EE Compliance: Java Transaction API and javax.sql Extensions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1930">DERBY-1930</a></td><td>Move JDBC implementation notes into the published javadoc</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1929">DERBY-1929</a></td><td>SYSTABLEPERMS and SYSCOLPERMS documentation needs to be updated</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1928">DERBY-1928</a></td><td>Update table "Support for SQL-92 Features: Basic schema manipulation" for GRANT/REVOKE</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1926">DERBY-1926</a></td><td>Provide documentation for ALTER TABLE DROP COLUMN</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1922">DERBY-1922</a></td><td>readme.html under frameworks does not mention about Derby client and some minor typos in example.html</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1920">DERBY-1920</a></td><td>DOCS - Improve topic titles for vague and duplicate topics</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1919">DERBY-1919</a></td><td>Top level index.html page should link to release notes and other items in top-level of a release.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1918">DERBY-1918</a></td><td>INCREMENT of IDENTITY column described as allowing a value of zero in reference manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1917">DERBY-1917</a></td><td>Clob.position fails with Embedded driver and large Clobs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1909">DERBY-1909</a></td><td>ALTER TABLE DROP COLUMN needs to update GRANTed column privileges</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1895">DERBY-1895</a></td><td>Convert jdbcapi/blobclob4BLOB.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1890">DERBY-1890</a></td><td>improve XSDFI error message</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1889">DERBY-1889</a></td><td>Convert jdbcapi/lobStreams.java to Junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1879">DERBY-1879</a></td><td>Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1874">DERBY-1874</a></td><td>largeDataTests/LobLimits master needs update for new exception names</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1869">DERBY-1869</a></td><td>lang/timestampArith.java fails if it starts right before midnight</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1868">DERBY-1868</a></td><td>Merge argument descriptors into SQLState strings so that SQLState documentation can be generated by a program</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1867">DERBY-1867</a></td><td>Document algorithm support required for using secmec 8(USRSSSBPWD) and limitation on ibm141 vm.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1861">DERBY-1861</a></td><td>Column ordering ASSERT when combining column references and expressions in same ORDER BY</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1852">DERBY-1852</a></td><td>Wrong results: duplicate rows returned for nested UNIONs when they should be eliminated.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1847">DERBY-1847</a></td><td>SELECT statement asserts with XJ001 when attempted to select a newly added column in SQL authorization mode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1841">DERBY-1841</a></td><td>lang/groupBy.sql fails with IBM j9 vms</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1828">DERBY-1828</a></td><td>Access rule violations should use a SQL state starting with '42' according to the SQL standard.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1822">DERBY-1822</a></td><td>LOCK TABLE example and description in reference manual should get replaced by a 'real' example</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1816">DERBY-1816</a></td><td>Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1815">DERBY-1815</a></td><td>In admin guide examples to start network server on windows with .bat scripts, $DERYBY_INSTALL Is used , I think it should be %DERBY_INSTALL%</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1814">DERBY-1814</a></td><td>Tests should always be compiled with line number information.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1805">DERBY-1805</a></td><td>Links to element ids inside a topic are broken in PDFs and HTML Books</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1797">DERBY-1797</a></td><td>Building toursdb would go a little faster if it used autocommit off mode.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1795">DERBY-1795</a></td><td>Graphics not copied over for PDF and HTML-single manuals</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1791">DERBY-1791</a></td><td>Make policy file and harness tests cope with derbyTesting being in a different folder (test) to the other jars.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1765">DERBY-1765</a></td><td>Update ALTER TABLE documentation to reflect DERBY-119 (ALTER COLUMN [NOT]NULL)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1760">DERBY-1760</a></td><td>remote server testing with 10.2 snapshot showed 8 failures</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1758">DERBY-1758</a></td><td>Enable xmlSuite to run as part of derbyall in environments that have the required external jars.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1753">DERBY-1753</a></td><td>Doc for SYSCS_INPLACE_COMPRESS_TABLE has incorrect procedure name in the java examples.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1752">DERBY-1752</a></td><td>Fix javadoc to account for changes required by new licence header policy.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1746">DERBY-1746</a></td><td>upgrade tests should start using 10.1.3 released builds</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1712">DERBY-1712</a></td><td>Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1709">DERBY-1709</a></td><td>Deprecate scripts in frameworks directory</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1704">DERBY-1704</a></td><td>Allow more concurrency in the lock manager</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1673">DERBY-1673</a></td><td>Compling with jikes not longer works due to recent changes that added -target -source command line flags to each compile</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1665">DERBY-1665</a></td><td>Incorrect JavaDoc for Qualifier interface</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1662">DERBY-1662</a></td><td>Document derbyrun.jar</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1644">DERBY-1644</a></td><td>NPE when inserting values to a table that has a column declared as generated by default as identity</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1624">DERBY-1624</a></td><td>use of direct column name rather than alias make aggregation fail (Hibernate depends on that)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1623">DERBY-1623</a></td><td>Add ANSI TRIM implementation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1620">DERBY-1620</a></td><td>SQL CASE statement returns ERROR 42X89 when including NULL as a return value</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1610">DERBY-1610</a></td><td>Resolve difference of type compatibility between Embedded and NetworkServer/NetworkDriver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1606">DERBY-1606</a></td><td>derbyrunjartest hangs with wctme5.7 &amp; always uses j9_13; hangs with _foundation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1590">DERBY-1590</a></td><td>Consolidate the *conrefs.dita files in the documentation source tree to a single file.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1589">DERBY-1589</a></td><td>CREATE TABLE throws NullPointerException in Derby SQL Standard Authorization after DROPs and REVOKES</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1588">DERBY-1588</a></td><td>Link "Getting Started...." and "Apache Derby Server ...." in demo.html needs to be linked to actual documents instead of manuals page</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1570">DERBY-1570</a></td><td>The derby configuration, logging and diagnostic properties such as derby.language.logStatementText are hard to find in the documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1558">DERBY-1558</a></td><td>enable more testcases in ConcurrencyTest</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1557">DERBY-1557</a></td><td>Add a JUnit test decorator that creates a database at setUp and removes it at tearDown.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1556">DERBY-1556</a></td><td>Add a utility JUnit test decorator that drops all SQL objects in its tearDown method.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1535">DERBY-1535</a></td><td>Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1526">DERBY-1526</a></td><td>build should be able to locate the Java runtime libraries from properties not sourced from ${user.home}, but inside the current subversion checkout.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1520">DERBY-1520</a></td><td>Document new SYSCS_DIAG tables</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1519">DERBY-1519</a></td><td>'setAsciiStream' uses different encodings for embedded and client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1501">DERBY-1501</a></td><td>PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1496">DERBY-1496</a></td><td>testSecMec needs many masters - should convert to junit</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1494">DERBY-1494</a></td><td>PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1490">DERBY-1490</a></td><td>Provide ALTER TABLE RENAME COLUMN functionality</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1489">DERBY-1489</a></td><td>Provide ALTER TABLE DROP COLUMN functionality</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1484">DERBY-1484</a></td><td>Client and embedded behave differently when the table name is null in DatabaseMetaData methods</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1440">DERBY-1440</a></td><td>jdk 1.6 client driver omits SQLStates and chained exceptions in error messages</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1434">DERBY-1434</a></td><td>Client can send incorrect database name to server after having made multiple connections to different databases.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1381">DERBY-1381</a></td><td>Document ij.exceptionTrace property</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1377">DERBY-1377</a></td><td>Update copyright headers to comply with new ASF policy</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1355">DERBY-1355</a></td><td>ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1341">DERBY-1341</a></td><td>LOB set method(s) are currently no supported, but part of the Java 1.4 JDBC interface</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1285">DERBY-1285</a></td><td>Finish JDBC3 Blob implementation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1275">DERBY-1275</a></td><td>Provide a way to enable client tracing without changing the application</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1132">DERBY-1132</a></td><td>Truncation Error with Concat</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1122">DERBY-1122</a></td><td>Improve base JUnit testing classes</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1054">DERBY-1054</a></td><td>Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1001">DERBY-1001</a></td><td>Rewrite 'store/encryptionKey.sql' to a JUnit test</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-967">DERBY-967</a></td><td>lang/autoincrement.sql intermittently fails on SunOS-5.10_i86</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-931">DERBY-931</a></td><td>Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-908">DERBY-908</a></td><td>YEAR,SECOND,MONTH, MINUTE, HOUR and DAY functions have incorrect information on durations.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-815">DERBY-815</a></td><td>Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-812">DERBY-812</a></td><td>Scripts to publish Derby test results</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-806">DERBY-806</a></td><td>One each deleted or updated from a heap row a new RowPosition object is created.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-801">DERBY-801</a></td><td>Allow parallel access to data files.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-790">DERBY-790</a></td><td>SQLException used by the networked interface to Derby is not serializable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-729">DERBY-729</a></td><td>Scalar time and date functions return 0 instead NULL when argument is NULL</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-681">DERBY-681</a></td><td>Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-680">DERBY-680</a></td><td>In ij, executing a prepared statement with numeric/decimal parameter fails with NullPointerException in J2ME/CDC/FP</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-630">DERBY-630</a></td><td>create trigger fails with null pointer exception</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-606">DERBY-606</a></td><td>SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-595">DERBY-595</a></td><td>Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-552">DERBY-552</a></td><td>Fetching resources using getResourceAsStream from a jar stored in a database that is archived in a jar file fails</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-538">DERBY-538</a></td><td>Investigate using the standard java.net.URLClassLoader for database class loading.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-537">DERBY-537</a></td><td>SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-415">DERBY-415</a></td><td>sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-396">DERBY-396</a></td><td>Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-391">DERBY-391</a></td><td>Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-378">DERBY-378</a></td><td>support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-264">DERBY-264</a></td><td>This enhancement to allow expressions in ORDER BY clause will require documentation changes.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-234">DERBY-234</a></td><td>Documentation of DateTime types is incomplete</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-208">DERBY-208</a></td><td>Add support to retrieve lobs for Network Server by locator rather than matierializing the LOB</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-183">DERBY-183</a></td><td>Parameter names required in CREATE FUNCTION</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-147">DERBY-147</a></td><td>ERROR 42X79 not consistant ? - same column name specified twice</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-64">DERBY-64</a></td><td>Create a table with a query</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-47">DERBY-47</a></td><td>Some possible improvements to IN optimization</td>
+</tr>
+</table>
+</blockquote>
+</body>
+</html>
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/KEYS b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/KEYS
new file mode 100644
index 0000000..17d145d
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/KEYS
@@ -0,0 +1,536 @@
+iThis file contains the PGP keys of various developers.
+
+Users: pgp < KEYS
+ gpg --import KEYS
+Developers:
+ pgp -kxa <your name> and append it to this file.
+ (pgpk -ll <your name> && pgpk -xa <your name>) >> this file.
+ (gpg --list-sigs <your name>
+ && gpg --armor --export <your name>) >> this file.
+
+pub 1024D/AB1B7EE4 2004-08-12 Daniel John Debrunner <djd@debrunners.com>
+sig 3 AB1B7EE4 2004-08-12 Daniel John Debrunner <djd@debrunners.com>
+sig 3 B1669287 2004-08-13 Katherine Marsden <kmarsden@Sourcery.Org>
+sig 3 AB821FBC 2004-08-26 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 99586C26 2004-08-27 Jean T. Anderson <jta@bristowhill.com>
+sig 3 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sig 3 21EA3ECD 2004-08-27 Mike Matrigali <mikem_app@sbcglobal.net>
+sub 1024g/96268F22 2004-08-12
+sig AB1B7EE4 2004-08-12 Daniel John Debrunner <djd@debrunners.com>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.4 (Darwin)
+
+mQGiBEEbfSwRBAC/KAN4hHUgL0hMc0+ooUY9t43Pkw1rf5OSo3eMA3an46v1hQ29
+vh4nCeiwWtj56wtSxQPCR79ZNEBzsXy90UoAjLiQt5P5unqzq7SAkJxmk+Ch3ckZ
+NfLsz8YASXAuAWb8z884BQIJKdBOtD3gzqOAZArQw1Y2VRUe4X/7b3cvDwCg5mTX
+gNeGNqmMgd86XVuqbRIOBoUD/iuGr9RFkuASmNa9s1DGbIOkDNU4OITk+cBv0o0W
+FCDcAOjW3OqjQPDZYjwHUuHn0nklPPOPh96GUlnDvImH2Za2Y4XgClApg0kKCkhC
+X6Bu1oGKQglkByqttiu/0g+vZfblV31GXYg+W3N/q29UBG8zkldXeW1rV/VDKc+a
+7gbBBACgEQArU2h/g5iwNUArzxRw478s7sLwMTxRP00DfUwTyMdxuEAufmEqwDCd
+yflciEotUDNJusCs/a77i8eZrCQerIr9ZoexuNg/ByCV1OdorQSuGked16d4FUmx
+aS1Ucrz/9iuTYZuTEmw/+9jAAQZbuaWstLLuFrzZ+G3QN3IUH7QqRGFuaWVsIEpv
+aG4gRGVicnVubmVyIDxkamRAZGVicnVubmVycy5jb20+iF4EExECAB4FAkEbfSwC
+GwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQIv0S4qsbfuRY1QCdHIBpUeda6uk8
+mc5M2QuzGh/lnK4AoKuHzHd7qJgCbUWjA8s+rLdF9E9RiEYEExECAAYFAkEdCcsA
+CgkQG0h36bFmkof0TgCbBX4Ob3HZmdvWPXOULaRinQfizM4AoMbYpk1ePa+QsoWU
+J0hZUseBtj9/iEYEExECAAYFAkEuXeQACgkQDfB0XauCH7zbyACgknmFlPN8pVZV
+p2woh119orkI1kkAn20jQMyTX6gi+rRcwm/nmYP1R1GRiEYEExECAAYFAkEvhFsA
+CgkQF0L6u5lYbCZ5KgCfRY9ehWdrJ2X829WnVw9BXxQhN1EAoJ/ffCdCXFMWxtXi
+nU3PqmLIPNSxiEYEExECAAYFAkEvcKcACgkQENVNIY6DZ7F1BwCgpBMHfDAdtPP0
+XLwMXsg4IaIp+R4AnjxR64hvnire7nuCj+iJnKaBXTy1iEYEExECAAYFAkEvxf8A
+CgkQEpeslyHqPs2XFgCg2x3X5ov29fQ3bGFZp1zOGg3OmDcAoOQKzgxE6FuFqN9q
+9O3zMakQ9GckuQENBEEbfS0QBADDEjCsdHtVSfZ20OZMyoskjcBpaWJidRM1vmgU
+ePXMTrUJWR9SvFiNk9eXhpF31CjlB8D+nbtqjLMFsI82Po8dY1kRQxUHUEUTyeNw
+Kt8HGzVDHyBbOqDbUFpfsgU7gal7pgkq7K/dkDfaKXEPG9pqnE4rYmjdPAbkWyNq
+6lvRtwADBwP/ZCbCWczliovWLo6t2pOty8C7RzjyG0T/JorGTqZJX/Ph7pcnkeP8
+ryI5zBksqrN4+HVcLbpLwnUS7nzi9cw+W9aCJ23qLMiy3lbhYKCcDx70e1qsWprS
+za1XeQXNkjxAbG828l8JTbd0eFBuCFVFHnzl/Goy0AmqfTYriwsLbLGISQQYEQIA
+CQUCQRt9LQIbDAAKCRAi/RLiqxt+5OAlAKC+zemlVdvOHhVVbPAkgDxjK9fA9wCg
+ks0SzqIiYE5NOS67we11MZgrzM0=
+=S3Gw
+-----END PGP PUBLIC KEY BLOCK-----
+
+pub 1024D/AB821FBC 2004-07-20 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 AB821FBC 2004-07-20 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 B1669287 2004-08-12 Katherine Marsden <kmarsden@Sourcery.Org>
+sig 3 99586C26 2004-08-26 Jean T. Anderson <jta@bristowhill.com>
+sig 3 AB1B7EE4 2004-08-26 Daniel John Debrunner <djd@debrunners.com>
+sig 3 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sig 3 21EA3ECD 2004-08-31 Mike Matrigali <mikem_app@sbcglobal.net>
+sub 2048g/7A461F74 2004-07-20
+sig AB821FBC 2004-07-20 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.4 (Darwin)
+
+mQGiBED9lBURBADWhKzOmdwVwcFpgRBn0E9eltDrlkLGU3hDYMa/udM9+9k0SuBq
+YfMWYPWL40yPpCJ0wh72/KRUgoIcVbPX3hWAsWRxb8cG/zsYDyidkX2nvNycQ7Pp
+o9EsV8cyQ0Soaix8TgJBO35mw3pSiOMZv+U+iHXkh6efO4wpzPaBRB5BVwCgqcgP
+SznlslAu4HWnxHk+PWLu+sEEAJ3jNjEIX4biNpdoWKLAHw5MICXdxN9fW32Ft2QQ
+891kuusbrjxgUz48qV/ovHWUsMyRwiKzwrS/rJhX7L/bQ/pBG/rb0Y5rpeeqlvV5
+z1/ehAWv9M16aX7rgYTf1uSj03pEJdBD7TgoCATtkO+J7tWZ3u8wPlfno5HiDKly
+iiacA/48owwiRyj1HfQG+5caOpNtTdDNKf0Hc5Z9pd8vMW1bDadHaKV3cvQtCeEj
+kpu+tV6sSMMsynBHVDChA5681BBMBMPs4JxwpLaYvG0UEjRxgwhLAdY+C40XExmU
+hzI6ZgAZ0VXl6VB7EhIGUmwnyq06zBgEYkK8dvK6JXjo1SnnGbRLU2FtdWVsIEFu
+ZHJldyBNY0ludHlyZSAoQXBhY2hlIERlcmJ5IFByb2plY3QpIDxmdXp6eWxvZ2lj
+QG5vbmludHVpdGl2ZS5jb20+iF4EExECAB4FAkD9lBUCGwMGCwkIBwMCAxUCAwMW
+AgECHgECF4AACgkQDfB0XauCH7zx7gCgkPzqYiB+1yZFoqhdO3jpZaD71skAn13J
+dgBBcHr5iRnHnUG3nfFJFB9/iEYEExECAAYFAkEb/r8ACgkQG0h36bFmkocobACf
+Vkbp4x+wDqVz7Sw1dIarxu8aBQcAnjXK54MbC8jNHhhX7vYIkUc8wg14iEYEExEC
+AAYFAkEuY6kACgkQF0L6u5lYbCYr9ACcD8S1yfNDBYnbkmx6FCL4o7OSBDwAnjhQ
+Jju8OZcvLIeYZe3I2AESdIEaiEYEExECAAYFAkEucX8ACgkQIv0S4qsbfuQ73ACf
+UltK+Q51Jm+/ZQ4YvYJ69oHURPYAnAvAAKmVwIVfHqANkxmvlMVRTuM0iEYEExEC
+AAYFAkEvb+MACgkQENVNIY6DZ7EZVACfdK+6h+ZqKoAh6RocBL66kKKvQ+cAnRyp
+xgjXxKIFo6pwTTeiHVweW44ViEYEExECAAYFAkE0/2EACgkQEpeslyHqPs3F9gCe
+NV5EIst5TM+KA75GNFvxUer2lXkAoOOc8p5n8rTYP8mpYUPx6gwpoS+/uQINBED9
+lSQQCAClI+JDrIyy7VH0pLQlW8YPkz9PNyyNbexuzR/jmW85PGeHHI0t1/lKChVe
+b22XX8wS2kLJqePGVIKHTsdb1PoyoLrF+oKe83M4iNesT5uGtCa6p+jpjDWptdgW
+wUkDhye3n07Zm16sWyfRMeUvJHPhHTATCYQraBWDUw+6UGJd946qX2FfMohamzMY
+bJuB6CXB4foIdPHJSFnS2M3ZSSWIG7RsILd5/zHr2poxWYfbQbnEW8HcrFkmY9qD
+/YNpXY+pTW71gsKvL1xLBBB4MItcZxpcGJzew9HJZyNUImiIznkUhzPxDpGCq0HV
+fEVFWbwNjEBmv8rUGCJk4fAMDiJrAAMGCACChXiQ6HYpjd7i7MekroD1pJLbriBJ
+GqbxwcquxAGldwee3HfL1isoQSuib74MPP6bv5/6ul9+r4DETKA/NyDF5952tFkr
+FL68hvpihuEHzSfD0oBI/AAvlCZyO9ncvx/qq4VhTIt9/NjbyJv3HQXdFAI6Sjq7
+NS5xEPWixyozqJeTHLB/0xF8Ed0YJOTSIB3mnMt3TEhjGVAfNwTcasMLKCDxEmYH
+bmghGayRorXawISINBJAgrSmyZK9TI27YnefOZgSkLqZ3V2i7sAy34fLbDOsl30i
+PDcOXxykzr32JZ4j9IxPlfq7BvDAzH6u6+2LSUwZGoI3kKAO8sEiHL4JiEkEGBEC
+AAkFAkD9lSQCGwwACgkQDfB0XauCH7zAlwCePWwR/FfzWNlOSOpwp2Rpb6PpB+UA
+njcL3Dmrk2xcuaQBRUk+uIiyGJfM
+=C/fM
+-----END PGP PUBLIC KEY BLOCK-----
+
+pub 1024D/21EA3ECD 2004-08-27 Mike Matrigali <mikem_app@sbcglobal.net>
+sig 3 21EA3ECD 2004-08-27 Mike Matrigali <mikem_app@sbcglobal.net>
+sig 3 AB821FBC 2004-08-28 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 B1669287 2004-08-27 Katherine Marsden <kmarsden@Sourcery.Org>
+sig 3 99586C26 2004-08-27 Jean T. Anderson <jta@bristowhill.com>
+sig 3 AB1B7EE4 2004-08-27 Daniel John Debrunner <djd@debrunners.com>
+sig 3 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sub 2048g/0FA646B3 2004-08-27
+sig 21EA3ECD 2004-08-27 Mike Matrigali <mikem_app@sbcglobal.net>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.4 (Darwin)
+
+mQGiBEEvfQARBACnZcCpdMMWQbNdM5RNI6tee2ZrjVBqMidQ5iVUOswVOckSyRX/
+ItQInQil/dotZmaBHp4Og05SV9G4h+8E6PrjlcY5D2ieWb9IUAOmBAV3IKSFFboG
+pvfmpZilPFcxUo4RrAhi5lhQx8RNZ9LsZPBmKQAS+tnvvWv+2oFQm6MdxwCg9+wB
+zgBvoadGD6bk4LV5t2yLK3kD/2GryQIcXpsg384WpFLcC9xTmzcZM8DS4UlRh/Y1
+nkNz5I9acaU5MRx0MsWRTLDCqmPd2Ib5ipemb8pyHbyT6jzFgfC+Y6IuZmiGEDmu
+dfTDb6tsE55cXDRFrzdelmgX1X5ORFV6PNOMXukXBX9Ms49pE7phaZLQY+bHULXF
+sJKHA/92EOCuQPDpDcE/YUtVVMWKsqBcrpdGdEkfYBS+ooB4AZ61Y6hkXWRB/1ly
+YBdcEpwsNPweky3OecGA57+1ojmmTjKr0qQEjlLGAF//pBQ87ZvvN7qM1htrCAVD
+ZIS6c2A/MFzozwsKm4r95+PvnfbCWbLJqudTzI9k90tqDyfk+7QoTWlrZSBNYXRy
+aWdhbGkgPG1pa2VtX2FwcEBzYmNnbG9iYWwubmV0PoheBBMRAgAeBQJBL30AAhsD
+BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEBKXrJch6j7NbEAAn2Q10H3P47+/oXTZ
+E8SMnYLhmmAfAKDSqmVKXt+JGzHUJnSCvPCguz4HF4hGBBMRAgAGBQJBL+TCAAoJ
+EA3wdF2rgh+8Z74An2UOErmEfAQp6oaJIoY/OOkVq7DmAJ0ZYDMEM5zPfxwrJX8k
+CMVAJK+KbIhGBBMRAgAGBQJBL77+AAoJEBtId+mxZpKHbcoAoKtwjGdwiULxlzBB
+XWFZNOrygwj/AKCJPf6S6WQTe9KAE9AhnZrbYP4X6ohGBBMRAgAGBQJBL8D1AAoJ
+EBdC+ruZWGwmZoIAmwVJpH0erDLxvyUhJQJeo5zCCc46AJ4zNwbBpLQaahmvV2ex
+8+g/Hs3GJ4hGBBMRAgAGBQJBL8E5AAoJECL9EuKrG37k5JsAoM/b3OMR3zx+maBH
+P0tLaLr4iufgAJ9yTyy7szZDaC2Vro9qL5xpUm70GohGBBMRAgAGBQJBL8QWAAoJ
+EBDVTSGOg2ex48sAn3KR4fGln1tHbWowJo/QUt5SjdE0AJ9lbRVhauQfhsZooVCS
+2ucp6UZtgbkCDQRBL30REAgAhLQS7DxyODVNzyffHFPDGYOqgk0RxKZMFs2WxYr/
+XFcwn0WGDJuVjZ24/TFGdtiAjst8jer/a2yPI5riI8X30cmeZlmazN18jGKFufny
+PP2KmXvkMNbjDUhXk1Dv4aO0a0JI1pIu5BS+Dtp7oWjsd/tU6u7EzV9kSxC7NWxe
+JP6Dz6GrMSQZCE3WhxwyJxxgpvl2jpcmmwd0DMaiNvi49EXLoG/gYI8RsyVFxOSS
+xA4zYW/0+bh1eVfXSztndQBYsfTFf3wraTX8ddiFr3lW9VuL2XwKFxx4F+I2qGhU
+REte9fHnJm9kQc/UEKmLWJKDJTAU+yWLpVEs0w5Qx3uwPwADBQf9GaiXsDYHBYa/
+vBApAWD47YGImBqOie+Wj9NoX1eh/nPP7CnwUhK/lW4mRgQcP//0ZC7sTpYINBWn
+a1ET1lKCjLCOT1YTLtTS0Z9iWzCmBY4iRh5J2gpSErKuj2e9tR1ir/AC7hv0se8N
+GjpCpnzZitewWX2LmFEpRhe0bVpsduK9j6rqJvHF4m3XDRUlsuqWa9fgS4PwyHeB
+hRxHBiWEiUpaCuP7TM3J+wvdFhZtgTYngJVbgjt0jGo4tovTiMCaX5YX+ENYxnu9
+1Zsv+EzjeLgQpvDWhSkuVAN2C+yU21m4zzmntfN6jjZll7kMIBRKNbNE9fqYn7FE
+VNcpll8ptohJBBgRAgAJBQJBL30RAhsMAAoJEBKXrJch6j7NXdkAnA1P7cVpoAx4
+5enoz93olfon51rWAJ9ntmliCpgkFnIhjxezC4KtCt6lPw==
+=w60g
+-----END PGP PUBLIC KEY BLOCK-----
+
+pub 1024D/8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sig 3 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sig 3 B1669287 2004-08-27 Katherine Marsden <kmarsden@Sourcery.Org>
+sig 3 AB821FBC 2004-08-27 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 99586C26 2004-08-27 Jean T. Anderson <jta@bristowhill.com>
+sig 3 21EA3ECD 2004-08-28 Mike Matrigali <mikem_app@sbcglobal.net>
+sub 1024g/CFDFAA50 2004-08-27
+sig 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.4 (Darwin)
+
+mQGiBEEugQoRBACP7Wa5vUIclXfyZu5JC/VpY0jRCnf3/zktvHOhxFyQANbdBc5E
+hGyXZZ+sE2jqyr/XLXNaChbrS0NTrWph1WoW5JrWBKJF8/YJ5tY6d2fIeZnomopy
+78yNHPuRuNo+E0C+trLjWWY8ewBg6mdvoW6Q+LEujeoE1sUXiFIZH5PGDwCgujqh
+NpFzLG7TQUBnBYCRgTWb6WcD/0MlGlP7NPLljpe0V9sh7llXtEq0uuysr729aTkA
+kDLFYg9e6Lc2gOedYQ+HfS0cmyHQLEcTO6KzaH5hQaD4dekCLrZqQjXGuHihbQZo
+2Iw2EhsdrUllaZVTssvG2hPldS7GT996o/5MSn2iH3eHYk0EydF4CAW4T8GY9wBt
+oen/A/9sIlp3z/BGt8aZv1wZoA1/i66/ZDG9m533lCyy6tErxI483NpPu6d68SJ6
+XxTrx3R3likQQN/VRGk9Nl9Drxr1rUb+DBpdzyHDV9WGd/j9EDLgXBADfvopP49c
+IBvTi/r02Y1kcJNfVyosJ7UJvinlw5zah2/KA5LmVRXUZYVKpLRAU2F0aGVlc2gg
+QmFuZGFyYW0gKEFwYWNoZSBEZXJieSBQcm9qZWN0KSA8c2F0aGVlc2hAU291cmNl
+cnkuT3JnPoheBBMRAgAeBQJBLoEKAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJ
+EBDVTSGOg2exMzMAnRQjaWR9f8fXOOYcMO2LK/quSIJQAJ4sRYN0FC9uEbZkYoDA
+jGocCR6MKohGBBMRAgAGBQJBLoUUAAoJEBtId+mxZpKH4B0An0zHYM+QcRwWHDVw
+0P48qeod1+oXAJ0dMmoAfn9TBOXjCIqS+863SlAIFIhGBBMRAgAGBQJBLs2cAAoJ
+EA3wdF2rgh+8jKkAnRMb+bZhUkvJnz6vB3t5IKA4UUgGAJ93bIkG113hEkImTlxT
+xITAqB4gfohGBBMRAgAGBQJBL6sBAAoJEBdC+ruZWGwmBDMAnAjCR9GsHh6qHNzo
+1on/VTSsCE+gAJ9+jszy+eGHAvEHLaRQYSuirrMAUohGBBMRAgAGBQJBL8xEAAoJ
+EBKXrJch6j7NTJwAn3pYi5blwnTw305JgxIudPQEzTmJAJ0f93dVPboI7l5TofVe
+ljQ/xXW58bkBDQRBLoELEAQArXDMv6dCRMEHYPQQO0nznFZa5DcWStqJE109TD7a
+17uhr7hPP3zDsFeKe+MtMeeKOeULSAPd9tKHB1RZvtgxWs36C4iG86MRZcVa6oVa
+PMIctAnah7qim/IBb2a9XeZcOayUs2pqdZSBy3DDYdXj7jVm0LLcrvzNF4D7CVz2
+jV8AAwUD/2xNOv4ShBiAnOU6fQQeqAOI7mjcfda8pKvg69lxZPPLPyUq8MfBtcad
+YPzqhM04IxMXjkxZ9H5a8TCAmR+oApU0zZAmFeh1WfCm9+7f46/lxWM7TA4XOQSq
+2ve3LQd9VKfk0fQDoeUuqx43IEJenZSfORI7/6+D46EFKQunby6+iEkEGBECAAkF
+AkEugQsCGwwACgkQENVNIY6DZ7HxmgCfcwzX6Psnt1raT2ON0BfhQEwl49YAnRLW
+Rb7wNS9cfh8CWIRGhjMgmyj2
+=3zBL
+-----END PGP PUBLIC KEY BLOCK-----
+
+pub 1024D/99586C26 2004-08-14 Jean T. Anderson <jta@bristowhill.com>
+sig 3 99586C26 2004-08-14 Jean T. Anderson <jta@bristowhill.com>
+sig 3 AB821FBC 2004-08-26 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 B1669287 2004-08-26 Katherine Marsden <kmarsden@Sourcery.Org>
+sig 3 AB1B7EE4 2004-08-26 Daniel John Debrunner <djd@debrunners.com>
+sig 3 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sig 3 21EA3ECD 2004-08-27 Mike Matrigali <mikem_app@sbcglobal.net>
+sub 1024g/0A785B8D 2004-08-14
+sig 99586C26 2004-08-14 Jean T. Anderson <jta@bristowhill.com>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.4 (Darwin)
+
+mQGiBEEegw0RBACdLKcnoK0vorrHsI/8ZdkiysSUCsdLrSBn5AyTE/ruSv0E8dMc
+KsBpn6O56YfyacDPdqnEGJk1sPa+0V+u3Nu0bSJZJG1VtVi8WiMfpOplQVjkWJII
+zrvLEIZPCwJkAzt3u5AwatqVfVeO5TQqyyplYbB8yQNUCFJCi9dQgj1gYwCgqAqH
+cwy1OmCGtRpk4TILR4xxRDED/3jnXYZxCzfaddZijAT7IsNGoUK1UoKgmiS+ivri
+31HsRJ4lVBIslu2C/S9QFjLRFhrng98C/aCQ7Y+Wxx/Jsg/zB6/Yhx2Yv9Y1299c
+idWaSgmiusvR5mO0u0n97Ho79VpBuuXXuBmbkGzYlKsjIhHrIO79o8j0x7fVPD3I
+w56KA/4wjwpCa3PDna4wNvhZMxUUZO2k0MFL8mrqpUxqO7ZQYSzY/k6V3a1xjbjL
+8dNjj1KnzVz6ycDhDRAGVHvamLO8rzQ2mh3X4MllNePcsLqDXbonClgacVd7fivY
++Pp5UUJGI6+ZHp319/vcDndX2ofyp0Ah4Z2RVxNu71KF1JiBtLQmSmVhbiBULiBB
+bmRlcnNvbiA8anRhQGJyaXN0b3doaWxsLmNvbT6IXgQTEQIAHgUCQR6DDQIbAwYL
+CQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAXQvq7mVhsJvnIAKCjq8uuJjcZPZsP00Jb
+IAzRpyj9HACfcZu9UTK62QDmT3lFyKkV/YaNNWeIRgQTEQIABgUCQS5g4AAKCRAN
+8HRdq4IfvPAmAJ9ZVUkP1/3wvF3e+My9YkuIO+u0XACeIRL00+mBzm5QVmhcMxhQ
+4tRyeo6IRgQTEQIABgUCQS5pVAAKCRAbSHfpsWaSh626AKC99Ik9mJSvTz21F3we
+cd9s3w8yOACfTQi2NoUtwvQKs7Tu1gqEtnTunRWIRgQTEQIABgUCQS5rwgAKCRAi
+/RLiqxt+5BTKAJ4mstR0ohP48ItKWKGd7aIKMG4l2ACZAUr+0tPpQjmxvADM8Dgu
+wnLkp2+IRgQTEQIABgUCQS9tLQAKCRAQ1U0hjoNnsdyyAJ9T8VxSPj8AU/IVm9rL
+Uifq9WEdfACcDR0NZPAGz6IOhFBdBbjXj7TVgDaIRgQTEQIABgUCQS/C8wAKCRAS
+l6yXIeo+zfOWAJ0caKR7/0yNtaKXFXp0qjeB9Qf7CACdG4/UMb6c9z1qv3gMYbzO
+5FT7+bG5AQ0EQR6DFBAEAK8tLY10PSMqpkYjXM32OwTA5TbjZV5T3osNL0h7PvQK
+Cvs1pSsa/qDhvDHj18KWdyU/tDmLBtxRLRyV4pjPR9txmcuQcQ15whca1Wbi78og
+IZA7O59+1gWzkdEWtVkTrgac0aImdMRGOTxqQaMxfbIOtqd7DrCnd1q1tl4Yc3O/
+AAMFA/96HUAATeRbX5DqVA+k6X7OglZGHCMmdwcqWb10E1tl8dnnZZzTk2kC3csk
+SS4NfjFXaI7jqla1mp8LM1QRLs51MyoiUqtkyemxVhVfLIj+T6L2LCFEVQhesjF2
+gtBzxOR7lwjo9Pjp6ZwxrZg6M2al1ynAvITZv6egM33oRMJoMYhJBBgRAgAJBQJB
+HoMUAhsMAAoJEBdC+ruZWGwmXzAAoKCTDi9b+/wCMuWSDnmeq5H5uEYlAJ9x2C0B
+wkrZTEJZy3Hta6ECTWSNRQ==
+=Pgt+
+-----END PGP PUBLIC KEY BLOCK-----
+pub 1024D/B1669287 2004-08-11 Kathey Marsden <kmarsden@apache.org>
+sig 3 B1669287 2005-10-21 Kathey Marsden <kmarsden@apache.org>
+uid Katherine Marsden <kmarsden@Sourcery.Org>
+sig 3 B1669287 2004-08-11 Kathey Marsden <kmarsden@apache.org>
+sig 3 AB821FBC 2004-08-12 Samuel Andrew McIntyre (Apache Derby Project) <fuzzylogic@nonintuitive.com>
+sig 3 AB1B7EE4 2004-08-13 Daniel John Debrunner <djd@debrunners.com>
+sig 3 99586C26 2004-08-26 Jean T. Anderson <jta@bristowhill.com>
+sig 3 8E8367B1 2004-08-27 Satheesh Bandaram (Apache Derby Project) <satheesh@Sourcery.Org>
+sig 3 21EA3ECD 2004-08-27 Mike Matrigali <mikem_app@sbcglobal.net>
+sub 2048g/8DB2F79B 2004-08-11
+sig B1669287 2004-08-11 Kathey Marsden <kmarsden@apache.org>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.5 (MingW32)
+
+mQGiBEEZvwARBACeNOc5OYdK6KlapdhaXqoUUNUOqBzK3W+hQOUwxxaU1kjZ+oGd
+iL8taaa5CUVtuPyN6mhNd90Mle/6s0bnuu7nIY/GC1N8bCD1d+7ulpAd0RpJd/yv
+EOSbeJKe/Q6jNdLimmZYq0vfhLqvKaTcNnTmJg46UpXnn+46eG5Zo/21ewCgy/CJ
+D1qRc3luwm1OqYVCpgjjRfcD/13mQ4NeXMzpHu4akMqnGIZwes1+YqNTxP9iZZQQ
+9iTIABA0wJgoD6f/axvhzK7kbE/qw7XGVBIuCGEhjRzCggQWdOZ3v5AKATQJ7KTg
+5yFsf5F0pukfUEGDPqLNMPeAooGNx5pTSkwk0oC6o4uQ+l/adhyqIhvs94JmR7hl
+o6f+A/97g28pIA40g8lpkn+UQnKTZUbIVZUqYRaa+8cP1rNftp+OxdcqqZmBXx6A
+EjowNjxEsrv3wzhqz+bL8RAqVuFwVSHbieDusHFmDMpy8oHj7rUw+3kFlQb6qeZQ
+/43hl00IZ33eA73xWJuNC0YBlZpmoJ2X5+GHx9sBH2mptA/Hr7QkS2F0aGV5IE1h
+cnNkZW4gPGttYXJzZGVuQGFwYWNoZS5vcmc+iGIEExECACICGwMHCwkIBwMCAQMV
+AgMDFgIBAh4BAheABQJDWTR/AhkBAAoJEBtId+mxZpKH3B0AoK1DJNlR4hbLtMqQ
+PEQ9cgJa04XiAKCVzt66DTdlvIvVQ6AsxTrSpQuvULQpS2F0aGVyaW5lIE1hcnNk
+ZW4gPGttYXJzZGVuQFNvdXJjZXJ5Lk9yZz6IXwQTEQIAHwUCQRm/AAIbAwcLCQgH
+AwIBAxUCAwMWAgECHgECF4AACgkQG0h36bFmkoeZ4ACfS9gYaTagIa2eYcQzAUEe
+4SqxKXEAn2uO5qeQKeqgLX2YLrbQZHEwj2meiEYEExECAAYFAkEcARcACgkQDfB0
+XauCH7z+8wCfSXb/A4X5ot9fptZovIh5N06wnZkAmwTa5bU8y+8UErPrauUMomYm
+PXyxiEYEExECAAYFAkEc+18ACgkQIv0S4qsbfuRWPQCgjXCwGdtEK+rhr5ogR6dK
+KZ1I63AAn0PN2L7HjmBJmmli3jYgDxtzb0F3iEYEExECAAYFAkEuaEQACgkQF0L6
+u5lYbCbA1ACfduwN8KrqBnGYPufRAWdr9a6Xe/oAnjBTv8Tvov8SD/ZaIMQnD1N0
+pVNriEYEExECAAYFAkEuhsYACgkQENVNIY6DZ7Fa0QCgpe1Q91vlD2IkhcWIiLmd
+j2AFZh0AniL+Djl9NvaGHSb1VZtgntrq7QamiEYEExECAAYFAkEvvSwACgkQEpes
+lyHqPs0anACgmAY38+ajx1iV8UMIIrNTeFxn3lAAn1boZDDVCnouy8j9gwsbS2JE
+OjsHuQINBEEZv1UQCACGNe+0lhLKheq2dcW3i0Sh9Yr+ormiUAH8caQAPL7nWMDl
+w5DaJLmo678tR3aImtDUO1x9RIQNhs/vOHRVDR+5g5X2DwaBElahi6sV2nk6703p
+gL51MpTGunyeM4ge2xsjI8la2i+TXQQYsDCDNmdEWA8f2oYSHsMifxFNY8jvdNGy
+c3SwUWF/THVIwT4O+onrK34/5Uo2CfXBikWEfnVV0mW3xyBZQ/z148JkkuitY6Dh
+adEI3mJBbUnJ4d3yEUq5IWtFdwMqSlqLCuQQWtIWLeDC8kyW7GLhQykMKvNT07jl
+s4BX14GBWZFYNMBk4xgtAlb0mkwXLzAxlnKoTuyXAAURB/49TWfRlJtywcCCdbxR
+JKMnzlqGVWtG+9BvFR5VSqkYIUS40xqZHKCRvtr24RKRFppDxinWivohKGjdzEPk
+UMIU082PPvs2b6FxKAKTUqglWyEwq8j4nM7SDkP4pR5PEIcXFWsvWo1n7iJXQCO+
+M5dzr6vkOAAFib86EwlMw7L47NrTCpeEzXZ+lY1jgNDJUQvNsLf3fFxmEJf+VzqF
+25O/8D49Vyhz0mGNhlt/UI3stTqVRY9nrrmVh2VfSDQMfWetCL3fvYrKFocRZTeS
+oO9Y93N0NhmBnRPDWqeexBYhUJFlIVYp4t7iN9VhzzDHHIp9DAnIWl9o1H4TBI7Q
+jelbiEkEGBECAAkFAkEZv1UCGwwACgkQG0h36bFmkodnGwCgt0Db36ImC7fVtI0d
+j+pbNohCiXgAn11iz+InH93Db4c5TprJm1D/DcJX
+=Y+Qi
+-----END PGP PUBLIC KEY BLOCK-----
+
+pub 1024D/98E21827 2006-02-04
+uid Rick Hillegas <rhillegas@apache.org>
+sig 3 98E21827 2006-02-04 Rick Hillegas <rhillegas@apache.org>
+sub 2048g/EA8075A5 2006-02-04
+sig 98E21827 2006-02-04 Rick Hillegas <rhillegas@apache.org>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.4.1 (MingW32)
+
+mQGiBEPj+4IRBACumYIyghf1QoMOa2mdizbqyjOt31+w1XC/HQc+gUYmjnxdvoJn
+H2614X2bq3gfOtlSVY6k5zBUhcQRIDrfT5JF+idvSvTRAFr6FNRz3cCuX4HSJJmx
+V2OAiCU8RK2fDZ1g/KNpk1BjWLBgnj//0pII0PjUJ9z34Ae8eqzscehtLwCg2ArY
+hfx5CaruWPpd9K2/o2NPZEkEAINy7f7jXVPMP7IW06hNcitAMloKadPKOyJjhET4
+Q0W482RbeJDmow7WhAClRlxmx6dPsmktCtfNTipNDEc95fF1/HnikmKUSbw8Xj62
+fNSVMwt0LXsi45iYJKZ+/DOjxOQTz/VJsmroVkgPxgupx1Klw23zYtFwo2PTlIVP
+MEBKBACreiRPusK5irqPNl5EJB42guH0dF/QXJHa9kbwdlyvyiuKT6xeYhZAo/w5
+RE5/GBkXPNpNJakpIDlLItnZ7KCtLGOTNbI1xEQgFHMlJ0K79yErOJigFR2j9mlx
+FXIqYriJo4E/WVQqcSL1KzZRw487RPu8W/fT7g1tFZcBD/zQGLQkUmljayBIaWxs
+ZWdhcyA8cmhpbGxlZ2FzQGFwYWNoZS5vcmc+iF4EExECAB4FAkPj+4ICGwMGCwkI
+BwMCAxUCAwMWAgECHgECF4AACgkQPYsA4ZjiGCcJDgCfTZG9L5LFg0lNejBsuiiI
++QV/WgcAoKiRANWvc/2swRxBFboG/nchx37ruQINBEPj+4kQCADkbn9EKZlYTmyO
+Uk4Ygwn5+fkAcm4CrUU+u1nBcDNSZLO17msIvi4ZKqjRps9eAyPTad1gNPKWNbLU
+/o6nPTwhTjoBl4p+7gPw1xhdxQTvrQ1jOqNcQTcXCmAad/Ei+0NVwYbTrO/CdOjv
+t5B2Lt5Dgx4huaCsZns3J4+YY+TrRm7eowS/7cINfYnH731evQ92S+umuwoYQhpf
+bJq4oWz2aL+Q500hO5xJmh1mOSaRHjjC6pHnHxbij3BMonW9TlasQU/66lMHj/Gw
+o9MFVj0gLQkmYq6sxiKDzHj31Sv2b2tNCFCsc1KN6WvvMWUB45pXKoSIC34+lco4
+jUrtDbsrAAMFCADTpSfqhkmkHhpPrGVarjOsYjEne+FlLuxmN8iDTKI8cvye4M5j
+zX2xBNtBGQA8E8X6iRFlGjZufWxR52uuTpgVO6dvriepsl2oJ8kMSzQbpnYD3pMi
+7v0zzSroiXRyFmVWnUKhgTezPjt0GLoHwOXubdQ6AQgsbL5gaTzIb6OV2BnpzrA3
+CGo8w0qtbFYLyPoM/PrA280kx8AeR0ibzcCk5ziEozw6NEs5+iVvVQSl118hP0lT
+Uj0AU9ZukV6UsirLMZl4jnUZ1Slg3E60ovU0k/wEFm1FF2tb2UDgxrjzx+AO4Dha
+Ac7oyFyJnYL/MbUU7gHQqI7+K2Eb2taGEWDFiEkEGBECAAkFAkPj+4kCGwwACgkQ
+PYsA4ZjiGCfVYQCfc06KjdCY9oA8q4wtoBYRFcAudCAAnixZ+3wVIT9bPo+etL8S
+daUsGX+B
+=gOT2
+-----END PGP PUBLIC KEY BLOCK-----
+pub 1024D/0C8EBFBE 2005-12-12 David Van Couvering (My Apache Key) <davidvc@apache.org>
+sig 3 0C8EBFBE 2005-12-12 David Van Couvering (My Apache Key) <davidvc@apache.org>
+sub 1024g/62754CD7 2005-12-12
+sig 0C8EBFBE 2005-12-12 David Van Couvering (My Apache Key) <davidvc@apache.org>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.2 (MingW32)
+
+mQGiBEOdIO0RBACSHDWWM/y4VhD7qjdvQhM/pV4fHhrswnUig1uYfjTSzPKEdOsq
+LP33HmGf/hc9ccRRFSDRknA26bzHYdkQj3av50GOG5Uk7GebuyUU8doa/5ONj9Ij
+newGwNGks9SXesCvoA1YnUQjm/bTHIyE2C7NlrVKU5f+EIBeBwBu312mCwCgiLN9
+E7OKISoIOctEsJWfTZsxtSkD/i8lZcnkJEbXArU0Ucnc5xqOppKzl/J5HKlcFYml
+mpLfkRKQH1HAg296qFLg3tQH/BalYpsvBT5ns/yQlmwALi97ArjG8liGYyNT+E5X
+G5IwphSfaEd4FqzyXIeoOS0nfQxIACh1hbCfpvXl56hAkl2Aa7NSROJw6JNquvaH
+LH5gA/9i9sWdDXA2OiUfKNQGfFQaVbKP7i2w7PVRBAXiQANv6TdIaMYFcPMb/ayH
+k9alXWyi5wVh+zazOI+/b/g/9KTyZdfcdrMKs7yBF1EOdcTKeo36yfuBLzpyCYSn
+u/ZbTJZrbO0pg5X2BSIBG3jzCZjjtVJUg3V4DHRi/T7snTuiJLQ4RGF2aWQgVmFu
+IENvdXZlcmluZyAoTXkgQXBhY2hlIEtleSkgPGRhdmlkdmNAYXBhY2hlLm9yZz6I
+WwQTEQIAGwUCQ50g7QYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRCLtlN0DI6/vrZ2
+AJ9L5L/91YUq0lBySCUyP+4zXEFvUgCfTIwq6aRSpVT4RoZuEglWXGkoDGy5AQ0E
+Q50g7hAEAIOcMG05qk+5B2HpXrffhM1nHMjzamFV9QLdz4UI4pVkbcgZP0H+4aeV
+GzPaSK/IzjItKb94XqXIL9g1J3FSpnH6behCZtrtmlDWgcc+um/qPOiWg5SBGjmT
+vnCi/kzByBPzqc/O+qhX7tr6PRxI91IKj499+vzlIp0TvPtc6x0HAAMFA/4oted7
+UIGd2A/oGqfg0lqKuROpWQo4Xx1b/IxJIstNO7g8bUeteBDctXErqwdMT9flNw0o
+wxLABKBlaUHfhaC0xGUKJHMlQ8BIWNWkf/VVYy56SolTh6mao+p/NY03z1A2x3Bh
+pXL0ecCJQ+6mTztaeARgDa1SBWuBwSunabUdVIhGBBgRAgAGBQJDnSDuAAoJEIu2
+U3QMjr++rwUAn34Z5ghQZOpDmF8R/8SPMzlRx2yeAKCAnSxY7R5og/tVa29t7ih+
+tDrSVQ==
+=Rbhm
+-----END PGP PUBLIC KEY BLOCK-----
+pub 1024D/990ED4AA 2006-08-16
+uid Knut Anders Hatlen <kahatlen@apache.org>
+sig 3 990ED4AA 2006-08-16 Knut Anders Hatlen <kahatlen@apache.org>
+sub 2048g/165BD1F7 2006-08-16
+sig 990ED4AA 2006-08-16 Knut Anders Hatlen <kahatlen@apache.org>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.4.5 (FreeBSD)
+
+mQGiBETiuQURBADTblCPi5gXDXhT88Yp2YPAmeb5FMFyV1oPZfwsq/1cj8+BfqpY
+ZaqUcqw0l0aCHiCFOagqlvLoy9A4NAeRBgcx3Q1sfWEqSbvqy3jYS9zUpS2Fx9fb
+X6zrtLMNswK9pzkUgtdxBvBKMcjbSMMLfScAuHTnTFP/mXZapXGW1IPJqwCgmXBg
+eFsYAjeAWxIUHyv7hYeZ7wMEAMX714eZUVR+jyjcw6iDMJbhFaIVm5WVT/+Jf5Eh
+mf4IAYRkSCANX8s4jZfukUs6kptGRllwqstF7maFDRqdOGkN0unhUgvv0pTEOtXn
+0FtV2wR2dP0N0yxhOYuedishTi9OOo8llDWRUaaazKwjYIXQJIep5ViN86rvrbCE
+Y9TQA/wJKF5qoos/FPSECly18wzuCcgnTWHw3bYjQbUlOJ8HeqYS5vQI5hUHuUXA
+4hjVSMoTDbfVVhDRDML3ACd+qgIsNKVRi0mWRFAz4ZBTmrJiWqdVX36xAjeedXkD
+1vk/VMWVjpJms3EDDFo+hOWm24diefWtnDCvf0WY9s4N96ZZrLQoS251dCBBbmRl
+cnMgSGF0bGVuIDxrYWhhdGxlbkBhcGFjaGUub3JnPohgBBMRAgAgBQJE4rkFAhsD
+BgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ4eHysJkO1KqNCgCfehVc27Q+dhwb
+IrtoTTvJDrKdD1oAnReLlobKcAIH6ToqWhc1KPyQrxfSuQINBETiuQkQCACP/g0D
+cjg+SPXowQqRKcIla0MUINusXCHxKcNRqRpcCEiSPNcBko1PpGjiVcIfP1urAkVV
+c8/Vey4l3LI00kapGOsXK//v/BJksnzWNNY5Q3lVEVwI57hVhMPMihn+4aE93mh2
+p/k2f2DldDPOEBEanrJiCmGtTWo7cX4sTPYwJwNwbUuApp+uI0QDs6dZSElA3pdj
+u+6JwZYDiBnrwv2YWBXgIeSQ3PhKjKS1MoybYj47b+jp9dBL1tvf0hBts2CaVBy3
+V/M98L32pm/OZrv+nm9BPg7utT+wsX+9XT5l6F7jjteYU4G8GXgFFyKldE+ZLAro
+BRAgVtPJ7FXmwJ/DAAMFB/48r4qpbDp4aaBVyOgSDuX5nDGIF+oXNqP76F0Wz5+1
+D8hiE7fweRLD9vr3o7u278GUI/IFQAZLulcw5khboScNv9eoli0jMnZPQxDgM4BD
+kmZVa+JNHUaALf41N5cGB6yJ+1G3KSY24VKd8aqBoiedLCsDibe/unq2CWjr4xZW
+A73nWzZ7RsrX07xH7hfUulRk2p5heJwgcyyfsazm38ugqP1jL+XW/6jm6He5MMt6
+wc2MWUkoFCL+pMh7RK6KTT1YBsrX6e/MDJznXaEyIj3+2pTsyzqlFxPG9loDsSVd
+/dig5bU9lRajodg+yupgpm9yNEStTody40UOxw96ZPXwiEkEGBECAAkFAkTiuQkC
+GwwACgkQ4eHysJkO1KqpMwCcCZj3gJnnOOEJwHPP9E8dPUndDfUAnil3o1vuzEA/
+VxFd+IhqD85ykUrt
+=Nxxr
+-----END PGP PUBLIC KEY BLOCK-----
+pub 1024D/88D83722 2006-08-16
+uid Andreas Korneliussen <andreas.korneliussen@broadpark.no>
+sig 3 88D83722 2006-08-16 Andreas Korneliussen <andreas.korneliussen@broadpark.no>
+uid Andreas Korneliussen <andreask@apache.org>
+sig 3 88D83722 2006-08-16 Andreas Korneliussen <andreas.korneliussen@broadpark.no>
+sub 2048g/F920EBC6 2006-08-16
+sig 88D83722 2006-08-16 Andreas Korneliussen <andreas.korneliussen@broadpark.no>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.4.4 (SunOS)
+
+mQGiBETi5coRBACF0SAt1faQn4+TPcQMwXtyl61X5vgKOxLDZjQ85ZVL/AWyaj54
+UnoV+5e8MqIlsp+829z5iMT2kPGdcWQWM+Ormj5tniFFg0GNw7LL9+R4mnfzFsBQ
+/ourirBUuy+r+5apRO0trs2naSBjLgGBtSxLy5U3rGzuZYh7NVSUqoZI0wCg534n
+DkZoiN7r44Cv+aGsdpODAQ8D/ijqaIXO7nn5jGl4bWGP8c7bOjOsEl+ahQkP/tgt
+YkPjz1BxAbswir2j6jIyfRDr3NtWyfuF50MwFwJkRSWh9iriZLbbH2QzG6y2bhdE
+ATVSoqK4EpeaU0K9ycEUIKo0+UpeM+97oVaFRzcGp4D2bJVJfhD7XhPwGZ1ZBC30
+FAy9A/9Mu/tNqO7lJSCc5Vb/xm75yja+DC61njaJTMRvwaU0wJQzi3FVHl1JhRYy
+CI2cXb8gtQXqwYOAInVCv+HFP29Vif6EoDQ8p8kV4uZeThtPAHaAONbgAhw8U5vF
+rm8NwkrJm9I85q35Oy2kbuPPMfn3WseWgRwYiZ2RMDZRUQmKsrQqQW5kcmVhcyBL
+b3JuZWxpdXNzZW4gPGFuZHJlYXNrQGFwYWNoZS5vcmc+iGAEExECACAFAkTi5coC
+GwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDfoOnJiNg3IhE0AJ9KEg+lKnq9
+tOs0YLQjRkyOK+h4oQCgyDR2ZjZdT6zUnI5Bo0w+bzw1BDq0OEFuZHJlYXMgS29y
+bmVsaXVzc2VuIDxhbmRyZWFzLmtvcm5lbGl1c3NlbkBicm9hZHBhcmsubm8+iGAE
+ExECACAFAkTi5jkCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDfoOnJiNg3
+ItmnAKCCw2HTX/VUGsc5tcmuewOR1LVhcACgjQKjdZ56vfu5hTG62MJB2PWVPD65
+Ag0EROLl4xAIAIFHg90B+QrOH4rCFul12kyI/CPOFdcIzTtW4fQOuUlHave/b3ez
+7sGbobjj3nexyvGIG9K4rKiXbticfkU6FfmWGFWV+6AbRM8i+qYdSnAck9qBO8+4
+TRf/qwhEh3i3YLcgrMdyRS9ifWDHSImqfllawP4dBdyhLu2g7Pz7Xs1+uaRjzi7+
+2wJ6nS7BCYY+fmt5OM44So0R/tO2r793LULw3TgxkbO9AkOoIdOg71tuCT3VFyLq
+jGxfrnZgfRNcnPLnUyRNAw2VoWVe1IGGlNG5el1w83tr4ugAKsFV+cHqW4bWdHGE
+b1dWVUv033evlrfaau+TEu/cp2LHVE1zULcAAwUH/07+M4cOCnT6l3xNuS93/mSx
+areXSwZ33t/LahT6J9fAwhtac6MDTkeTaDxcDuSTKkCdNlyPetR8jFmfZTu7oj+k
+PwqlSfQUHi1WHmk3Fs/9HuF+71P1C4K2789MSLnFsu94KQ3hTqbJRZbayDwoU4wZ
+HSQfMlnh22INf47iD3enORbLf2Lg3PWHVc3Xs/ag4hPQwDahKEvX7TZsHbt3LNud
+hMcdcTVEAX1kP5PL/zCxb3/YMM3l5m0zG35d+bW89P4D+3SWt4Oc09vLaGmMc9Zx
+hnBxiZzNcaNaoLPKN9wWu1q/y2J44zZDIv9gfW2vyJA2rinPRncN/9flHYXzo4iI
+SQQYEQIACQUCROLl4wIbDAAKCRDfoOnJiNg3In9mAJwOJiJ+8s4BSFd+u9JzW2wg
+1D3dCgCgyDPdCE3+3sl/C/VvoZ0PdhnuYAE=
+=+RoX
+-----END PGP PUBLIC KEY BLOCK-----
+pub 1024D/5355D01C 2007-03-25
+uid Dag H. Wanvik (Derby committer) <dag@apache.org>
+sig 35C100F0 2007-03-26 Bernt M. Johnsen <bernt@apache.org>
+sig 3 5355D01C 2007-03-26 Dag H. Wanvik (Derby committer) <dag@apache.org>
+sig 990ED4AA 2007-03-27 Knut Anders Hatlen <kahatlen@apache.org>
+sig 3 5355D01C 2007-03-25 Dag H. Wanvik (Derby committer) <dag@apache.org>
+sig 3 990ED4AA 2007-04-11 Knut Anders Hatlen <kahatlen@apache.org>
+uid Dag H. Wanvik <dag@wanvik.com>
+sig 35C100F0 2007-03-26 Bernt M. Johnsen <bernt@apache.org>
+sig 3 5355D01C 2007-03-25 Dag H. Wanvik (Derby committer) <dag@apache.org>
+sig 35C100F0 2007-03-26 Bernt M. Johnsen <bernt@apache.org>
+sig 990ED4AA 2007-03-27 Knut Anders Hatlen <kahatlen@apache.org>
+sig 990ED4AA 2007-03-27 Knut Anders Hatlen <kahatlen@apache.org>
+sig 3 990ED4AA 2007-04-11 Knut Anders Hatlen <kahatlen@apache.org>
+uid Dag H. Wanvik <dag.wanvik@sun.com>
+sig 3 5355D01C 2007-03-26 Dag H. Wanvik (Derby committer) <dag@apache.org>
+sub 2048g/6F3578EF 2007-03-25
+sig 5355D01C 2007-03-25 Dag H. Wanvik (Derby committer) <dag@apache.org>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.4.6 (SunOS)
+
+mQGiBEYFzRARBADTpSSXSlij41eYml26ejzK7+9YqX+Res3kLRcAwYp3S+pOW4no
+1exOp+TfeKBUtnHTK2jJUoKCEHXygze7cT5p1Xh1baNj/QJFYYH0LrD3hmkCiINQ
+9+sS0tNx6MsM3//wPlXgxeUMyJFIfV0nLIU+Qs0G5ZkJmqfuj/Ipr6fg7wCgsQ9h
+DtlSqQgDC69Sesan00BIiVMD/iuY7nmtj3zO5O9aEwnko+STmsb1sI86QDK8jVVw
+UpelfIntyXRHaAXrsjwCTc6fDyuWEhlaeD8bFHRF3MDO220ABFwbAruwWn7nJaSZ
+gzV2+8Bnt0aQHjeofSYF/pfecsiVeKjq3gIBs1OFuWDofAdu1+myRmesGdc4ofsm
+0de/A/0a8Ko5JyI8fhPD/f+OE/Wgd2gGBVlzSKYr3hqECoRavhYPTc/qMRLj6v1T
+Z96gGUlTmkp2G4vcylysMELii5P8B34ske47nAJ/ViTw+NHOQXhFJwhVz96jjWfB
+tkDOz37834NocTXkXE4Kn61NQik/qtulzbMUvwlPRHYDOwwMZLQwRGFnIEguIFdh
+bnZpayAoRGVyYnkgY29tbWl0dGVyKSA8ZGFnQGFwYWNoZS5vcmc+iEYEEBECAAYF
+AkYHqcIACgkQlFBD9TXBAPA4rQCfbm3WaHDkA8kLkOea2KoRNG9SFioAoMZIQjEr
+umWzY7DUToAaQCQy79G8iGMEExECACMCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
+gAUCRge5FwIZAQAKCRDhZNinU1XQHImEAJ9oC/yw8cXpP29fpMgJB5uwpJDdVQCf
+UZm12DcnXttCY7TPUTU3xwjU5KKIRgQQEQIABgUCRgj2mwAKCRDh4fKwmQ7UqjT9
+AJ9WuibI/uQthSc5kcyElLgHFRgTuwCeNKVlaCeFPuERBA4zejyzVUb8/zeIYAQT
+EQIAIAUCRgXcQQIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEOFk2KdTVdAc
+hh8Anj1zirsVGqjErpeTnubWj+v0Gb1xAJ4heVo90/egMZ3ScdaZF4cUkDuOBohG
+BBMRAgAGBQJGHIOHAAoJEOHh8rCZDtSqVPQAnAmj4UFUjl2KGEKoAyvH2d+RCLMn
+AJ0bEXc0GjFXeQQmguOQAkZJPTdsx7QeRGFnIEguIFdhbnZpayA8ZGFnQHdhbnZp
+ay5jb20+iEYEEBECAAYFAkYHqcUACgkQlFBD9TXBAPCEngCbBs9buDSKE7jVFvw8
+UNygWEeCr+4AoLucnHd0PHdQLahU5ScZeAHxBDHkiGAEExECACAFAkYFzRACGwMG
+CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDhZNinU1XQHNpZAKCwiAk6xdYj37RP
+EThH9PeEfhgRfwCgigvu0ZcjO6KzHM+J9NgI8rJWS7SIRgQQEQIABgUCRgepwgAK
+CRCUUEP1NcEA8DitAJ9ubdZocOQDyQuQ55rYqhE0b1IWKgCgxkhCMSu6ZbNjsNRO
+gBpAJDLv0byIRgQQEQIABgUCRgj2mwAKCRDh4fKwmQ7UqjT9AJ9WuibI/uQthSc5
+kcyElLgHFRgTuwCeNKVlaCeFPuERBA4zejyzVUb8/zeIRgQQEQIABgUCRgj2pgAK
+CRDh4fKwmQ7UqunXAJ95+ITMHXM7LegaaZoMD+qSzh8dPQCeLAQvxf6MFqGCmGor
+/Z7PmZxkkkeIRgQTEQIABgUCRhyDjwAKCRDh4fKwmQ7Uqt3pAKCNV70NyLS1K+ay
+SSH5Rx2Dqb+HFgCbBzASo3Dby/h9c0hNQoOCDHM6O620IkRhZyBILiBXYW52aWsg
+PGRhZy53YW52aWtAc3VuLmNvbT6IYAQTEQIAIAUCRge4WwIbAwYLCQgHAwIEFQII
+AwQWAgMBAh4BAheAAAoJEOFk2KdTVdAcbjgAoJoInSvth3ErBRUAnD0MR0JQ8wHt
+AJwLgZu4iypoPaD1wD9ImetiEGIJ8LkCDQRGBc0rEAgAxFBiVzoJmLsJ9A4RXdtX
+xo8DK8sHWct0BzedwjinrAAPIjZeWAxGoDw2HfWk2uK3K0jw07ACwHI+kKTpcvud
+znFWfSrZIxtWyVSazEoeDuZ1Mvf61pYcKeAISE9IX2nj6tpQ3W7XJjXgk/NycfWU
+2JQxJ7YLoihgNtVQ3CWbMFhLSVNwFjKdxqpqqQBlKLVnkQclOX91jweUm2ZJ0eCh
+YfNV7OpW1LMla3Xq6eXilHCNAmbMAlmxBWZDzsSjOPbBLhJW+ZQBUsGBO3f/OmBI
+Wjk7ZmHeldx/roYHw8TgPBBHApq2xmt/VEv1FVYhABlOaQQEB7TnTf7tEpsTQfvr
+owADBQf/Qae1hCqsDw1eh9EOaUvxheN25fKBLcmuURfThNySb2ZHsVwOAuwqLvw7
+N3hVY0/ZLvCxEoDDXVQJMyJD3a9/rxtSikJapVk7uwCXTw1ev5Q9TzcpfaCie5BC
+1JDtMS7mykj8A4wFTFG0KuYOdj+YIemhsETIkyo3obUC1NByaiy81RkAPBxhKV8X
+B95YBGIFBJ60NAFcv35qgjG7bLyjlulFhDpMo9zwaHYXLskjWu1bBL6zMMYP/nMd
+25JwQOdnfmMlWQm7pPnLDivXiwDFriG7sheeWPADBsxyQeY7gRnuvyxwlyjhk0Hj
+Uo/UFhBxZRV2WWCVwfua27jtgv7wvYhJBBgRAgAJBQJGBc0rAhsMAAoJEOFk2KdT
+VdAcSQsAn25pw03yrMuhIhoY7SKio1YYgTqpAKCA47/9pu4cpNAxyfQvIMcrOLaf
+sQ==
+=GBQb
+-----END PGP PUBLIC KEY BLOCK-----
+
+pub 1024D/37AA956A 2007-06-25
+uid Myrna van Lunteren <m.v.lunteren@gmail.com>
+sig 3 37AA956A 2007-06-25 Myrna van Lunteren <m.v.lunteren@gmail.com>
+sub 2048g/6BF93B02 2007-06-25
+sig 37AA956A 2007-06-25 Myrna van Lunteren <m.v.lunteren@gmail.com>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.4.5 (MingW32)
+
+mQGiBEaAF40RBADMSMjU8Um9vy/XwrdHnX7038R6sfTVxmXSasVNunskwByJwZz4
+Q6/q6dD2FjhTY5tDTt6wmCJls7E0wTD5ixaz5k4L3efNkol3jQKwokCPzFJdXcYe
+pWZpHszlCekn0Hpdsl3VlvJdxu3pE+oowYauVFPpCNBpLNxzC1q9EVo8twCg/Twg
+DmZEf6DjawmHSMmhaODLVs8D/0k5FTIrlFTBWebpdfFQ5yzcdDQ1QY4EZFHbJkFC
+zVTrtmO9SuXFcoZRgf923QVaQ4oRiyjK9IQhnWNCwS6y/LEWAYqF8xJB2UeNlZtq
+d3CGQUPNB9fnkybJZxv3tnTFLq+qhHoxKz5dwa0SOe98nU8QcGigt5cYeY2aqZIr
+pWfgA/9YPcnHpedhz7LMn9bN7oRHOMw7+FK16cmw1fs8tHBLlFqbQlIA+GZZFDx9
+rNWYJgKrjY/PdKVNOMv1rxiYV9SPDTuREIop1a75ixlyB6h3yVGnrSo9xDmOBw/t
+qKM0Hd5G7E6HyRuZ18pCmuXHxY/+T6UOHxwhJd22RILENLe+1rQrTXlybmEgdmFu
+IEx1bnRlcmVuIDxtLnYubHVudGVyZW5AZ21haWwuY29tPohgBBMRAgAgBQJGgBeN
+AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQDhP3WjeqlWqxtgCfbQcTr8vB
+ZKOKYg9oAAKsT1MlgT8AnR7d0E15Z/2u+BizR1eqhECPAOkGiEYEEBECAAYFAkaC
+5n8ACgkQDfB0XauCH7wdmgCeK0gTkRd8o9XlkySuEy/toa/DnY8AniaMmYOe/VD+
+g7RGlTejIFTl9pIbuQINBEaAF60QCACbIvSXHEW+LY3o/ty85FIpBLNtw0FLRzvp
+nZZtMmdcS2uzOQuvQKYqMCHNh8+CyiX0JKrZ9kvd8brufVcXwi/Fh6TmSJhyRuFn
+m30QwfkH27PFvMPZsX23GLYuQ2xUneJYPJ1odY+eAWizGzo67uo0ux3wff9A6ExW
+95wC5STf0IDLO2NB0qh0r4wQ+fXi0u0+IwwWCoBvK9bve+1zuAMCRH54Z4Xi1SpC
+wHXoMq3f3Fwyu2iUPHksaUu+EYJ1677f9k82fn+AXpuvukHBCH/weZNSf4zChIBR
+A7dXGAIA7k9pxS4AE8KNscLSnbB/RIMc4DT4rJy1Sf0l6q0NWCqjAAMFB/9m1lNE
+e/DT2RfCU4tbX9I2ckNNUcfxSQoTQ/cnP+xmypE9I/o4ARu9MWMZ7W7ABg6A2kFr
+y0wBL4DuLq3hItKkxrHyX8HB2CHXcsPRQJNBt7nR7DFyym1Be0J8/+YfPcY4vvAY
+y404BabGX/APRQZl1TeI0iTkM6JlbbRjaTZ1j+HCbJwvzusx9Vcxn+QYeSoCXrgg
+bv/8nbMLyUSiDlgzrdJHa3jzhwTYWj150hgX+nrsr73EbVhyRjoytjuyFYEQvQgn
+ItIGSv98fnVrdKlQ8TPOgr4pBjshrSxmXtaxx7YpgWjrg3ggVMdonwurnnjP0mZp
+vnrx+LkMkbXT+6w/iEkEGBECAAkFAkaAF60CGwwACgkQDhP3WjeqlWqtuwCfYxyE
+KvRlezcoy99271lMnOsO+NgAoIp9sbQaf1Jo8tmQbFNnHWMlZ/Zk
+=8Ji1
+-----END PGP PUBLIC KEY BLOCK-----
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/LICENSE b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/LICENSE
new file mode 100644
index 0000000..d645695
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/LICENSE
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/NOTICE b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/NOTICE
new file mode 100644
index 0000000..563d7af
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/NOTICE
@@ -0,0 +1,31 @@
+=========================================================================
+== NOTICE file corresponding to section 4(d) of the Apache License, ==
+== Version 2.0, in this case for the Apache Derby distribution. ==
+=========================================================================
+
+Apache Derby
+Copyright 2004-2007 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
+"Software Grant and Corporate Contribution License Agreement",
+informally known as the "Derby CLA".
+The following copyright notice(s) were affixed to portions of the code
+with which this file is now or was at one time distributed
+and are placed here unaltered.
+
+(C) Copyright 1997,2004 International Business Machines Corporation. All rights reserved.
+
+(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
+International Business Machines Corporation in accordance with the NIST
+Software Acknowledgment and Redistribution document at
+http://www.itl.nist.gov/div897/ctg/sql_form.htm
+
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/RELEASE-NOTES.html b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/RELEASE-NOTES.html
new file mode 100644
index 0000000..fc3ee58
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/RELEASE-NOTES.html
@@ -0,0 +1,4115 @@
+<html>
+<title>Release Notes for Derby 10.3.1.4</title>
+<body>
+<h1>
+<a name="Release Notes for Derby 10.3.1.4"></a>Release Notes for Derby 10.3.1.4</h1>
+<blockquote>
+<p>These notes describe the difference between Derby release 10.3.1.4 and the preceding release 10.2.2.0.</p>
+</blockquote>
+<ul>
+<li>
+<a href="#Overview">Overview</a>
+</li>
+<li>
+<a href="#New Features">New Features</a>
+</li>
+<li>
+<a href="#CHANGES">CHANGES</a>
+</li>
+<li>
+<a href="#Issues">Issues</a>
+</li>
+<li>
+<a href="#Open Bugs">Open Bugs</a>
+</li>
+<li>
+<a href="#Build Environment">Build Environment</a>
+</li>
+</ul>
+<h2>
+<a name="Overview"></a>Overview</h2>
+<blockquote>
+
+
+<p>
+Derby is a pure Java relational database engine using standard SQL and
+JDBC as its APIs.
+</p>
+
+
+<p>
+Derby functionality includes:
+</p>
+
+
+<ul>
+
+<li>Embedded engine with JDBC drivers</li>
+
+<li>Network Server</li>
+
+<li>Network client JDBC drivers</li>
+
+<li>Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)</li>
+
+</ul>
+
+<p>
+Derby 10.3.1.4 runs on the following platforms:
+</p>
+
+<ul>
+<li><b>JDK 1.4 and Java 5</b> - Here Derby supports the JDBC 3.0 interface.</li>
+<li><b>Java 6</b> - Here Derby supports the JDBC 4.0 interface.</li>
+<li><b>CDC/Foundation 1.1</b> - Here Derby supports the JSR 169 interface.</li>
+</ul>
+
+</blockquote>
+<h2>
+<a name="New Features"></a>New Features</h2>
+<blockquote>
+
+
+<p>
+This is a minor release. The following table lists new features that were added and notable improvements that were made:
+</p>
+
+
+</blockquote>
+
+<ul>
+<table border="2">
+<tr>
+<td><b>Feature</b></td><td><b>Description</b></td><td><b>Issue Id(s)</b></td>
+</tr>
+<tr>
+<td>DBA Powers</td><td>Control who can shutdown, encrypt and upgrade databases.</td><td>Master JIRA: <a href="http://issues.apache.org/jira/browse/DERBY-2264">DERBY-2264</a></td>
+</tr>
+<tr>
+<td> Secure Server </td><td> Make the Network Server secure by default. </td><td> Master JIRA: <a href="https://issues.apache.org/jira/browse/DERBY-2196">DERBY-2196</a> </td>
+</tr>
+<tr>
+<td> Language Based Ordering </td><td> Add built in language based ordering and like processing to Derby. </td><td> Master JIRA: <a href="https://issues.apache.org/jira/browse/DERBY-1478">DERBY-1478</a> </td>
+</tr>
+<tr>
+<td> Alter Table </td><td> You can now DROP or RENAME a column. Together with a number of enhancements in 10.2, this means that most dynamic schema modifications are now possible </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-396">DERBY-396</a> <a href="https://issues.apache.org/jira/browse/DERBY-1489">DERBY-1489</a> <a href="https://issues.apache.org/jira/browse/DERBY-1490">DERBY-1490</a> <a href="https://issues.apache.org/jira/browse/DERBY-1926">DERBY-1926</a> <a href="https://issues.apache.org/jira/browse/DERBY-1909">DERBY-1909</a> <a href="https://issues.apache.org/jira/browse/DERBY-2042">DERBY-2042</a></td>
+</tr>
+<tr>
+<td> SSL/TLS </td><td> Implement SSL/TLS communication between client and server </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-2108">DERBY-2108</a> <a href="https://issues.apache.org/jira/browse/DERBY-2356">DERBY-2356</a> <a href="https://issues.apache.org/jira/browse/DERBY-2272">DERBY-2272</a> <a href="https://issues.apache.org/jira/browse/DERBY-2273">DERBY-2273</a> </td>
+</tr>
+<tr>
+<td> Blob/Clob API </td><td> Support all JDBC API methods for Blob/Clob, both for embedded driver and client driver </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-1341 ">DERBY-1341 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-1285">DERBY-1285 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-1286">DERBY-1286 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-2443">DERBY-2443 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-2444">DERBY-2444 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-2730">DERBY-2730 </a> </td>
+</tr>
+<tr>
+<td> Client Side Tracing </td><td> Provide a way to enable client tracing without changing the application </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-1275">DERBY-1275</a> </td>
+</tr>
+<tr>
+<td> Import/Export of Blob/Clob</td><td> Add support for import/export of tables with clob, blob and other binary type columns</td><td> <a href="https://issues.apache.org/jira/browse/DERBY-378">DERBY-378</a> </td>
+</tr>
+<tr>
+<td> JDBC methods for autogenerated keys </td><td> Implement JDBC methods for autogenerated keys for Embedded </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-2631">DERBY-2631</a> </td>
+</tr>
+<tr>
+<td> CREATE TABLE AS <subquery> WITH NO DATA </td><td> Enable Create of a new empty table based upon a sub query </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-64">DERBY-64</a></td>
+</tr>
+<tr>
+<td> XATransaction timeout </td><td> Support for XAResource.setTransactionTimeout</td><td>Master JIRA: <a href="https://issues.apache.org/jira/browse/DERBY-2432">DERBY-2432</a></td>
+</tr>
+<tr>
+<td>
+SYSCS_UTIL.SYSCS_SET_USER_ACCESS</br>
+SYSCS_UTIL.SYSCS_GET_USER_ACCESS</br>
+</td><td>
+Add a system procedure to set a user's connection level authorization.
+</td><td>
+<a href="http://issues.apache.org/jira/browse/DERBY-2735">DERBY-2735</a>
+</td>
+</tr>
+<tr>
+<td>SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE</td><td>Create a procedure to empty the statement cache exposing the existing functionality.</td><td><a href="http://issues.apache.org/jira/browse/DERBY-2772">DERBY-2772</a></td>
+</tr>
+<tr>
+<td>support for diagnostic vti tables that take parameters</td><td>Implement support for diagnostic vti tables that take parameterss.</td><td><a href="http://issues.apache.org/jira/browse/DERBY-2152">DERBY-2152</a></td>
+</tr>
+<tr>
+<td>FOR EACH/MODE DB2SQL in CREATE TRIGGER optional</td><td>Make FOR EACH clause and MODE DB2SQL phrase in CREATE TRIGGER statement optional.</td><td><a href="http://issues.apache.org/jira/browse/DERBY-1953">DERBY-1953</a></td>
+</tr>
+<tr>
+<td>ANSI TRIM</td><td>Add ANSI TRIM implementation</td><td><a href="http://issues.apache.org/jira/browse/DERBY-1623">DERBY-1623</a></td>
+</tr>
+<tr>
+<td> Performance </td><td> Reduce CPU usage in embedded Derby. Main areas being worked on are: Lock manager and latching, reduced use of synchronized data structures, optimize use of bit sets.</td><td> <a href="https://issues.apache.org/jira/browse/DERBY-1704">DERBY-1704</a> <a href="https://issues.apache.org/jira/browse/DERBY-2107">DERBY-2107</a> <a href="https://issues.apache.org/jira/browse/DERBY-2149">DERBY-2149</a> <a href="https://issues.apache.org/jira/browse/DERBY-2150">DERBY-2150</a> <a href="https://issues.apache.org/jira/browse/DERBY-2191">DERBY-2191</a> <a href="https://issues.apache.org/jira/browse/DERBY-2226">DERBY-2226</a> </td>
+</tr>
+<tr>
+<td> Performance </td><td> Improve Derby's treatment of IN-lists to allow the optimizer to consider using indexes when appropriate. </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-47">DERBY-47</a></td>
+</tr>
+<tr>
+<td> Testing </td><td> Switch testing to be pure JUnit based. </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-1952">DERBY-1952</a> & many others </td>
+</tr>
+<tr>
+<td> Memory Usage </td><td> Avoid having to materialize entire LOBs in network client. The client will use locators when requesting operations to be performed on LOBs stored on the server side. </td><td> Master JIRA: <a href="https://issues.apache.org/jira/browse/DERBY-208">DERBY-208</a> </td>
+</tr>
+<tr>
+<td> Platforms </td><td> Minimum JDK support will change to JDK 1.4.2 for J2SE & CDC/Foundation 1.1 for J2ME. (Removes support for JDK 1.3 and J2ME/CDC/Foundation 1.0) </td><td> <a href="http://issues.apache.org/jira/browse/DERBY-1983">DERBY-1983</a> <a href="https://issues.apache.org/jira/browse/DERBY-1985">DERBY-1985</a> <a href="https://issues.apache.org/jira/browse/DERBY-2121">DERBY-2121</a> </td>
+</tr>
+</table>
+</blockquote>
+</ul>
+
+<h2>
+<a name="CHANGES"></a>CHANGES</h2>
+<blockquote>
+<p>The following issues are addressed by Derby release 10.3.1.4. These issues are not addressed in the preceding 10.2.2.0 release. </br>
+This list includes bugs and improvements, and sub-tasks if the super-task is not fixed in 10.3.1.4, but not issues with only test or web content changes.</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-2973">DERBY-2973</a></td><td>With collation TERRITORY_BASED, insert into table after changing type of column causes assert failure and loss of connection</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2966">DERBY-2966</a></td><td>loss of connection with TERRITORY_BASED collation.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2963">DERBY-2963</a></td><td>AccessControlException connection from remote client.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2960">DERBY-2960</a></td><td>Group by substr() on collated database causes ERROR XJ001</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2955">DERBY-2955</a></td><td>ERROR 42ZA2 creating table with check constraint with literal comparison</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2941">DERBY-2941</a></td><td>With 10.2, Closing a resultset after retrieving a large > 32665 bytes value with Network Server does not release locks</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2925">DERBY-2925</a></td><td>Prevent export from overwriting existing files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2882">DERBY-2882</a></td><td>Remove references to JDK 1.2 and 1.3 in the documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2868">DERBY-2868</a></td><td>BUILDING.txt doesn't mention junit.jar in list of jars installed in tools/java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2858">DERBY-2858</a></td><td>Export exceptions swallow useful information</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2849">DERBY-2849</a></td><td>Add a documentation for derby.jdbc.xaTransactionTimeout system/database property</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2837">DERBY-2837</a></td><td>Update docs on STRONG_PASSWORD_SUBSTITUTE_SECURITY/ENCRYPTED_USER_AND_PASSWORD_SECURITY and JCE support</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2809">DERBY-2809</a></td><td>Expressions with a parameter can be assigned the incorrect type</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2806">DERBY-2806</a></td><td>calling getByteLength on org.apache.derby.impl.jdbc.StoreStreamClob makes BinaryStream, fetched before this call, unusable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2794">DERBY-2794</a></td><td>Document ansi trim functionality</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2793">DERBY-2793</a></td><td>Ensure LIKE predicate follows correct rules for determing collation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2789">DERBY-2789</a></td><td>DatabaseMetaData .locatorsUpdateCopy() should return true</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2784">DERBY-2784</a></td><td>With JDBC 4 autoloading DriverManager.getProtocol("jdbc:derby:") throws java.sql.SQLException No suitable driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2753">DERBY-2753</a></td><td>org.apache.derby.impl.drda.DDMWriter might swallow unexpected exceptions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2748">DERBY-2748</a></td><td>TimeSlice and Socket-Timeout bounds checking wrong</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2737">DERBY-2737</a></td><td>Change documentation on permissions needed to include read/write for system property derby.storage.jvmInstanceId </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2694">DERBY-2694</a></td><td>org.apache.derby.impl.drda.DDMWriter uses wrong algorithm to avoid spliting varchar in the middle of a multibyte char.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2692">DERBY-2692</a></td><td>Client driver doesn't chain exceptions received from the server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2689">DERBY-2689</a></td><td>Deadlock with GenericPreparedStatement</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2686">DERBY-2686</a></td><td>The skip method for some InputStreams and Readers return invalid values</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2673">DERBY-2673</a></td><td>If derby.system.home does not exist Derby should only attempt to create that specific folder, not any missing parents (ie. use File.mkdir(), not File.mkdirs())</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2671">DERBY-2671</a></td><td>Errors/messages early in starting the network server through NetworkServerControl.start() are not reported to the PrintWriter passed into start().</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2654">DERBY-2654</a></td><td>Document newly-supported (in embedded mode) JDBC methods for autogenerated keys.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2652">DERBY-2652</a></td><td>Clob.setCharacterStream differs between embedded and client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2619">DERBY-2619</a></td><td> A Derby source release must include the documentation source files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2613">DERBY-2613</a></td><td>upgrade test problem when attempting to test 10.0.2.1 - </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2610">DERBY-2610</a></td><td>Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2607">DERBY-2607</a></td><td>DatabaseMetaData is not consistent about throwing SqlException when tablename=null</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2606">DERBY-2606</a></td><td>Derby should print the parameters to failed statements to the derby.log when it logs the error </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2604">DERBY-2604</a></td><td>Implement Clob support for locators</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2603">DERBY-2603</a></td><td>Minor erratum in page of VARCHAR in Derby Reference manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2597">DERBY-2597</a></td><td>Language result sets should not reuse current isolation level across executions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2594">DERBY-2594</a></td><td>Revoking a privilege from an SQL Object should invalidate statements dependent on that object</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2593">DERBY-2593</a></td><td>Add documentation for the CREATE TABLE as subquery clause</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2591">DERBY-2591</a></td><td>DataDictionaryImpl.getSystemSQLName() may generate duplicates</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2584">DERBY-2584</a></td><td>Creating a database with JPOX SchemaTool sometimes gives ArrayIndexOutOfBoundsException when getIndexInfo() is called</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2581">DERBY-2581</a></td><td>Callers of SanityManager.THROWASSERT should chain the exceptions when possible</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2580">DERBY-2580</a></td><td>SanityManager.THROWASSERT(String,Throwable) ignores message argument</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2579">DERBY-2579</a></td><td>AssertFailure class should use JDK's built-in chaining of exceptions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2570">DERBY-2570</a></td><td>Create a utility which generates Release Notes</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2566">DERBY-2566</a></td><td>OutOfMemory/Sanity-assert failed when updating database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2558">DERBY-2558</a></td><td>client trhows ArrayIndexOutOfBounds exception instead of parameter out of range </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2556">DERBY-2556</a></td><td>Code paths for db restore do not use doPrivileged-calls, causing SecurityException</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2551">DERBY-2551</a></td><td>Global Xid value garbled in syscs_diag.transaction_table.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2549">DERBY-2549</a></td><td>ArrayIndexOutOfBoundsException in SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2538">DERBY-2538</a></td><td>Update documentation to describe the expected behavior when a JDBC 4 app creates a JDBC 3 datasource.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2526">DERBY-2526</a></td><td>Wrong results with queries that use the JOIN ... ON syntax to join with views or other non-base table expressions.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2521">DERBY-2521</a></td><td>Building derby outputs (from ant) various information messages that are marked as warning severity.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2520">DERBY-2520</a></td><td>Document new restrictions of database shutdown, encryption and hard upgrade powers</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2511">DERBY-2511</a></td><td>reference manual's description of JDBC4 features has misleading sections</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2501">DERBY-2501</a></td><td>Batch scripts in bin\ report extraneous errors when DERBY_HOME is invalid</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2500">DERBY-2500</a></td><td>Assertion failure preparing query with AND and OR in where clause</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2493">DERBY-2493</a></td><td>Use unsynchronized collections in BackingStoreHashtable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2489">DERBY-2489</a></td><td>Document the policy-reloading system procedure.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2488">DERBY-2488</a></td><td>When loaded by jvm1.6 - EmbeddedConnectionPoolDataSource is not returning a JDBC 4 compliant PooledConnection object</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2480">DERBY-2480</a></td><td>DriverManager.getConnection leaks memory when connecting to a non-existent database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2472">DERBY-2472</a></td><td>Use Throwable.initCause() to improve error reporting</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2462">DERBY-2462</a></td><td>org.apache.derby.impl.store.access.BackingStoreHashTableFromScan does not honor ResultSet holdability</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2459">DERBY-2459</a></td><td>Ordering on a CASE-expression casues a NullPointerException when using a UNION</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2456">DERBY-2456</a></td><td>File stream is left open when an exception occurs while setting up a character stream for data export.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2450">DERBY-2450</a></td><td>Clob.Position returning wrong value when operating on Reader</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2444">DERBY-2444</a></td><td>Implement not implemented methods Blob.getBinaryStream(long pos, long length) and Clob. getCharacterStream(long pos, long length) in the Network Client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2443">DERBY-2443</a></td><td>Implement ResultSet updateClob/updateBlob methods on the NetworkClient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2431">DERBY-2431</a></td><td>Documentation for DatabaseMetaData should reflect that getColumnPrivileges and getTablePrivileges are implemented</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2425">DERBY-2425</a></td><td>ResultSetMetaData.getColumnDisplaySize() returns a negative value for BLOB columns for client </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2406">DERBY-2406</a></td><td>XAResource.end does not set the XA transaction state correctly when the XAException is thrown</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2400">DERBY-2400</a></td><td>Javadoc - clean up Cloudscape references in javadoc</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2391">DERBY-2391</a></td><td>"Derby and standards" section of Developer's Guide needs reorganization</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2390">DERBY-2390</a></td><td>DOCS - Merge Working with Derby and Getting Started Guide</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2387">DERBY-2387</a></td><td>DOCs - Reorder the topics in the Ref Manual into Alphabetical order - functions, procedures</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2386">DERBY-2386</a></td><td>timestampdiff function fails when using SQL_TSI_FRAC_SECOND for datepart parameter, except for very small intervals</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2383">DERBY-2383</a></td><td>ReuseFactory should use the constants in java.lang.Boolean</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2381">DERBY-2381</a></td><td>ParameterMappingTest fails due to ArrayIndexOutOfBoundsException executing a procedure</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2377">DERBY-2377</a></td><td>Document language based ordering which will be implemented by code related sub-tasks of DERBY-1478.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2376">DERBY-2376</a></td><td>Patch available to make .classpath entries portable - relative to ECLIPSE_HOME</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2372">DERBY-2372</a></td><td>Document the secure-by-default network server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2371">DERBY-2371</a></td><td>Setting a default value for a VARCHAR column fails when column contains data</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2370">DERBY-2370</a></td><td>EXISTS may return the wrong value for sub-queries involving set operations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2369">DERBY-2369</a></td><td>NetworkServerControl.shutdown() takes at least 1.5 seconds, could be faster.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2365">DERBY-2365</a></td><td>Brushing up pages for MAX and MIN in Derby Reference Manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2364">DERBY-2364</a></td><td>improve documentation to explain logged/unlogged operations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2361">DERBY-2361</a></td><td>Documentation should give examples for using the different security mechanisms</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2355">DERBY-2355</a></td><td>Wrong URL in Eclipse-Plugin Lab Example Jays.java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2350">DERBY-2350</a></td><td>Use of XML values in the action statement of a trigger throw exceptions.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2331">DERBY-2331</a></td><td>Disallow code in installed jars from resolving classes in the org.apache.derby.* namespace except for public apis.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2330">DERBY-2330</a></td><td>Disallow user-defined SQL routines to resolve to entry points (methods in classes) in the org.apache.derby.* namespace</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2323">DERBY-2323</a></td><td>Update Graphic in Dev Guide - Embedded deployment application overview</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2301">DERBY-2301</a></td><td>Documentation of different executeBatch error handling between embedded and DerbyNetClient needed</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2296">DERBY-2296</a></td><td>getProperties method deprecated on ClientDataSource</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2281">DERBY-2281</a></td><td>Update the Tuning Guide figure about using the statement cache</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2279">DERBY-2279</a></td><td>JDBC3 driver is loaded instead of JDBC4 when running with jdk1.7 </td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2275">DERBY-2275</a></td><td>XSLT changes for PDF output</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2272">DERBY-2272</a></td><td>SSL Documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2263">DERBY-2263</a></td><td>Update the copyright dita files to mark Derby logo images as non-substantive images (for accessibility)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2262">DERBY-2262</a></td><td>DatabaseMetaData.getTypeInfo returns incorrect MAXIMUM_SCALE value for DECIMAL and NUMERIC types</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2260">DERBY-2260</a></td><td>DatabaseMetaData.getTypeInfo() returns incorrect precision for VARCHAR FOR BIT DATA</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2259">DERBY-2259</a></td><td>DatabaseMetaData.getTypeInfo() SEARCHABLE column returns incorrect information for types that cannot be searched.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2258">DERBY-2258</a></td><td>DatabaseMetaData.getTypeInfo() does not list supported Derby SQL types correctly.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2256">DERBY-2256</a></td><td>Wrong Results: Use of decimal values in an IN-list with INTEGER left operand can lead to extra rows.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2244">DERBY-2244</a></td><td>DatabaseMetaData.supportsExpressionsInOrderBy() returns false</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2243">DERBY-2243</a></td><td>DatabaseMetaData.supportsANSI92EntryLevelSQL() returns false for embedded, true for client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2237">DERBY-2237</a></td><td>Cleanup copyrights in the DITA source and generated docs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2230">DERBY-2230</a></td><td>AssertFailure: ByteCode Conditional then/else stack mismatch</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2228">DERBY-2228</a></td><td>Support Derby on J2ME/CDC/Foundation 1.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2226">DERBY-2226</a></td><td>Move column bitset computation to IndexToBaseRowNode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2223">DERBY-2223</a></td><td>Let BasePage.fetchFieldFromSlot use the special single-col FetchDescriptor ctor</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2222">DERBY-2222</a></td><td>'show indexes in SCHEMANAME' does not work with the client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2220">DERBY-2220</a></td><td>Uncommitted transactions executed throught XAResource will held locks after the application terminates (or crashes during the transaction).</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2218">DERBY-2218</a></td><td>Null Pointer Exception when an untyped NULL subquery ("values null") appears outside of the FROM list in a SELECT query.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2216">DERBY-2216</a></td><td>Allow demo SimpleApp to work in J2ME environment</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2214">DERBY-2214</a></td><td>Fix Getting Started file to reflect classpath change</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2208">DERBY-2208</a></td><td>setNetworkServerCP scripts need not add derby.jar into the CLASSPATH</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2202">DERBY-2202</a></td><td>DROP PROCEDURE depends on SET SCHEMA</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2195">DERBY-2195</a></td><td>Nested triggers not working properly after maximum trigger count exception is thrown</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2193">DERBY-2193</a></td><td>[import] ERROR 38000: StringIndexOutOfBoundsException was thrown while evaluating an expression.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2191">DERBY-2191</a></td><td>Cleanup of FormatableBitSet</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2183">DERBY-2183</a></td><td>Trigger recompilation problem when trigger action has its table not qualified with a schema</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2166">DERBY-2166</a></td><td>Implement proper handling of SocketTimeoutException in DRDAConnThread</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2152">DERBY-2152</a></td><td>Support diagnostic vti tables that take parameters, such as SpaceTable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2150">DERBY-2150</a></td><td>Reduce use of synchronized collections in GenericLanguageConnectionContext</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2149">DERBY-2149</a></td><td>Replace Vectors and Hashtables with ArrayLists and HashMaps in RAMTransaction</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2147">DERBY-2147</a></td><td>LIKE predicate does not accept a pure column reference as righthand operand (gives ERROR 42824)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2141">DERBY-2141</a></td><td>BlobClob4BlobTest.testPositionBlob() fails with NullPointerException</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2138">DERBY-2138</a></td><td>Remove DataDictionaryContext and associated code</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2137">DERBY-2137</a></td><td>CALL (PROCEDURE) statement documentation in reference manual has incomplete syntax for arguments</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2124">DERBY-2124</a></td><td>Incorrect method name in error message for Connection.setTransactionIsolation method</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2123">DERBY-2123</a></td><td>Remove workaround for old JIT bug from StoredPage</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2122">DERBY-2122</a></td><td>Optimize ContainerLock.isCompatible()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2121">DERBY-2121</a></td><td>Remove JDK 1.3 build dependency in network server</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2118">DERBY-2118</a></td><td>Change some boundary checks in ArrayInputStream to ASSERTs to improve performance</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2114">DERBY-2114</a></td><td>Let Clock embed a HashMap rather than inherit from Hashtable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2112">DERBY-2112</a></td><td>Nullpointer on executeBatchRequestX when preparedStatement has no parameters</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2107">DERBY-2107</a></td><td>Move page latching out of the lock manager</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2103">DERBY-2103</a></td><td>After a Lexical Error due to syntax error , even a simple create table does not work on the same connection.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2099">DERBY-2099</a></td><td>Make BasePage.getPageId() final</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2096">DERBY-2096</a></td><td>Change the Parser.parserStatement() to return the more specific StatementNode instead of QueryTreeNode.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2093">DERBY-2093</a></td><td>Error in initSlotTable() can cause NPE or ASSERT rather than reporting page number in corrupt page message.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2088">DERBY-2088</a></td><td>Update the documentation templates. Add comment about changing the reference ID</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2083">DERBY-2083</a></td><td>Shutting down a database loaded from a jar leaves an open file reference to the jar file containing the database.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2067">DERBY-2067</a></td><td>Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2060">DERBY-2060</a></td><td>SET CURRENT ISOLATION in ref.man refers java.sql.Connection.setTransactionLevel instead of java.sql.Connection.setTransactionIsolation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2057">DERBY-2057</a></td><td>SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE documentation or implementation error on its arguments.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2053">DERBY-2053</a></td><td>Dev Guide: Syntax errors in SQL tips -&gt; Tricks of the VALUES clause -&gt; Multiple rows</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2050">DERBY-2050</a></td><td>Manipulating CachedItems could be more efficient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2046">DERBY-2046</a></td><td>Make class org.apache.derby.iapi.store.raw.PageKey final</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2042">DERBY-2042</a></td><td>Provide documentation for new RENAME COLUMN statement</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2040">DERBY-2040</a></td><td>Setting derby.database.classpath to contain installed jars causes the database to be unbootable when a Securitymanager is installed.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2019">DERBY-2019</a></td><td>IJ's describe command does not handle quotes very well</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2018">DERBY-2018</a></td><td>NullPointerException in CREATE VIEW ... VALUES NULL;</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2001">DERBY-2001</a></td><td>Add DITA templates for the 3 topic types into the trunk</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1995">DERBY-1995</a></td><td>Add base schema scripts for order entry</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1993">DERBY-1993</a></td><td>Check in the demo used by the Java in the Database session at Apachecon 2006</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1983">DERBY-1983</a></td><td>Change build system so that base level is JDK 1.4</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1965">DERBY-1965</a></td><td>NetworkServerControlImpl never closes the socket or streams it opens in setUpSocket.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1964">DERBY-1964</a></td><td>Update the documentation of SYSCS_UTIL.SYSCS_COMPRESS_TABLE for the changes that went in as part of DERBY-737</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1959">DERBY-1959</a></td><td>10.2 'Derby Developer's Guide' error/ambiguity.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1956">DERBY-1956</a></td><td>Remove stale code from the statement classes in the client driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1955">DERBY-1955</a></td><td>Unquoted path in .bat files may cause errors (Win)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1953">DERBY-1953</a></td><td>Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1949">DERBY-1949</a></td><td>locate function documentation should clarify behavior when first parameter is empty string</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1947">DERBY-1947</a></td><td>OutOfMemoryError after repeated calls to boot and shutdown a database</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1942">DERBY-1942</a></td><td>There exists difference between behavior of setNull(Types.TIME) and setTiime(null).</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1935">DERBY-1935</a></td><td>Reference Manual - Derby Limitations</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1934">DERBY-1934</a></td><td>Reference Manual updates - J2EE Compliance: Java Transaction API and javax.sql Extensions</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1930">DERBY-1930</a></td><td>Move JDBC implementation notes into the published javadoc</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1929">DERBY-1929</a></td><td>SYSTABLEPERMS and SYSCOLPERMS documentation needs to be updated</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1928">DERBY-1928</a></td><td>Update table "Support for SQL-92 Features: Basic schema manipulation" for GRANT/REVOKE</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1926">DERBY-1926</a></td><td>Provide documentation for ALTER TABLE DROP COLUMN</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1922">DERBY-1922</a></td><td>readme.html under frameworks does not mention about Derby client and some minor typos in example.html</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1920">DERBY-1920</a></td><td>DOCS - Improve topic titles for vague and duplicate topics</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1919">DERBY-1919</a></td><td>Top level index.html page should link to release notes and other items in top-level of a release.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1918">DERBY-1918</a></td><td>INCREMENT of IDENTITY column described as allowing a value of zero in reference manual</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1917">DERBY-1917</a></td><td>Clob.position fails with Embedded driver and large Clobs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1890">DERBY-1890</a></td><td>improve XSDFI error message</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1879">DERBY-1879</a></td><td>Save meta data related information for an EmbedResultSet at the plan level instead of the ResultSet level improves performance.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1868">DERBY-1868</a></td><td>Merge argument descriptors into SQLState strings so that SQLState documentation can be generated by a program</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1861">DERBY-1861</a></td><td>Column ordering ASSERT when combining column references and expressions in same ORDER BY</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1852">DERBY-1852</a></td><td>Wrong results: duplicate rows returned for nested UNIONs when they should be eliminated.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1847">DERBY-1847</a></td><td>SELECT statement asserts with XJ001 when attempted to select a newly added column in SQL authorization mode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1828">DERBY-1828</a></td><td>Access rule violations should use a SQL state starting with '42' according to the SQL standard.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1822">DERBY-1822</a></td><td>LOCK TABLE example and description in reference manual should get replaced by a 'real' example</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1816">DERBY-1816</a></td><td>Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1815">DERBY-1815</a></td><td>In admin guide examples to start network server on windows with .bat scripts, $DERYBY_INSTALL Is used , I think it should be %DERBY_INSTALL%</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1805">DERBY-1805</a></td><td>Links to element ids inside a topic are broken in PDFs and HTML Books</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1797">DERBY-1797</a></td><td>Building toursdb would go a little faster if it used autocommit off mode.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1795">DERBY-1795</a></td><td>Graphics not copied over for PDF and HTML-single manuals</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1765">DERBY-1765</a></td><td>Update ALTER TABLE documentation to reflect DERBY-119 (ALTER COLUMN [NOT]NULL)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1753">DERBY-1753</a></td><td>Doc for SYSCS_INPLACE_COMPRESS_TABLE has incorrect procedure name in the java examples.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1752">DERBY-1752</a></td><td>Fix javadoc to account for changes required by new licence header policy.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1709">DERBY-1709</a></td><td>Deprecate scripts in frameworks directory</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1673">DERBY-1673</a></td><td>Compling with jikes not longer works due to recent changes that added -target -source command line flags to each compile</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1665">DERBY-1665</a></td><td>Incorrect JavaDoc for Qualifier interface</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1662">DERBY-1662</a></td><td>Document derbyrun.jar</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1644">DERBY-1644</a></td><td>NPE when inserting values to a table that has a column declared as generated by default as identity</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1624">DERBY-1624</a></td><td>use of direct column name rather than alias make aggregation fail (Hibernate depends on that)</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1623">DERBY-1623</a></td><td>Add ANSI TRIM implementation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1620">DERBY-1620</a></td><td>SQL CASE statement returns ERROR 42X89 when including NULL as a return value</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1610">DERBY-1610</a></td><td>Resolve difference of type compatibility between Embedded and NetworkServer/NetworkDriver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1590">DERBY-1590</a></td><td>Consolidate the *conrefs.dita files in the documentation source tree to a single file.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1589">DERBY-1589</a></td><td>CREATE TABLE throws NullPointerException in Derby SQL Standard Authorization after DROPs and REVOKES</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1588">DERBY-1588</a></td><td>Link "Getting Started...." and "Apache Derby Server ...." in demo.html needs to be linked to actual documents instead of manuals page</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1570">DERBY-1570</a></td><td>The derby configuration, logging and diagnostic properties such as derby.language.logStatementText are hard to find in the documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1535">DERBY-1535</a></td><td>Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1526">DERBY-1526</a></td><td>build should be able to locate the Java runtime libraries from properties not sourced from ${user.home}, but inside the current subversion checkout.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1520">DERBY-1520</a></td><td>Document new SYSCS_DIAG tables</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1519">DERBY-1519</a></td><td>'setAsciiStream' uses different encodings for embedded and client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1501">DERBY-1501</a></td><td>PreparedStatement#setNull(int parameterIndex, int sqlType) throws SQL Exception if given sqlType is LONGVARBINARY in embedded mode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1494">DERBY-1494</a></td><td>PreparedStatement.setNull(int, int) checks type compatibility on embedded, but not on the client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1490">DERBY-1490</a></td><td>Provide ALTER TABLE RENAME COLUMN functionality</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1489">DERBY-1489</a></td><td>Provide ALTER TABLE DROP COLUMN functionality</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1484">DERBY-1484</a></td><td>Client and embedded behave differently when the table name is null in DatabaseMetaData methods</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1440">DERBY-1440</a></td><td>jdk 1.6 client driver omits SQLStates and chained exceptions in error messages</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1434">DERBY-1434</a></td><td>Client can send incorrect database name to server after having made multiple connections to different databases.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1381">DERBY-1381</a></td><td>Document ij.exceptionTrace property</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1377">DERBY-1377</a></td><td>Update copyright headers to comply with new ASF policy</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1355">DERBY-1355</a></td><td>ClientDriver ResultSetMetaData.isAutoIncrement(column) always returns false</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1285">DERBY-1285</a></td><td>Finish JDBC3 Blob implementation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1275">DERBY-1275</a></td><td>Provide a way to enable client tracing without changing the application</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1132">DERBY-1132</a></td><td>Truncation Error with Concat</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1054">DERBY-1054</a></td><td>Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-931">DERBY-931</a></td><td>Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-908">DERBY-908</a></td><td>YEAR,SECOND,MONTH, MINUTE, HOUR and DAY functions have incorrect information on durations.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-815">DERBY-815</a></td><td>Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-806">DERBY-806</a></td><td>One each deleted or updated from a heap row a new RowPosition object is created.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-801">DERBY-801</a></td><td>Allow parallel access to data files.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-790">DERBY-790</a></td><td>SQLException used by the networked interface to Derby is not serializable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-729">DERBY-729</a></td><td>Scalar time and date functions return 0 instead NULL when argument is NULL</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-681">DERBY-681</a></td><td>Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-680">DERBY-680</a></td><td>In ij, executing a prepared statement with numeric/decimal parameter fails with NullPointerException in J2ME/CDC/FP</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-630">DERBY-630</a></td><td>create trigger fails with null pointer exception</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-606">DERBY-606</a></td><td>SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-595">DERBY-595</a></td><td>Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-552">DERBY-552</a></td><td>Fetching resources using getResourceAsStream from a jar stored in a database that is archived in a jar file fails</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-538">DERBY-538</a></td><td>Investigate using the standard java.net.URLClassLoader for database class loading.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-537">DERBY-537</a></td><td>SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-415">DERBY-415</a></td><td>sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-396">DERBY-396</a></td><td>Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-391">DERBY-391</a></td><td>Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-378">DERBY-378</a></td><td>support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-264">DERBY-264</a></td><td>This enhancement to allow expressions in ORDER BY clause will require documentation changes.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-234">DERBY-234</a></td><td>Documentation of DateTime types is incomplete</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-208">DERBY-208</a></td><td>Add support to retrieve lobs for Network Server by locator rather than matierializing the LOB</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-183">DERBY-183</a></td><td>Parameter names required in CREATE FUNCTION</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-147">DERBY-147</a></td><td>ERROR 42X79 not consistant ? - same column name specified twice</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-64">DERBY-64</a></td><td>Create a table with a query</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-47">DERBY-47</a></td><td>Some possible improvements to IN optimization</td>
+</tr>
+</table>
+</blockquote>
+<h2>
+<a name="Issues"></a>Issues</h2>
+<blockquote>
+<p>Compared with the previous release (10.2.2.0), Derby release 10.3.1.4 introduces the following new features and incompatibilities. These merit your special attention.</p>
+<ul>
+<li>
+<a href="#Note for DERBY-2925">
+<p>Note for DERBY-2925:
+Prevent export from overwriting existing files
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2757">
+<p>Note for DERBY-2757:
+Security enhancements to the Network Server may slow down Derby's runtime performance, and
+ they may trigger SecurityExceptions when Derby executes user-written
+ functions and procedures.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2729">
+<p>Note for DERBY-2729: Blob and Clob objects are released when the
+transaction ends and when the connection is closed.</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2610">
+<p>Note for DERBY-2610:
+The table name can no longer be a pattern in calls to DatabaseMetaData
+methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo,
+getVersionColumns, getPrimaryKeys, getImportedKeys, getExportedKeys
+and getCrossReference.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2526">
+<p>Note for DERBY-2526: Queries which use the JOIN ... ON syntax to join with views or other
+non-base table expressions may now return different results.<br>
+
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2443">
+<p>Note for DERBY-2443: Added unimplemented methods introduced in the java.sql.ResultSet
+interface.</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2430">
+<p>Note for DERBY-2430:
+The application
+will see an error in the event of calling setObject(int targetType,
+Blob source) and setObject(int targetType, Clob source) with a
+targetType other than Blob and Clob. This will be in conformance with
+the embedded behaviour.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2386">
+<p>Note for DERBY-2386:
+The return type of the timestampdiff function has been changed from INT to BIGINT.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2370">
+<p>Note for DERBY-2370: EXISTS predicates with subqueries that use set operators (UNION,
+INTERSECT, EXCEPT) may now behave differently.</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2296">
+<p>Note for DERBY-2296:
+ClientDataSource now supports the createDatabase and shutdownDatabase properties.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2264">
+<p>Note for DERBY-2264:
+Henceforth, when authentication is enabled
+(<code>derby.connection.requireAuthentication</code> has the
+value <code>true</code>) <i>and</i> SQL Authentication is enabled
+(<code>derby.database.sqlAuthentication</code> has the
+value <code>true</code>) some database level operations are restricted
+to the <i>database owner</i>.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2256">
+<p>Note for DERBY-2256: Use of decimal values in an IN predicate whose left operand is an
+INTEGER may now return different results.<br>
+
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2196">
+<p>Note for DERBY-2196:
+The user should customize the security policy which the Network Server
+ now installs by default.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2108">
+<p>Note for DERBY-2108:
+SSL/TLS implemented for client/server communication.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2020">
+<p>Note for DERBY-2020:
+Writing of the transaction log to disk has been changed to open log files in "rwd" mode instead of "rws" if the JVM supports it.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1942">
+<p>Note for DERBY-1942: The use of the TIME data type is more restricted. </p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1852">
+<p>Note for DERBY-1852: Queries with nested set operators (UNION, INTERSECT, EXCEPT) in a
+FROM list may now return different results.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1828">
+<p>Note for DERBY-1828:
+Most authorization failures have new error codes.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1816">
+<p>Note for DERBY-1816: ResultSet.getTime() on an SQL TIMESTAMP value now has millisecond
+resolution with the Derby client driver.<br>
+
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1610">
+<p>Note for DERBY-1610:
+In a number of usage cases of setNull(int, int) and set*(int, null, int) methods for PreparedStatement and CallableStatement, Derby's Client implementation has been changed, to correctly behave in the same way as the Embedded implementation.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1519">
+<p>Note for DERBY-1519:
+Streams obtained by calling get-/setAsciiStream in the client driver use encoding "ISO-8859-1" instead of "US-ASCII".
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1484">
+<p>Note for DERBY-1484:
+The table name can no longer be null in calls to DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys and getExportedKeys.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1341">
+<p>Note for DERBY-1341: Added unimplemented methods introduced in the JDBC 3.0 and 4.0
+specification. Blob and Clob now support all the methods of JDBC 3.0 and 4.0.</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-729">
+<p>Note for DERBY-729:
+Scalar time and date functions should return NULL when the argument is NULL
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-415">
+<p>Note for DERBY-415:
+Sysinfo now presents separate command switches to check the classpath for the presence of the Derby client and the DB2 JCC driver.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-208">
+<p>Note for DERBY-208: Network Client: Locator-based implementation of Blob/Clob
+operations.
+</p>
+</a>
+</li>
+</ul>
+<hr>
+<h3>
+<a name="Note for DERBY-2925"></a>Note for DERBY-2925</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>
+Prevent export from overwriting existing files
+</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>
+Due to security concerns, and to avoid accidental file damage, Export processing
+will not overwrite existing files. As a result, applications may observe some behavioral changes with respect to Export operations.
+</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>
+<OL>
+ <LI>SYSCS_UTIL.SYSCS_EXPORT_TABLE: Exports of all the data from a table to an existing file is no longer possible and the user/application must remove the existing file, otherwise ERROR XIE0S will be returned. </LI>
+ <LI>SYSCS_UTIL.SYSCS_EXPORT_QUERY: Exports of all the data returned from the SELECT statement to an existing file is no longer possible and the user/application must remove the existing file, otherwise ERROR XIE0S will be returned. </LI>
+ <LI>SYSCS_UTIL.SYSCS_EXPORT_QUERY_LOBS_TO_EXTFILE: Export of the result of a SELECT statement to a main data output file, and the LOB data into a large object auxiliary file to an existing file is no longer possible and the user/application must remove the existing data file and/or large object auxiliary file, otherwise ERROR XIE0S will be returned if the data file exists or ERROR XIE0T will be returned if the large object auxiliary file exists.</LI>
+
+</OL>
+</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>
+Due to security concerns and to avoid accidental file damage, Export processing will no longer overwrite an existing file.
+</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 application needs to specify a different filename which does not exist or delete the existing file before performing the Export operation.
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2757"></a>Note for DERBY-2757</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>
+Security enhancements to the Network Server may slow down Derby's runtime performance, and
+ they may trigger SecurityExceptions when Derby executes user-written
+ functions and procedures.
+</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>
+Startup performance for networked applications may degrade after upgrading to 10.3. In addition,
+ after upgrade, user-written functions and procedures may raise SecurityExceptions.
+</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>
+In previous releases, the Network Server booted without
+installing a default security
+ manager. Now, the Network Server
+ installs a security manager if the user forgets to. Application
+ startup may slow down as the security manager performs initial access
+ checks on Derby tables. Once all user tables have been touched,
+ the application should reach steady state and the drag induced
+ by the security manager should be negligible.
+</p>
+
+
+<p>
+In addition, SecurityExceptions may occur if user-written functions
+ and procedures perform sensitive operations such as
+ reading/writing files and getting/setting system properties.
+</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>
+In a client/server configuration, it is particularly important to
+ protect against other users' mistakes and hacking. Derby is enhancing
+ security for this configuration.
+Now if you neglect to configure a Java security
+ manager, the Network Server attempts to install its own security
+ manager with a default policy.
+</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>
+SecurityExceptions can be avoided by installing your own security
+ manager with your own policy file, which grants the appropriate
+ privileges to your user-written code. Instructions on how to do
+ this can be found in the Derby Developer's Guide in the section
+titled "Running Derby under a security manager" and in the
+Derby Server and Administration Guide in the section titled
+"Running the Network Server under the security manager".
+</p>
+
+
+<p>
+If for some reason this is not practical, or if the startup
+ performance drag is intolerable, then you can instruct the
+ server to not install a security manager. You do this by booting
+ the server with the "-noSecurityManager" command line option as
+ explained in above-mentioned section of the Derby Server and Administration Guide.
+</p>
+
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2729"></a>Note for DERBY-2729</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>Blob and Clob objects are released when the
+transaction ends and when the connection 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>Applications now get a SQLException with SQL STATE XJ215 when
+ accessing Blobs and Clobs after the transaction ends or the
+ connection is closed.</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>
+In the previous release, Blobs and Clobs were sometimes usable even
+ after the transaction ended or the connection was closed. Now Blobs
+ and Clobs are not usable after these events.
+</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>
+Now Blobs and Clobs store their data in temporary files.
+These temporary files are deleted when the transaction ends.
+The Blob.free() and Clob.free() methods also delete these temporary files.
+This erases the transient state of these large objects and makes them
+unusable.
+</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 should be revised to not use Blobs and Clobs after
+ the transaction ends or the connection is closed.
+</p>
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2610"></a>Note for DERBY-2610</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 table name can no longer be a pattern in calls to DatabaseMetaData
+methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo,
+getVersionColumns, getPrimaryKeys, getImportedKeys, getExportedKeys
+and getCrossReference.
+</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 methods returned information on all
+tables that matched the pattern in the schema. A table name value of
+null was treated as a wildcard. Table names now have to match what is
+stored in the database. </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>
+Calls to the specified methods now fail if the table name parameter is a pattern (no information is returned).
+</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 behavior violated the JDBC standard. The new behavior is correct.
+</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 recode applications to specify the table names. When
+information on multiple tables is required, the application first has
+to get the table names, e.g. by using the DatabaseMetaData method
+getTables(), and then use the returned table names as input to the
+method in question. </p>
+
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2526"></a>Note for DERBY-2526</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>Queries which use the JOIN ... ON syntax to join with views or other
+non-base table expressions may now return different results.<br>
+
+</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 which use the explicit JOIN ... ON syntax to perform
+joins between three or more FROM expressions, at least one of which is
+a view, subquery, or other non-base table expression, may have been
+seeing incorrect results prior to this release.<br>
+
+</p>
+
+<p>As an example, take the following:<br>
+
+</p>
+
+<p>
+<span style="font-family: monospace;"> create table t1 (c0
+int);<br>
+ create table x (c1 int, c2 int);<br>
+ create table t2 (c3 int, c4 int);<br>
+
+<br>
+ insert into t1 values 1;<br>
+ insert into x values (0, 1);<br>
+ insert into t2 values (0, 2);</span>
+
+</p>
+
+<p>With these tables, the following query should return one row, but
+was returning zero rows in previous releases:<br>
+
+</p>
+
+<p>
+<span style="font-family: monospace;"> select t1.* from</span>
+<span style="font-family: monospace;">
+t1 JOIN (select * from x) vw(c1,c2) ON (t1.c0 = vw.c2)</span>
+<span style="font-family: monospace;">
+JOIN t2 ON (vw.c1 = t2.c3)<br>
+
+</span>
+</p>
+
+<p>This problem has been fixed in Derby 10.3.
+</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 fix for the bug shown above does not introduce any functional
+incompatibilities. However, applications may now see different
+results if they happen to use queries that rely on the JOIN ... ON
+syntax to
+join with views, subqueries, or other non-base table expressions. </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>Due to an error in column reference mappings, it was possible for
+earlier versions of Derby
+to confuse ON predicate column references with each other, thereby
+leading to incorrect computation of transitive closure. This in
+turn could lead to the addition of invalid predicates to the query,
+which caused wrong results in certain cases.<br>
+
+</p>
+
+<p>By fixing this bug we ensure that the affected queries will always
+return the correct results.<br>
+
+</p>
+
+<h4>Application Changes Required</h4>
+
+<p>
+No application changes should be needed.<br>
+
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2443"></a>Note for DERBY-2443</h3>
+<blockquote>
+
+
+<h4>Summary of Change</h4>
+
+<p>Added unimplemented methods introduced in the java.sql.ResultSet
+interface.</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>Existing application won't be effected by it as these methods are
+new implementations. Applications won't be getting Not Implemented
+exception anymore.</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 add implementations for unimplemented Blob and Clob related
+methods in the ResultSet interface.</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 can now make use of the following new methods</p>
+
+
+<pre>
+void updateBlob(int columnIndex, Blob x) throws SQLException
+void updateBlob(String columnName, Blob x) throws SQLException
+
+void updateClob(int columnIndex, Clob x) throws SQLException
+void updateClob(String columnName, Clob x) throws SQLException
+
+void updateBlob(int columnIndex, InputStream x, long length) throws SQLException
+void updateBlob(String columnName, InputStream x, long length) throws SQLException
+
+void updateClob(int columnIndex, Reader x, long length) throws SQLException
+void updateClob(String columnName, Reader x, long length) throws SQLException
+
+</pre>
+
+
+<p>
+Detailed
+description of these methods can be found in api docs of Java SE 6:
+<a href="http://java.sun.com/javase/6/docs/api/java/sql/ResultSet.html">ResultSet</a>.
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2430"></a>Note for DERBY-2430</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>Derby's Client implementation will return an error matching the
+behavior with Embedded in the event when setObject(int targetType,
+Blob source) and setObject(int targetType, Clob source) is called
+with a targetType other than Blob and Clob.</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 application
+will see an error in the event of calling setObject(int targetType,
+Blob source) and setObject(int targetType, Clob source) with a
+targetType other than Blob and Clob. This will be in conformance with
+the embedded behaviour.
+</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's Client
+implementation and Embedded implementation should behave the same way
+from the point of view of an application whenever possible.
+</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
+relying on the Client behaving in the old way will have to be
+adjusted.
+</P>
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2386"></a>Note for DERBY-2386</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 return type of the timestampdiff function has been changed from INT to BIGINT.
+</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(s), using the builtin timestampdiff function using the SQL_TSI_FRAC_SECOND for the datepart parameter would return an integer overflow error except with very small intervals, less then a second, because the result would exceed the range of an INT.
+For intervals larger than a second, SQL_TSI_SECOND had to be used. Now, the result type has been changed to BIGINT and so one can use intervals &gt; 1 sec with SQL_TSI_FRAC_SECOND.
+However as a result of the change SQL functions that take the result of the timestampdiff function as a parameter of datatype INT will no longer be resolved.
+</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>
+As a result of the change, the result type for the timestampdiff function is now BIGINT. Applications which use the return value as a parameter to an SQL function will find that the SQL function can no longer be resolved.
+</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 behavior required the application developer to know ahead of time the range for the timestampdiff. Returning BIGINT enables the function to cope with a larger range.
+</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>
+SQL functions taking the result of a timestampdiff function as a parameter will have to be modified to take a BIGINT parameter instead of INT.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2370"></a>Note for DERBY-2370</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>EXISTS predicates with subqueries that use set operators (UNION,
+INTERSECT, EXCEPT) may now behave differently.</p>
+
+<p>
+
+</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 which specify set operations inside of an EXISTS predicate
+may have been seeing incorrect results for such queries. For
+example, the following query should return a single row with column
+"OK":
+</p>
+
+
+<pre>
+select * from ( values 'OK' ) as T where exists (values 1 except values 2)
+</pre>
+
+
+<p>Prior to Derby 10.3, though, that query would incorrectly return
+zero rows.
+</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>
+Prior to Derby 10.3 a user could specify "SELECT *" within an EXISTS
+predicate's set operation and Derby took the "*" to be a single
+column. As a result, some queries would compile and execute
+without error even when they should have failed. As an example,
+the following query would succeed even if table T2 had more than one
+column:
+</p>
+
+
+<pre>
+select * from ( values 'OK') as T where exists
+ (select i from T1 union select * from T2)
+</pre>
+
+
+<p>As of version 10.3 Derby no longer allows this. Changes
+to fix the incorrect query results make it so that the above query will
+now throw an error (42X58) if T2 has more than one column, because then
+the left and right result sets of the union would not have the same
+number of result columns.
+</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>
+Due to the way in which Derby internally handles result columns within
+an EXISTS predicate, it was possible for queries having EXISTS
+predicates with set operators to return incorrect results. By
+internally rewriting the EXISTS subquery when it is a set operator, we
+can ensure that Derby now evaluates such predicates correctly.
+For more on the details of the rewrite, see DERBY-2370.
+</p>
+
+<h4>Application Changes Required</h4>
+
+<p>
+
+</p>
+
+<p>As a result of the new internal rewrite, any "*" that appears within
+the EXISTS set operation will now be properly expanded. This
+means that applications which specify set operations inside of an
+EXISTS predicate
+must now ensure that the result sets to which a given set operation
+applies have the same number of result columns. See the
+"incompatibilities" section above for details. No other
+application changes are required.</p>
+
+<p>
+
+</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.
+-->
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2296"></a>Note for DERBY-2296</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>
+ClientDataSource now supports the createDatabase and shutdownDatabase properties.
+</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 functionality is new for ClientDataSources. Previously, applications
+ could not call these methods. Now these methods work:
+</p>
+
+<blockquote>
+
+<ul>
+
+<li>setCreateDatabase (String) </li>
+
+<li>getCreateDatabase() </li>
+
+<li>setShutdownDatabase (String) </li>
+
+<li>getShutdownDatabase() </li>
+
+</ul>
+
+</blockquote>
+
+
+<p>
+These methods should behave similarly to the ones in Embedded, i.e.
+only valid value for setCreateDatabase is "create", and for
+setShutdownDatabase is "shutdown". In essence, at connection time, if
+set to a valid value, the property is passed on to the server side with
+the ConnectionAttributes.<br>
+Note, that the result for setting contradicting properties for
+createDatabase and ShutdownDatabase, whether through
+setCreateDatabase("create") and setShutdownDatabase("shutdown") or via
+setConnectionAttributes("create=true") or ("shutdown=true") is
+undefined.
+</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>No incompatibilities were introduced.
+</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>
+With version 10.2.1.6 an incompatibility with 10.1.1.0 was introduced -
+since revision 393003, the undocumented, non-standard but
+previously public method, getProperties for Client DataSources was
+removed for security reasons. This left only the
+setConnectionAttributes method available for creating or shutting down
+a database, and caused hardship for applications that had previously
+taken advantage of the getProperties method. For instance, in Geronimo
+the getProperties method was
+previously used to inquire and set whether a create=true was set for a
+database.<br>
+Support for the four methods already existing for EmbeddedDataSource
+was requested for ClientDataSource to compensate for the disappearance
+of getProperties as a public method.
+</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>Application code will need to be adjusted if they want to take
+advantage of these new methods for ClientDataSources.<br>
+
+<br>
+
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2264"></a>Note for DERBY-2264</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>
+Henceforth, when authentication is enabled
+(<code>derby.connection.requireAuthentication</code> has the
+value <code>true</code>) <i>and</i> SQL Authentication is enabled
+(<code>derby.database.sqlAuthentication</code> has the
+value <code>true</code>) some database level operations are restricted
+to the <i>database owner</i>.
+</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>
+When connecting to an existing database to
+<ul>
+
+<li>shut down the database</li>
+
+<li>encrypt a previously unencrypted database</li>
+
+<li>re-encrypt an encrypted database with a new bootPassword or a
+ new encryption key</li>
+
+<li>perform a full (as opposed to soft) upgrade of the database from
+ a previous version</li>
+
+</ul>
+an SQLException with SQLState "08004" is thrown. For the English
+locale the exception string will be one of:
+<ul>
+
+<li>User <i>user</i> cannot shut down database <i>database</i>. Only
+ the database owner can perform this operation.</li>
+
+<li>User <i>user</i> cannot (re)encrypt
+ database <i>database</i>. Only the database owner can perform this
+ operation.</li>
+
+<li>User <i>user</i> cannot hard upgrade
+ database <i>database</i>. Only the database owner can perform this
+ operation.</li>
+
+</ul>
+
+<!--
+ 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>
+In release 10.2, any authenticated user would be able to:
+<ul>
+
+<li>Shut down the database.</li>
+
+<li>Encrypt a previously unencrypted database.</li>
+
+<li>Re-encrypt an encrypted database with a new bootPassword or a
+ new encryption key.</li>
+
+<li>Perform a full (as opposed to soft) upgrade of the database from
+ a previous version.</li>
+
+</ul>
+In 10.3, if both authentication and sqlAuthentication are enabled, an
+application which tries to perform any such operation by connecting as
+any user other than the <i>database owner</i>, will see an
+SQLException with SQLState "08004" and the operation will not be
+performed.
+</p>
+
+<p>
+The check on full upgrade pertains to upgrades from 10.2.* (and
+subsequent) releases of Derby only. When upgrading from 10.0 or 10.1
+any valid user can still do the full upgrade. This user then becomes
+the database owner. The reason for this difference is that the
+database owner concept was first introduced in 10.2. Note that once
+you upgrade, the database owner can not be changed.
+</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>
+These changes were introduced to enhance Derby security by limiting operations
+which impact all users of a database - with potentially far-reaching
+effects - to the data base owner.
+</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>
+Impacted applications must now be changed to perform these operations
+as <i>the database owner</i>, that is, supplying the authorization
+identifier (i.e. user name) of the database owner when connecting to
+perform these operations.
+</p>
+
+
+<p>
+
+<b>Note:</b> The database owner is identical to the authorization
+identifier (i.e. user name) used when the database was created or user
+name used when upgrading from 10.0 or 10.1 as the case may be. If the
+database was created or upgraded <i>without</i> supplying a user name
+(authentication not enabled) the database owner defaults to "APP".
+</p>
+
+<p>
+The following query can be used to show the database owner:
+</p>
+
+<p>
+
+<code>
+select authorizationid from sys.sysschemas where schemaname = 'SYS';
+</code>
+
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2256"></a>Note for DERBY-2256</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>Use of decimal values in an IN predicate whose left operand is an
+INTEGER may now return different results.<br>
+
+</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 which use an IN predicate to see if an integer value is
+contained within a list of decimal values may have been seeing
+incorrect results prior to this release. In some cases rows may
+have been missing from the result; in other cases, additional
+(incorrect) rows may have been returned.<br>
+
+</p>
+
+<p>As an example, take the following:<br>
+
+</p>
+
+<p style="font-family: monospace;"> create table t1 (i int);<br>
+ insert into t1 values 1, 2, 3, 4, 5;<br>
+
+</p>
+
+<p style="font-family: monospace;"> -- Following query was
+returning zero rows when it should return 1 row.<br>
+ select * from t1 where i in (4.23, 4);
+<br>
+
+</p>
+
+<p>
+<span style="font-family: monospace;"> -- Following query
+should return zero rows but was returning 1 row.</span>
+<span style="font-family: monospace;"> select * from t1 where i
+in (2.8, 4.23);<br>
+
+</span>
+</p>
+
+<p>This problem has been fixed in Derby 10.3.<br>
+
+</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 fix for the bug shown above does not introduce any functional
+incompatibilities. However, applications may now see different
+results if they happen to use queries which rely on an IN predicate to
+check for integer values within a list of decimal values. </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's behavior in previous releases was incorrect and could lead
+to wrong results.<br>
+
+</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 application changes should be needed.<br>
+
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2196"></a>Note for DERBY-2196</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 user should customize the security policy which the Network Server
+ now installs by default.
+</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>
+When booted from the command line, the Network Server now installs a security manager with a default policy.
+This policy does not expose the application to any additional
+ risks. However, the policy is overbroad and the user should
+ customize it in order to reduce security threats.
+</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>
+Blah blah blah.
+</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 is providing more security support.
+</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>
+Instead of relying on the default policy installed by the Network
+ Server, the user should further limit the scope of privileged operations.
+In particular, the
+ user should fine-tune the blanket read/write privilege granted
+ on the entire server file system. The user should narrow this
+ privilege to just the directories needed for backup/restore,
+ import/export, and jar file loading.
+For instructions on how to refine the policy file, please consult
+ the Derby Server and Administration Guide section titled
+"Customizing the Network Server's security policy".
+</p>
+
+
+<p>
+This is also an opportunity for the user to enable user authentication
+ if the Network Server currently runs without
+ authentication. Running in a client/server configuration without
+ authentication exposes the application and the server machine to
+ many threats. It is strongly discouraged. For instructions on enabling
+ user authentication, please consult the Derby Developer's Guide
+ section titled "Working with user authentication".
+</p>
+
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2108"></a>Note for DERBY-2108</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>
+SSL/TLS implemented for client/server communication.
+</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>
+Several error messages have been changed to reflect failure scenarios
+which may involve SSL:
+</p>
+<p>
+
+<b>SQLExceptions:</b>
+
+</p>
+<p>
+The message<br>
+<code>ERROR 58009: A communications error has been detected</code>
+
+<br>has been extended to give the underlying cause. E.g. if the underlying
+cause is an SSL problem, you get
+<br>
+<code>ERROR 58009: A communications
+error has been detected. Unrecognized SSL message, plaintext
+connection?</code>
+
+</p>
+<p>
+The message<br>
+
+<code>ERROR 58009: A network protocol error was encountered and the
+connection has been terminated: A PROTOCOL Data Stream Syntax Error
+was detected. Reason: 0x3.</code>
+
+<br>has been changed to
+<br>
+<code>ERROR
+58009: A network protocol error was encountered and the connection has
+been terminated: A PROTOCOL Data Stream Syntax Error was detected.
+Reason: 0x3. Plaintext connection attempt to an SSL enabled
+server?</code>
+
+</p>
+<p>
+
+<b>Other error messages:</b>
+
+</p>
+<p>
+If the server socket can't be established when a server is started,
+the message
+<br>
+<code>Could not listen on port NNNN on host XXXX</code>
+<br>
+has been extended to give the underlying cause, e.g:
+<br>
+<code>Could not listen on port NNNN on host XXXX:
+ java.net.BindException: Address already in use</code>
+
+</p>
+<p>
+If a plaintext server is connected by an SSL enabled client, you will
+see messages like this in the server log:
+<br>
+<code>Execution failed
+because of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT
+arg = 0; Error Em Value = 3. Plaintext connection attempt from an
+SSL enabled client?</code>
+
+</p>
+<p> If a plaintext administration command is used towards an SSL
+server, the message <br>
+<code>Invalid reply header from network
+server: Invalid string xxxx.</code>
+<br> has been changed to
+<br>
+<code>Invalid reply header from network server: Invalid string
+xxxx. Plaintext connection attempt to an SSL enabled server?</code>
+
+</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>
+Applications which rely on the content of error message texts may 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 messages had to be extended due to more failure scenarios when
+connecting a client to a Derby server.
+</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 recode applications to recognize the changed messages.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2020"></a>Note for DERBY-2020</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>
+Writing of the transaction log to disk has been changed to open log files in "rwd" mode instead of "rws" if the JVM supports it.
+</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>
+With JVMs/OSs that support the functionality, such as JDK version 1.4.2 and up on Solaris, a performance improvement may be noticed. On other platforms, no change may be noticeable.
+
+</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>
+For writing the transaction log to disk Derby uses a RandomAccessFile. Before this change, if it was supported by the JVM, the log files were opened in "rws" mode making the file system take care of syncing writes to disk. "rws" mode ensured that both the data and the file meta-data was updated for every write to the file. On some operating systems (e.g. Solaris) this lead to two write operations to the disk for every write issued by Derby. This was limiting the throughput of update intensive applications. By changing the file mode to "rwd" the number of updates to the disk is reduced.
+
+Some JVMs have a bug in the support for "rws" and "rwd" mode. Derby will check for this bug, and if it is detected, Derby will revert back to using "rw" mode and print an appropriate message indicating this in derby.log.
+</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 needed or possible to benefit from this change. If your JVM supports it, it will be used. If Derby detects that your JVM has a bug in the support for "rwd", a message will be printed to derby.log:<br>
+------------ BEGIN ERROR MESSAGE ------------- <br>
+LogToFile.checkJvmSyncError: Your JVM seems to have a problem with implicit syncing of log files. Will use explicit syncing instead. <br>
+------------ END ERROR MESSAGE ------------- <br>
+
+
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1942"></a>Note for DERBY-1942</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 use of the TIME data type is more restricted. </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 might encounter an error that indicates incompatible data types, when values are
+passed using the TIME data type. </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>In previous releases, applications could call the setTime method for variables
+that use the TIMESTAMP data type, if the passing value was null. Starting with
+this release, calling the setTime method fails for variables that use the TIMESTAMP data type,
+regardless of the value that is passed.
+</p>
+
+<p>Moreover, applications were allowed to pass values that used the TIME data type to
+a parameter of the DATETIMEDIFF function in the previous release. Starting with this release,
+instead of using the TIME data type, the TIMESTAMP data type must be used to pass a parameter
+of the DATETIMEDIFF function. </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 TIME data type is classified as a data type for time
+ information. Unlike the TIMESTAMP and DATE data types, the TIME
+ data type is special case. The TIME data type does not represent
+ a specific instant or one time frame but represents all
+ instants, every day. For example, if TIME is 20:42, this
+ represents 20:42 regardless of the date. 20:42 today, 20:42
+ tomorrow, and so forth. Starting with this release, the TIME
+ data type is regarded completely different from the TIMESTAMP
+ data type. </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 using the TIME data type must use the TIMESTAMP data
+ type instead, if date information is needed besides time
+ information.
+</p>
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1852"></a>Note for DERBY-1852</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>Queries with nested set operators (UNION, INTERSECT, EXCEPT) in a
+FROM list may now return different results.
+</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 Derby documentation indicates that if the 'ALL' keyword is not
+specified when using a set operator, the default behavior is to remove
+duplicate rows from the result. There is, however, a specific
+type of query in which previous versions of Derby would incorrectly
+include duplicate rows, even if "ALL" was not specified. The
+queries in question have all of the following characteristics:<br>
+
+</p>
+
+<ol>
+
+<li>A chain of two or more set operators appears in the FROM list of
+a SELECT query; <span style="font-style: italic;">and</span>
+<br>
+
+</li>
+
+<li> There exists at least one nested set operator in the chain which:<br>
+a) is *not* the top-level set operator in the chain, and<br>
+b) which does *not* include "ALL"; <span style="font-style: italic;">and</span>
+</li>
+
+<li>The result of the set operator from #2 includes duplicate rows; <span style="font-style: italic;">and</span>
+</li>
+
+<li>None of the set operators which sit above the set operator from
+#2 in the query tree removes duplicates.<br>
+
+</li>
+
+</ol>
+
+<p>A query which satisfies all of these conditions would return
+incorrect results (duplicate rows) in previous releases. Consider
+the following simple example:<br>
+
+</p>
+
+<span style="font-family: monospace;"> create view vw(i) as
+values 1, 2 union values 2 union all values 3;<br>
+
+<br>
+ -- Both of the following queries are equally affected by this
+issue.<br>
+
+<br>
+ select * from vw;<br>
+ select * from (values 1, 2
+union values 2 union all values 3) x</span>
+<br>
+
+<p>In this example the chain of unions is as follows:</p>
+
+<p style="font-family: monospace;">
+
+<pre>
+ union_1 all
+ / \
+ union_2 values 3
+ / \
+ values 1, 2 values 2
+</pre>
+
+</p>
+
+<p>Note that <span style="font-family: monospace;">union_2</span> is
+nested within <span style="font-family: monospace;">union_1</span>,
+and that <span style="font-family: monospace;">union_2</span> has
+duplicate values ("2"). Also note that <span style="font-family: monospace;">union_1</span> has an "ALL" specified
+and thus does not remove duplicates. So we've satisfied the above
+criteria and we would expect that, since <span style="font-family: monospace;">union_2</span> does not have the "ALL"
+keyword, the duplicate "2" rows should be removed before evaluation of <span style="font-family: monospace;">union_1</span>. But in previous
+releases of Derby this removal of duplicates did not happen. Thus
+the query would incorrectly return four rows, with the value "2" being
+duplicated.<br>
+
+</p>
+
+<h4>Incompatibilities with Previous Release</h4>
+The fix for the bug shown above does not introduce any functional
+incompatibilities. However, applications may see different
+results if they happen to use queries which satisfy the conditions
+outlined above. Such applications may also see slightly increased
+execution times for the relevant queries due to the fact that Derby
+internally sorts the nested results to remove duplicates.<br>
+<!--
+ 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 behavior gave incorrect results.
+</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 application changes should be needed.
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1828"></a>Note for DERBY-1828</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>
+Most authorization failures have new error codes.
+</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, authorization failures had error codes 2850x
+and 04501. In this release, most of these errors have new error codes.
+The code changes are: 04501, 2850H, 2850I and 2850J are now 08004.
+28506-2850G are now 42500-4250A, 28501 is now 4250B, 28503-28505 are
+now 4250C-4250E. Only the error codes have been changed; error
+messages are not affected.
+</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>
+Applications that are dependant on authorization error codes may 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 old error codes violated the SQL standard. The new error codes
+are correct.
+</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 are dependant on authorization error codes must be
+recoded to expect the new codes.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1816"></a>Note for DERBY-1816</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>ResultSet.getTime() on an SQL TIMESTAMP value now has millisecond
+resolution with the Derby client driver.<br>
+
+</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>
+JDBC applications which a) use the Derby client driver, and b) use
+ResultSet.getTime() to retrieve a java.sql.Time object from an SQL
+TIMESTAMP value would, in previous releases, always get a java.sql.Time
+object whose milliseconds field was zero. This would be the case
+even though a Derby SQL TIMESTAMP has nanosecond resolution.<br>
+
+</p>
+
+<p>With this release the Derby client driver now matches the embedded
+driver in that a call to ResultSet.getTime() on an SQL TIMESTAMP will
+return a java.sql.Time object with the correct millisecond resolution.<br>
+
+</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>
+This change does not introduce any functional
+incompatibilities. Applications using the Derby client driver
+will now see correct millisecond values when they call
+ResultSet.getTime() to retrieve an SQL TIMESTAMP. </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>While it is true that a Derby SQL TIME value has by definition
+resolution of only a second, the java.sql.Time class is not a direct
+mapping to the SQL Type. Rather, it's a JDBC type, and the JDBC
+java.sql.Time class has a precision of milliseconds. So when
+retrieving a java.sql.Time value from an SQL TIMESTAMP, Derby should
+retain the millisecond precision.<br>
+
+</p>
+
+<p>Note that the Derby embedded driver correctly retained millisecond
+precision in previous releases. With the latest release, the
+client driver now matches that behavior.<br>
+
+</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 application changes should be needed.<br>
+
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1610"></a>Note for DERBY-1610</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 a number of usage cases of setNull(int, int) and set*(int, null, int) methods for PreparedStatement and CallableStatement, Derby's Client implementation has been changed, to correctly behave in the same way as the Embedded implementation.
+</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 a number of method calls involving null values for PreparedStatement and CallableStatement, Derby's Client implementation behaved differently from the Embedded implementation.
+Now, in most cases, the Client returns an error where Embedded returns an error and succeeds where Embedded succeeds.
+For instance:
+<ol>
+
+<li>setNull(LONGVARCHAR) on parameter of type CHAR FOR BIT DATA (Types.BINARY).
+In previous releases, Embedded returned an error (SQLState 22005), but the Client did not. Now, both Embedded and Client will return an error.</li>
+
+<li> setNull(LONGVARBINARY) on parameter of type CHAR FOR BIT DATA (Types.BINARY).
+In previous releases, this call succeeded with Embedded, but the Client returned an error (SQLState 22005). Now, such a call will succeed with both Embedded and Client.</li>
+
+<li> setNull(LONGVARBINARY) on parameter of type VARCHAR FOR BIT DATA (Types.VARBINARY).
+In previous releases, the call succeeded with Embedded, Client returned an error (SQLState 22005). Now, such a call will succeed with both Embedded and Client.</li>
+
+<li> setNull(BINARY) on parameter of type LONG VARCHAR FOR BIT DATA (Types.LONGVARBINARY).
+In previous releases, such a call succeeded with Embedded, but Client returned an error (SQLState 22005). Now, such a call will succeed with both Embedded and Client.</li>
+
+<li> setNull(TIME) on parameter of TIMESTAMP.
+In previous releases, Embedded returned an error (SQLState 22005), but the Client did not. Now, both Embedded and client will return an error.</li>
+
+</ol>
+Similar differences existed with the set&lt;type&gt;(int, null) calls.<br>
+Note, that where an error is returned, the actual SQLState returned may still be different between the two implementations.
+</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>
+Now, in the cases indicated above, the Client and Embedded implementation show the behavior previously shown only with Embedded.
+</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's Client implementation and Embedded implementation should behave the same way from the point of view of an application whenever possible.
+</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 relying on the Client behaving in the old way will have to be adjusted.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1519"></a>Note for DERBY-1519</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>
+Streams obtained by calling get-/setAsciiStream in the client driver use encoding "ISO-8859-1" instead of "US-ASCII".
+</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>
+Strange symbols might appear in text, or text seems garbled. Where a
+question mark was printed previously, another character (printable or
+non-printable) may occur. The described symptoms only apply for the client driver.
+</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>
+Ascii streams in the client driver can now return 8-bit values in the range 0 -
+255, whereas they previously returned 7-bit values in the range 0-127. As a
+consequence, all 8-bit values are also accepted as input.
+</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 JDBC specification defines Ascii as values in the range 0 - 255.
+"US-ASCII" only contains 7-bit values, and cannot represent
+the full range. "ISO-8859-1" can represent the full range.
+</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 accessing Ascii streams from Derby through the client driver must
+be extended to handle 8-bit values.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1484"></a>Note for DERBY-1484</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 table name can no longer be null in calls to DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys and getExportedKeys.
+</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, a table name value of null was treated as a wildcard. Derby now raises an SQLException if the table name is null.
+</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>
+Calls to the specified methods now fail if the table name parameter is null (SQLException is thrown).
+</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 behavior violated the JDBC standard. The new behavior is correct.
+</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 recode applications to specify the table names. When information on multiple tables is required, the application first has to get the table names, e.g. by using the DatabaseMetaData method getTables(), and then use the returned table names as input to the method in question.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1341"></a>Note for DERBY-1341</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>Added unimplemented methods introduced in the JDBC 3.0 and 4.0
+specification. Blob and Clob now support all the methods of JDBC 3.0 and 4.0.</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>Existing application won't be effected by it as these methods are
+new implementations. Applications won't be getting Not Implemented
+exception anymore.</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 support all the methods in Blob and Clob introduced in the latest JDBC Specification.<br>
+
+
+<br>
+
+
+
+</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 can now make use of following newly added methods</p>
+
+<span style="font-weight: bold;">java.sql.Blob
+</span>
+<br>
+
+
+<div style="margin-left: 40px;">InputStream
+getBinaryStream(long pos, long length) throws SQLException <br>
+
+OutputStream
+setBinaryStream(long pos)
+throws SQLException<br>
+
+int
+setBytes(long pos, byte[] bytes)
+throws SQLException<br>
+
+int
+setBytes(long pos, byte[] bytes, int offset, int len)
+throws SQLException<br>
+
+void
+truncate(long len)
+throws SQLException<br>
+
+
+</div>
+
+
+<span style="font-weight: bold;">java.sql.Clob
+</span>
+<br>
+
+
+<div style="margin-left: 40px;">Reader
+getCharacterStream(long pos, long length)
+throws SQLException<br>
+
+OutputStream
+setAsciiStream(long pos)
+throws SQLException<br>
+
+Writer
+setCharacterStream(long pos)
+throws SQLException<br>
+
+int
+setString(long pos, String str)
+throws SQLException<br>
+
+int
+setString(long pos, String str, int offset, int len)
+throws SQLException<br>
+
+void
+truncate(long len)throws SQLException<br>
+
+
+<br>
+
+
+</div>
+
+Detailed description of these methods can be found in api docs of Java SE 6<br>
+
+
+<div style="margin-left: 40px;">
+<br>
+
+
+<a href="http://java.sun.com/javase/6/docs/api/java/sql/Blob.html">http://java.sun.com/javase/6/docs/api/java/sql/Blob.html</a>
+<br>
+
+
+<a href="http://java.sun.com/javase/6/docs/api/java/sql/Clob.html">http://java.sun.com/javase/6/docs/api/java/sql/Clob.html</a>
+</div>
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-729"></a>Note for DERBY-729</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>
+Scalar time and date functions should return NULL when the argument is NULL
+</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, the scalar time and date functions returned 0 when the argument is NULL.
+This has now been corrected.
+</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>
+With this release, the scalar time and date functions will return NULL when the argument is NULL.
+</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 behavior was incorrect.
+</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 rely on the old behavior will have to be changed to expect/check for NULL as return value instead of 0.
+</p>
+
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-415"></a>Note for DERBY-415</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>
+Sysinfo now presents separate command switches to check the classpath for the presence of the Derby client and the DB2 JCC driver.
+</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>
+Previously, if you ran "java org.apache.derby.tools.sysinfo -cp client SimpleApp.class" you got a message indicating that the DB2 JCC driver was not found in your classpath, even though you had the Derby Client library in your classpath.
+Now "-cp client" only checks for the presence of the Derby client.
+To check for the presence of the DB2 JCC driver jar, you can pass the new "-cp db2driver" argument.
+</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>
+To check for the presence of the DB2 JCC driver, you must use the new
+"-cp db2driver" argument.
+</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 behavior has changed in order to eliminate a confusing diagnostic
+ message.
+</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 who want to check for the presence of the DB2 JCC driver will
+ need to use the new command switch.
+</p>
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-208"></a>Note for DERBY-208</h3>
+<blockquote>
+
+
+
+<h4>Summary of Change</h4>
+
+<p>Network Client: Locator-based implementation of Blob/Clob
+operations.
+</p>
+
+<h4>
+<!-- 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.
+-->Symptoms
+Seen by Applications Affected by Change</h4>
+
+<p>
+<FONT FACE="Thorndale, serif">Memory requirements for handling
+large Blob/Clob values in the Network Client are significantly
+reduced. As a result of this, applications may observe some
+behavioral changes with respect to Blob/Clob operations.</FONT>
+</p>
+
+<h4>
+<!-- OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
+
+ For instance:
+
+ Applications which open two InputStreams on the ResultSet column now
+ fail.
+-->Incompatibilities
+with Previous Release</h4>
+
+<OL>
+
+<LI>Life span for Blob/Clob objects: Blob/Clob objects are no
+ longer valid after the transaction in which they were created has
+ been terminated (committed or rolled back).</LI>
+
+<LI>Stream access to Blob/Clob values: Streams obtained to read
+ from Blob/Clob objects (E.g., Blob.getBinaryStream()), would in
+ previous releases not reflect any changes made to the object after
+ the stream was created. In Derby 10.3, it is unpredictable what a
+ read operation on a stream will see of changes made between the
+ creation of the stream and the time of the read operation. This
+ means that applications that interleaves reads and writes of a
+ Blob/Clob object may observe a changed behavior.</LI>
+
+</OL>
+
+<h4>
+<!-- DESCRIBE WHY THE CHANGE WAS MADE.
+
+ For instance:
+
+ The previous behavior violated the JDBC standard. The new behavior
+ is correct.
+-->Rationale
+for Change</h4>
+
+<p>
+<FONT FACE="Thorndale, serif">In earlier versions of the Derby
+Network Client, Blob and Clob operation caused the entire objects to
+be materialized in memory. For large values, this required large
+amounts of memory on the client side. To reduce the resource usage,
+a locator-based scheme has been implemented. The JDBC driver will
+hold references to server-side Blob/Clob values, and use these
+references to request the server to perform operations on the values.
+ Hence, the Network Client will no longer need large amounts of
+memory too materialize large values in memory.</FONT>
+</p>
+
+<p>
+<FONT FACE="Thorndale, serif">The incompatibilities are introduced
+because it was difficult to maintain the previous behavior when the
+Blob/Clob objects are no longer materialized in memory.</FONT>
+</p>
+
+<h4>
+<!-- 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.
+-->Application
+Changes Required</h4>
+
+<p>Applications that access Blob/Clob objects after the transaction
+they were created in has committed need to be changed. Make sure
+that the commit of the transaction is delayed until the objects are
+no longer needed. This means that if the same object is to be used
+in several statements, these statements will have to run in the same
+transaction (i.e., auto-commit may not be used in such cases). Also
+note that if auto-commit is used, a transaction will be committed
+when the result set is closed. Hence, when using auto-commit one
+must delay the closing of the result set until the Blob/Clob objects
+are no longer needed.</p>
+
+</blockquote>
+<h2>
+<a name="Open Bugs"></a>Open Bugs</h2>
+<blockquote>
+<p>For open bugs please refer to the JIRA bug tracking system: <a href="http://issues.apache.org/jira/browse/DERBY">http://issues.apache.org/jira/browse/DERBY</a>
+</p>
+<p>However, of special interest in particular for existing applications are the following bugs open at the time of the 10.3.1.4 release:</p>
+<table border="2">
+<tr>
+<td><b>Issue Id</b></td><td><b>Description</b></td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2436">DERBY-2436</a></td><td>SYSCS_IMPORT_TABLE can be used to read derby files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2437">DERBY-2437</a></td><td>SYSCS_EXPORT_TABLE can be used to overwrite derby files</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 > 32665 bytes value with Network Server does not release locks</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2905">DERBY-2905</a></td><td>Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.</td>
+</tr>
+</table>
+</blockquote>
+<h2>
+<a name="Build Environment"></a>Build Environment</h2>
+<blockquote>
+<p>Derby release 10.3.1.4 was built using the following environment:</p>
+<ul>
+<li>
+<b>Branch</b> - Source code came from the 10.3 branch.</li>
+<li>
+<b>Machine</b> - SunOS 5.11 snv_48.</li>
+<li>
+<b>Ant</b> - Apache Ant version 1.6.5 compiled on June 2 2005.</li>
+<li>
+<b>JDK 1.4</b> - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03).</li>
+<li>
+<b>Java 6</b> - Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-b105).</li>
+<li>
+<b>OSGi</b> - The osgi.jar was used to build org.apache.derby.osgi.EmbeddedActivator.</li>
+<li>
+<b>Compiler</b> - The 1.4.2_12-b03 javac was used to compile all
+ classes except for the JDBC4 drivers. The JDBC4 driver classes were compiled
+ using the 1.6.0-b105 javac.</li>
+<li>
+<b>JSR 169</b> - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).</li>
+</ul>
+</blockquote>
+</body>
+</html>
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/NetworkServerControl.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/NetworkServerControl.bat
new file mode 100644
index 0000000..2041a94
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/NetworkServerControl.bat
@@ -0,0 +1,38 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+CALL "%~dp0derby_common.bat" %*
+
+if "%_JAVACMD%"=="" goto end
+
+if "%_USE_CLASSPATH%"=="no" goto runNoClasspath
+if not "%CLASSPATH%"=="" goto runWithClasspath
+
+:runNoClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%LOCALCLASSPATH%" org.apache.derby.drda.NetworkServerControl %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:runWithClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%CLASSPATH%;%LOCALCLASSPATH%" org.apache.derby.drda.NetworkServerControl %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:end
+set _JAVACMD=
+set DERBY_CMD_LINE_ARGS=
+
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/dblook.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/dblook.bat
new file mode 100644
index 0000000..980b334
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/dblook.bat
@@ -0,0 +1,38 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+CALL "%~dp0derby_common.bat" %*
+
+if "%_JAVACMD%"=="" goto end
+
+if "%_USE_CLASSPATH%"=="no" goto runNoClasspath
+if not "%CLASSPATH%"=="" goto runWithClasspath
+
+:runNoClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%LOCALCLASSPATH%" org.apache.derby.tools.dblook %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:runWithClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%CLASSPATH%;%LOCALCLASSPATH%" org.apache.derby.tools.dblook %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:end
+set _JAVACMD=
+set DERBY_CMD_LINE_ARGS=
+
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/derby_common.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/derby_common.bat
new file mode 100644
index 0000000..2c14f18
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/derby_common.bat
@@ -0,0 +1,81 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+if exist "%~dp0..\lib\derby.jar" goto libsCopied
+cd %~dp0..\..\plugins\org.eclipse.net4j.db.derby_*
+cd lib
+copy derby.jar ..\..\..\derby\lib
+
+:libsCopied
+cd %~dp0..\work
+
+rem %~dp0 is expanded pathname of the current script under NT
+set DEFAULT_DERBY_HOME=%~dp0..
+
+if "%DERBY_HOME%"=="" set DERBY_HOME=%DEFAULT_DERBY_HOME%
+set DEFAULT_DERBY_HOME=
+
+set _USE_CLASSPATH=yes
+
+rem Slurp the command line arguments. This loop allows for an unlimited number
+rem of arguments (up to the command line limit, anyway).
+set DERBY_CMD_LINE_ARGS=%1
+if ""%1""=="""" goto doneStart
+shift
+:setupArgs
+if ""%1""=="""" goto doneStart
+if ""%1""==""-noclasspath"" goto clearclasspath
+set DERBY_CMD_LINE_ARGS=%DERBY_CMD_LINE_ARGS% %1
+shift
+goto setupArgs
+
+rem here is there is a -noclasspath in the options
+:clearclasspath
+set _USE_CLASSPATH=no
+shift
+goto setupArgs
+
+rem This label provides a place for the argument list loop to break out
+rem and for NT handling to skip to.
+
+:doneStart
+rem check the value of DERBY_HOME
+if exist "%DERBY_HOME%\lib\derby.jar" goto setLocalClassPath
+
+:noDerbyHome
+echo DERBY_HOME is set incorrectly or derby.jar could not be located.
+echo Please set the DERBY_HOME environment variable to the path where you installed Derby.
+goto endcommon
+
+:setLocalClassPath
+set LOCALCLASSPATH=%DERBY_HOME%/lib/derby.jar;%DERBY_HOME%/lib/derbynet.jar;%DERBY_HOME%/lib/derbyclient.jar;%DERBY_HOME%/lib/derbytools.jar
+
+:checkJava
+set _JAVACMD=%JAVACMD%
+
+if "%JAVA_HOME%" == "" goto noJavaHome
+if not exist "%JAVA_HOME%\bin\java.exe" goto noJavaHome
+if "%_JAVACMD%" == "" set _JAVACMD=%JAVA_HOME%\bin\java.exe
+goto endcommon
+
+:noJavaHome
+if "%_JAVACMD%" == "" set _JAVACMD=java.exe
+
+:endcommon
+
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/ij.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/ij.bat
new file mode 100644
index 0000000..2216430
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/ij.bat
@@ -0,0 +1,38 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+CALL "%~dp0derby_common.bat" %*
+
+if "%_JAVACMD%"=="" goto end
+
+if "%_USE_CLASSPATH%"=="no" goto runNoClasspath
+if not "%CLASSPATH%"=="" goto runWithClasspath
+
+:runNoClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%LOCALCLASSPATH%" org.apache.derby.tools.ij %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:runWithClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%CLASSPATH%;%LOCALCLASSPATH%" org.apache.derby.tools.ij %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:end
+set _JAVACMD=
+set DERBY_CMD_LINE_ARGS=
+
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setEmbeddedCP.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setEmbeddedCP.bat
new file mode 100644
index 0000000..3e6fcaa
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setEmbeddedCP.bat
@@ -0,0 +1,33 @@
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+@rem set DERBY_INSTALL=
+
+@if "%DERBY_HOME%"=="" set DERBY_HOME=%DERBY_INSTALL%
+@if "%DERBY_HOME%"=="" goto noderbyhome
+
+@FOR %%X in ("%DERBY_HOME%") DO SET DERBY_HOME=%%~sX
+
+set CLASSPATH=%DERBY_HOME%\lib\derby.jar;%DERBY_HOME%\lib\derbytools.jar;%CLASSPATH%
+@goto end
+
+:noderbyhome
+@echo DERBY_HOME or DERBY_INSTALL not set. Set one of these variables
+@echo to the location of your Derby installation.
+@goto end
+
+:end
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkClientCP.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkClientCP.bat
new file mode 100644
index 0000000..514a92a
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkClientCP.bat
@@ -0,0 +1,33 @@
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+@rem set DERBY_INSTALL=
+
+@if "%DERBY_HOME%"=="" set DERBY_HOME=%DERBY_INSTALL%
+@if "%DERBY_HOME%"=="" goto noderbyhome
+
+@FOR %%X in ("%DERBY_HOME%") DO SET DERBY_HOME=%%~sX
+
+set CLASSPATH=%DERBY_HOME%\lib\derbyclient.jar;%DERBY_HOME%\lib\derbytools.jar;%CLASSPATH%
+@goto end
+
+:noderbyhome
+@echo DERBY_HOME or DERBY_INSTALL not set. Set one of these variables
+@echo to the location of your Derby installation.
+@goto end
+
+:end
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkServerCP.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkServerCP.bat
new file mode 100644
index 0000000..9e8b938
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/setNetworkServerCP.bat
@@ -0,0 +1,32 @@
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+@rem set DERBY_INSTALL=
+
+@if "%DERBY_HOME%"=="" set DERBY_HOME=%DERBY_INSTALL%
+@if "%DERBY_HOME%"=="" goto noderbyhome
+
+@FOR %%X in ("%DERBY_HOME%") DO SET DERBY_INSTALL=%%~sX
+
+set CLASSPATH=%DERBY_HOME%\lib\derbynet.jar;%DERBY_HOME%\lib\derbytools.jar;%CLASSPATH%
+@goto end
+
+:noderbyhome
+@echo DERBY_HOME or DERBY_INSTALL not set. Set one of these variables
+@echo to the location of your Derby installation.
+
+:end
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/startNetworkServer.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/startNetworkServer.bat
new file mode 100644
index 0000000..423159b
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/startNetworkServer.bat
@@ -0,0 +1,39 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+TITLE Derby Server
+
+CALL "%~dp0derby_common.bat" %*
+
+if "%_JAVACMD%"=="" goto end
+
+if "%_USE_CLASSPATH%"=="no" goto runNoClasspath
+if not "%CLASSPATH%"=="" goto runWithClasspath
+
+:runNoClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%LOCALCLASSPATH%" org.apache.derby.drda.NetworkServerControl start
+goto end
+
+:runWithClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%CLASSPATH%;%LOCALCLASSPATH%" org.apache.derby.drda.NetworkServerControl start
+goto end
+
+:end
+set _JAVACMD=
+set DERBY_CMD_LINE_ARGS=
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/stopNetworkServer.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/stopNetworkServer.bat
new file mode 100644
index 0000000..e2cded1
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/stopNetworkServer.bat
@@ -0,0 +1,37 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+CALL "%~dp0derby_common.bat" %*
+
+if "%_JAVACMD%"=="" goto end
+
+if "%_USE_CLASSPATH%"=="no" goto runNoClasspath
+if not "%CLASSPATH%"=="" goto runWithClasspath
+
+:runNoClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%LOCALCLASSPATH%" org.apache.derby.drda.NetworkServerControl shutdown
+goto end
+
+:runWithClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%CLASSPATH%;%LOCALCLASSPATH%" org.apache.derby.drda.NetworkServerControl shutdown
+goto end
+
+:end
+set _JAVACMD=
+set DERBY_CMD_LINE_ARGS=
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/sysinfo.bat b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/sysinfo.bat
new file mode 100644
index 0000000..87b504d
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/bin/sysinfo.bat
@@ -0,0 +1,38 @@
+@echo off
+
+@REM Licensed to the Apache Software Foundation (ASF) under one
+@REM or more contributor license agreements. See the NOTICE file
+@REM distributed with this work for additional information
+@REM regarding copyright ownership. The ASF licenses this file
+@REM to you under the Apache License, Version 2.0 (the
+@REM "License"); you may not use this file except in compliance
+@REM with the License. You may obtain a copy of the License at
+
+@REM http://www.apache.org/licenses/LICENSE-2.0
+
+@REM Unless required by applicable law or agreed to in writing,
+@REM software distributed under the License is distributed on an
+@REM "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+@REM KIND, either express or implied. See the License for the
+@REM specific language governing permissions and limitations
+@REM under the License.
+
+CALL "%~dp0derby_common.bat" %*
+
+if "%_JAVACMD%"=="" goto end
+
+if "%_USE_CLASSPATH%"=="no" goto runNoClasspath
+if not "%CLASSPATH%"=="" goto runWithClasspath
+
+:runNoClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%LOCALCLASSPATH%" org.apache.derby.tools.sysinfo %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:runWithClasspath
+"%_JAVACMD%" %DERBY_OPTS% -classpath "%CLASSPATH%;%LOCALCLASSPATH%" org.apache.derby.tools.sysinfo %DERBY_ARGS% %DERBY_CMD_LINE_ARGS%
+goto end
+
+:end
+set _JAVACMD=
+set DERBY_CMD_LINE_ARGS=
+
diff --git a/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/lib/derbynet.jar b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/lib/derbynet.jar
new file mode 100644
index 0000000..b3ebca7
--- /dev/null
+++ b/features/org.eclipse.emf.cdo.server.product-feature/rootfiles/derby/lib/derbynet.jar
Binary files differ