db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@apache.org
Subject svn commit: r645229 [1/2] - in /db/derby/code/branches/10.4: RELEASE-NOTES.html releaseSummary.xml
Date Sun, 06 Apr 2008 11:48:09 GMT
Author: dyre
Date: Sun Apr  6 04:48:07 2008
New Revision: 645229

URL: http://svn.apache.org/viewvc?rev=645229&view=rev
Log:
10.4 release preparations: Check in new versions of relesaseSummary.xml 
and RELEASE_NOTES.html in preparation for the release candidate. 


Modified:
    db/derby/code/branches/10.4/RELEASE-NOTES.html
    db/derby/code/branches/10.4/releaseSummary.xml

Modified: db/derby/code/branches/10.4/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.4/RELEASE-NOTES.html?rev=645229&r1=645228&r2=645229&view=diff
==============================================================================
--- db/derby/code/branches/10.4/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.4/RELEASE-NOTES.html Sun Apr  6 04:48:07 2008
@@ -1,10 +1,10 @@
 <html>
-<title>Release Notes for Derby 10.3.0.0</title>
+<title>Release Notes for Derby 10.4.1.0</title>
 <body>
 <h1>
-<a name="Release Notes for Derby 10.3.0.0"></a>Release Notes for Derby 10.3.0.0</h1>
+<a name="Release Notes for Derby 10.4.1.0"></a>Release Notes for Derby 10.4.1.0</h1>
 <blockquote>
-<p>These notes describe the difference between Derby release 10.3.0.0 and the preceding release 10.2.2.0.</p>
+<p>These notes describe the difference between Derby release 10.4.1.0 and the preceding release 10.3.2.1.</p>
 </blockquote>
 <ul>
 <li>
@@ -59,705 +59,610 @@
 
 
 <p>
-This is a minor release. The following new features were added:
+This is a feature release. The following new features were added:
 </p>
 
+<ul>
+
+<li>SQL ROW_NUMBER() window function, as described in the SQL 2003
+standard section 6.10, for an empty, inlined window specification. The
+<em>window clause</em>, as described in section 7.11 is not
+implemented.</li>
+
+
+<li>Unique constraints on nullable columns. SQL Feature T591.</li>
+	
+
+<li>Asynchronous replication with manual fail-over.</li>
+
+
+<li>VTI Table Functions.</li>
+
+
+<li>Java Management Extensions (JMX) for Derby, allowing local and remote
+monitoring and management of a running Derby system (this release
+includes a basic set of MBeans - it is expected that more JMX
+functionality will be added in later releases).</li>
+	
+
+<li>SQL bracketed comments (/*..*/). SQL Feature T351.</li>
+
+
+<li>ij continuation marker. Interactive ij shows &gt; prompt until ; is entered.</li>
+	
+
+<li>A JDBC statement object cache in the client driver. Some limitations imposed by the presence of DERBY-3596.</li>
+
+
+<li>Caching of the isolation level and the current schema in the client driver.</li>
+
+
+<li>Implement a new multi-threaded buffer manager to get better scalability on machines with multiple CPUs or multiple cores.</li>
+
+</ul>
 
 </blockquote>
 <h2>
 <a name="Bug Fixes"></a>Bug Fixes</h2>
 <blockquote>
-<p>The following issues are addressed by Derby release 10.3.0.0. These issues are not addressed in the preceding 10.2.2.0 release.</p>
+<p>The following issues are addressed by Derby release 10.4.1.0. These issues are not addressed in the preceding 10.3.2.1 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-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-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-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-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-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-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-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-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-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-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-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-2591">DERBY-2591</a></td><td>DataDictionaryImpl.getSystemSQLName() may generate duplicates</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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-2123">DERBY-2123</a></td><td>Remove workaround for old JIT bug from StoredPage</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3589">DERBY-3589</a></td><td>AllocPage.createPage() doesn't initialize minimumRecordSize correctly</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-2122">DERBY-2122</a></td><td>Optimize ContainerLock.isCompatible()</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3538">DERBY-3538</a></td><td>NullPointerException during execution for query with LEFT OUTER JOIN whose inner table selects all constants.</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-2121">DERBY-2121</a></td><td>Remove JDK 1.3 build dependency in network server</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3458">DERBY-3458</a></td><td>dblook fails on TERRITORY_BASED databases</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3442">DERBY-3442</a></td><td>Reference Manual doesn't state limit on number of identity columns</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3430">DERBY-3430</a></td><td>Inconsistency in JDBC autogen APIs between Connection.prepareStatement(...) and Statement.execute(...)</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3379">DERBY-3379</a></td><td>"No Current connection" on PooledConnection.getConnection() if pooled connection is reused during connectionClosed processing</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-2107">DERBY-2107</a></td><td>Move page latching out of the lock manager</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3373">DERBY-3373</a></td><td>SQL "distinct" and "order by" needed together</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3366">DERBY-3366</a></td><td>Various formatting erros in L10N property files</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-2099">DERBY-2099</a></td><td>Make BasePage.getPageId() final</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3352">DERBY-3352</a></td><td>truncateTable crashed, Caused by: java.lang.NullPointerException</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3350">DERBY-3350</a></td><td>SQL CAST always marks its type as nullable even if the expression to be cast is not nullable</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3343">DERBY-3343</a></td><td>Subsequent calls to PreparedStatement cause SQLIntegrityConstraintViolationException on column that is  "Generated always"</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3322">DERBY-3322</a></td><td>Server guide refers to phantom property in template policy file for the Network Server</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3321">DERBY-3321</a></td><td>NullPointerException for 'NOT EXISTS' with nested subquery</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3316">DERBY-3316</a></td><td>Leak in client if ResultSet not closed</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3308">DERBY-3308</a></td><td>Broken synchronization for event handling in ClientPooledConnection40</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3303">DERBY-3303</a></td><td>ArrayIndexOutOfBoundsException at MergeSort.compare</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3302">DERBY-3302</a></td><td>NullPointerException during recovery of database with territory-based collation</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3301">DERBY-3301</a></td><td>Incorrect result from query with nested EXIST</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3299">DERBY-3299</a></td><td>Uniqueness violation error (23505) occurs after dropping a PK constraint if there exists a foreign key on the same columns.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3298">DERBY-3298</a></td><td>Getting Started manual needs clearer introduction to connection URL</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3288">DERBY-3288</a></td><td>wrong query result in presence of a unique index</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3279">DERBY-3279</a></td><td>Derby 10.3.X ignores ORDER BY DESC when target column has an index and is used in an OR clause or an IN list.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3278">DERBY-3278</a></td><td>Developer's Guide topic cdevdvlp51654 has duplicate information on connection URL</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3274">DERBY-3274</a></td><td>Developer's Guide has duplicate information on database connections</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3262">DERBY-3262</a></td><td>Documentation is missing cross-references for connection URL attributes</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3260">DERBY-3260</a></td><td>NullPointerException caused by race condition in GenericActivationHolder</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3257">DERBY-3257</a></td><td>SELECT with HAVING clause containing OR conditional incorrectly return 1 row - should return 2 rows - works correctly with 10.2 DB</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3253">DERBY-3253</a></td><td>NullPointer Exception (NPE) from query with IN predicate containing two values and joining a view with a large table.  ERROR 38000: The exception 'java.lang.NullPointerException' was thrown while evaluating an expression.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3247">DERBY-3247</a></td><td>Activation for a dynamic ResultSet created from an Prepared/CallableStatement will not be closed until garbage collection indicates it is unused to the LCC and the LCC closes it</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3244">DERBY-3244</a></td><td>NullPointerException in ....B2IRowLocking3.searchLeftAndLockPreviousKey</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3243">DERBY-3243</a></td><td>(jdbc net client) exception during normal iteration through "ResultSet" of "select * from t"</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3238">DERBY-3238</a></td><td>When table contains large LOB values (&gt; ~32K) trigger execution fails for that row with ERROR XCL30: An IOException was thrown when reading a 'BLOB' </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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3231">DERBY-3231</a></td><td>Sorting on COUNT with OR and GROUP BY delivers wrong results.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3230">DERBY-3230</a></td><td>Selecting data from a Table raises Error XN008: Query processing has been terminated due to an error on the server</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3229">DERBY-3229</a></td><td>testSysinfoLocale fails if derbyTools.jar is first in the classpath</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3226">DERBY-3226</a></td><td>BlobLocatorInputStream.read() and ClobLocatorInputStream.read() don't mask out sign bits</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3221">DERBY-3221</a></td><td>"java.sql.SQLException: The conglomerate (-5) requested does not exist." from Derby 10.3.1.4 embedded within Eclipse 3.3 and RAD 7.0</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3215">DERBY-3215</a></td><td>Potential NullPointerException in CachedPage class</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-1935">DERBY-1935</a></td><td>Reference Manual - Derby Limitations</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3214">DERBY-3214</a></td><td>Optimizer can see negative cost estimates when pulling Optimizables from the join order.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3198">DERBY-3198</a></td><td>Using setQueryTimeout will leak sections </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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3194">DERBY-3194</a></td><td>LOCALIZEDDISPLAY of CURRENT_TIMESTAMP returns only the TIME</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3168">DERBY-3168</a></td><td>Reference Manual lacks topics on trace-related connection URL attributes</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3160">DERBY-3160</a></td><td>SYSCS_GET_USER_ACCESS incorrectly treats the passed in user name as a SQL identifier and thus can reports the wrong user information</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3094">DERBY-3094</a></td><td>Grouping of expressions causes NullPointerException</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3084">DERBY-3084</a></td><td>CREATE SCHEMA in refman does not contain material on restrictions in sqlAuthorization mode</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3079">DERBY-3079</a></td><td>Database name is printed twice in derby.log on rollbacks when logStatementText  is enabled</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3060">DERBY-3060</a></td><td>Network Server incorrectly assumes that all SQLExceptions with error code 08004 are caused by an authentication failure.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3044">DERBY-3044</a></td><td>Typos in documentation</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3023">DERBY-3023</a></td><td>Different result rows depending on the sequence of INNER JOIN and OUTER JOIN</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3001">DERBY-3001</a></td><td>SYSTABLES documentation for TABLETYPE should include 'A' (Synonym)</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2983">DERBY-2983</a></td><td>The ResultSet returned by DatabaseMetaData.getFunctions() does not contain a required column named FUNCTION_TYPE.</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-1890">DERBY-1890</a></td><td>improve XSDFI error message</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2939">DERBY-2939</a></td><td>Log file is flushed every time a log buffer gets full</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2935">DERBY-2935</a></td><td>DDMReader.readLengthAndCodePoint() decodes long integer incorrectly</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2892">DERBY-2892</a></td><td>Closing a resultset after retrieving a large &gt; 32665 bytes value with Network Server does not release locks</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-1861">DERBY-1861</a></td><td>Column ordering ASSERT when combining column references and expressions in same ORDER BY</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2815">DERBY-2815</a></td><td>ij doesn't start with J2ME / JSR169 / weme6.1 because attempting to find java.sql.Driver if ij.protocol property is specified</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2733">DERBY-2733</a></td><td>ij rolls through NullPointerException (NPE) with J2ME/JSR169/WEME 6.1.</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2683">DERBY-2683</a></td><td>tools and utilities guide: ij.URLCheck's list of checked attributes is not correct</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2680">DERBY-2680</a></td><td>Reference manual section "Setting attributes.." lacks upgrade=true attribute</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2592">DERBY-2592</a></td><td>Wrong description of IndexName field in public JavaDoc for LockTable</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2585">DERBY-2585</a></td><td>Mistaken description in page of CLOB </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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2559">DERBY-2559</a></td><td>recreating a datasource using javax.naming.Reference from a ClientDataSource40 fails</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2351">DERBY-2351</a></td><td>ORDER BY with expression with distinct in the select list returns incorrect result</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-1765">DERBY-1765</a></td><td>Update ALTER TABLE documentation to reflect DERBY-119 (ALTER COLUMN [NOT]NULL)</td>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2270">DERBY-2270</a></td><td>'18 ' (18 followed by four blanks) needs three more blanks</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2142">DERBY-2142</a></td><td>NullPointerException while using XAConnection/PooledConnection in a heavily contended multithreaded scenario</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2128">DERBY-2128</a></td><td>The word 'class' appears twice for the message SIF01.V</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1823">DERBY-1823</a></td><td>Derby Developer's Guide -  Issues w/ User authentication and authorization extended examples section/paragraph</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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1585">DERBY-1585</a></td><td>derbylang/procedureInTrigger: not able to create trigger due to an open ResultSet</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-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-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-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-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>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1573">DERBY-1573</a></td><td>Unsafe synchronization in NetworkServerControlImpl</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.0.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
-<ul>
-<li>
-<a href="#Note for DERBY-2610">Note for DERBY-2610: ???</a>
-</li>
-<li>
-<a href="#Note for DERBY-2386">Note for DERBY-2386: ???</a>
-</li>
-<li>
-<a href="#Note for DERBY-2296">Note for DERBY-2296:
-ClientDataSource now supports the createDatabase and shutdownDatabase properties.
-</a>
-</li>
-<li>
-<a href="#Note for DERBY-2108">Note for DERBY-2108: ???</a>
-</li>
-<li>
-<a href="#Note for DERBY-1852">Note for DERBY-1852: ???</a>
-</li>
-<li>
-<a href="#Note for DERBY-1828">Note for DERBY-1828:
-Most authorization failures have new error codes.
-</a>
-</li>
-<li>
-<a href="#Note for DERBY-1501">Note for DERBY-1501: ???</a>
-</li>
-<li>
-<a href="#Note for DERBY-1484">Note for DERBY-1484:
-The table name can no longer be a pattern in calls to DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys and getExportedKeys.
-</a>
-</li>
-<li>
-<a href="#Note for DERBY-729">Note for DERBY-729: ???</a>
-</li>
-<li>
-<a href="#Note for DERBY-415">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.
-</a>
-</li>
-<li>
-<a href="#Note for DERBY-119">Note for DERBY-119:
-The ALTER TABLE statement now includes the additional ability to alter
-the NULL / NOT NULL constraint on a column in a table.
-</a>
-</li>
-</ul>
+<h2>
+<a name="Issues"></a>Issues</h2>
+<blockquote>
+<p>Compared with the previous release (10.3.2.1), Derby release 10.4.1.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
+<ul>
+<li>
+<a href="#Note for DERBY-3585">
+<p>Note for DERBY-3585: 
+Shutting down the Network Server now supports user authentication, and
+in fact requires credentials when authentication is enabled.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-3460">
+<p>Note for DERBY-3460: 
+The two following reserved keywords are introduced: <code>NONE</code>
+and <code>CURRENT_ROLE</code>.</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-3301">
+<p>Note for DERBY-3301: 
+Queries with nested EXIST, ANY or IN clauses now return correct results.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-3026">
+<p>Note for DERBY-3026: 
+The <code>frameworks</code> directory (and its contents) has been removed.
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-3013">
+<p>Note for DERBY-3013: 
+The column default value can now also be specified as CURRENT_USER or
+SESSION_USER. 
+
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2892">
+<p>Note for DERBY-2892: 
+  DERBY-2892 fixes the bug: "Closing a resultset after retrieving a large &gt; 32665 bytes value with Network Server does not release locks." The fix  changes the JDBC retrieval of BLOB/CLOB columns release locks and the lob locator after calls to ResultSet.getString(), ResultSet.getCharacterStream(), ResultSet.getBytes() or ResultSet.getBinaryStream().  Previously locks would remain held after these calls.  Note: Locks will still be held for calls to ResultSet.getClob() or ResultSet.getBlob().  The user must call free() or commit or rollback the transation to release these locks.
+
+</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2351">
+<p>Note for DERBY-2351: An ORDER BY clause of a DISTINCT query which specifies to order by a
+column which was not in the DISTINCT list is now rejected, because the
+intent of the query is ambiguous. Previously, Derby instead produced
+non-distinct results.
+Also, an ORDER BY clause which specifies a table-name-qualified column alias
+is now rejected as invalid, where previously it was accepted.</p>
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2065">
+<p>Note for DERBY-2065: 
+Error code changed for embedded connection when  a connection with an open transaction is attempted closed.
+</p>
+</a>
+</li>
+</ul>
+<hr>
+<h3>
+<a name="Note for DERBY-3585"></a>Note for DERBY-3585</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>
+Shutting down the Network Server now supports user authentication, and
+in fact requires credentials when authentication is enabled.
+</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, a network server running with user authentication didn't check
+for user credentials for server shutdown.  Any client could shut down the
+server by calling NetworkServerControl with a shutdown command-line
+argument or by invoking the shutdown() method (provided the shutdown was
+initiated on the host running the server).  While this generated a console
+warning (Connection refused : Invalid authentication.), the server shutdown
+proceeded and could also result in open databases not being properly
+closed.
+</p>
+
+
+<p>
+Now, class NetworkServerControl supports user and password information as
+command-line and constructor arguments.  When running a network server with
+user authentication, a server shutdown now requires user credentials; if
+the user authentication check fails, the client sees an authentication
+error and the running server remains intact.  Note that Derby does not
+yet restrict the shutdown privilege to specific users: the server can
+be shut down by any user on the server machine who presents valid credentials.
+</p>
+
+
+<p>
+In detail, to provide user credentials class
+org.apache.derby.drda.NetworkServerControl now supports new shutdown
+command-line options:
+<blockquote>
+
+<ul>
+
+<li> -user &lt;username&gt; </li>
+
+<li> -password &lt;password&gt; </li>
+
+</ul>
+
+</blockquote>
+as well as two additional constructors with new parameters:
+<blockquote>
+
+<ul>
+
+<li> NetworkServerControl(String userName, String password) </li>
+
+<li> NetworkServerControl(InetAddress address, int portNumber, String
+userName, String password) </li>
+
+</ul>
+
+</blockquote>
+These command-line options or constructor arguments must be used to enable
+a NetworkServerControl instance to shutdown a network server running with
+user authentication.
+</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>
+If running a network server without user authentication (the default) no
+command-line or API incompatibilities will be experienced.
+</p>
+
+
+<p>
+However, some incompatibilities were introduced if running a network
+server with user authentication:
+
+<ol>
+
+<li> The NetworkServerControl command-line usage changes for shutting down
+a sever:
+<blockquote>
+java org.apache.derby.drda.NetworkServerControl shutdown
+</blockquote>
+now results in an exception:
+<blockquote>
+08004:Connection authentication failure occurred. Reason: Invalid authentication.
+</blockquote>
+
+
+<p>
+The remedy is to provide credentials:
+<blockquote>
+java org.apache.derby.drda.NetworkServerControl shutdown -user &lt;username&gt; -password &lt;password&gt;
+</blockquote>
+
+</p>
+
+</li>
+
+
+<li> The NetworkServerControl API usage to programatically shutdown a
+server changes:
+<blockquote>
+
+<code>
+NetworkServerControl nsc = new NetworkServerControl();<br>
+nsc.shutdown();<br>
+
+</code>
+
+</blockquote>
+results in a java.sql.SQLException:
+<blockquote>
+Connection authentication failure occurred. Reason: Invalid authentication.
+</blockquote>
+
+
+<p>
+The remedy is provide credentials to the NetworkServerControl constructor:
+<blockquote>
+
+<code>
+NetworkServerControl nsc = new NetworkServerControl(user,
+password);<br> 
+nsc.shutdown();<br>
+
+</code>
+
+</blockquote>
+
+</p>
+
+</li>
+
+
+<li> Note that there is an edge case
+<blockquote>
+
+<code>
+NetworkServerControl nsc = new NetworkServerControl();<br>
+nsc.start(console);<br>
+...<br>
+nsc.shutdown();<br>
+
+</code>
+
+</blockquote>
+which currently fails with the SQLException shown above.
+
+<p>
+A solution is to create the initial NetworkServerControl instance with user credentials:
+<blockquote>
+
+<code>
+NetworkServerControl nscauth = new NetworkServerControl(user,
+password);<br>
+nscauth.start(console);<br>
+...<br>
+nscauth.shutdown();<br>
+
+</code>
+
+</blockquote>
+Another option is to create a second NetworkServerControl instance with user
+credential arguments for the purpose of server shutdown:
+<blockquote>
+
+<code>
+NetworkServerControl nsc = new NetworkServerControl();<br>
+nsc.start(console);<br>
+...<br>
+NetworkServerControl nscauth = new NetworkServerControl(user,
+password);<br>
+nscauth.shutdown();<br>
+
+</code>
+
+</blockquote>
+
+</p>
+
+</li>
+
+
+<li> If users have their own tests that use Derby's junit test framework,
+they'll have to use a test decorator that takes user credential arguments.
+</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>
+The previous behavior represented a security issue, because any client
+could shut down a network server running with user authentication from the
+same host without needing to provide user credentials.
+</p>
+
+
+<!-- 
+  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 and scripts will need to be adjusted to provide user
+credentials for shutting down a network server that runs with user
+authentication.
+</p>
+
+
+</blockquote>
 <hr>
 <h3>
-<a name="Note for DERBY-2610"></a>Note for DERBY-2610</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-2386"></a>Note for DERBY-2386</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-2296"></a>Note for DERBY-2296</h3>
+<a name="Note for DERBY-3460"></a>Note for DERBY-3460</h3>
 <blockquote>
-<!--
+
+<!-- 
   SUMMARIZE THE ISSUE. This is a one line summary of the issue.
 
   For instance:
@@ -765,13 +670,15 @@
   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>
+The two following reserved keywords are introduced: <code>NONE</code>
+and <code>CURRENT_ROLE</code>.</p>
+
 
-<!--
+<!-- 
   DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
 
   For instance:
@@ -783,55 +690,115 @@
   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>
+If an application attempts to use one of these keywords, a syntax
+error (SQL state 42X01) is raised.
 
-<blockquote>
+<!-- 
+  DESCRIBE WHY THE CHANGE WAS MADE.
 
-<ul>
+  For instance:
+
+  The previous behavior violated the JDBC standard. The new behavior
+  is correct.
+-->
+
+<!-- 
+  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
+
+  For instance:
+
+  Applications which open two InputStreams on the ResultSet column now
+  fail.
+-->
 
-<li>setCreateDatabase (String) </li>
+<h4>Incompatibilities with Previous Release</h4>
+These two keywords were not previously reserved by Derby, and
+applications that rely on using them will break.
 
-<li>getCreateDatabase() </li>
+<h4>Rationale for Change</h4>
+This change complies with the SQL standard and prepares
+Derby for supporting SQL roles in a future release.
 
-<li>setShutdownDatabase (String) </li>
 
-<li>getShutdownDatabase() </li>
+<!-- 
+  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
+  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
 
-</ul>
+  For instance:
 
+  Users must recode applications which open multiple streams on the same column.
+-->
+
+<h4>Application Changes Required</h4>
+Such user identifiers must be renamed so that they are not reserved
+keywords. See the Derby Reference Manual section titled "SQL Reserved Words".
 </blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-3301"></a>Note for DERBY-3301</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 EXIST, ANY or IN clauses now return correct 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>
-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.
+In the previous release, applications that executed SQL statements 
+containing nested EXISTS, ANY or IN clauses could see fewer rows
+than those satisfying the query. In particular, rows that had the
+same value for one of the selected columns as another row might not
+have been returned.
 </p>
-<!--
+
+
+<!-- 
   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>
+None.
 </p>
-<!--
+
+<!-- 
   DESCRIBE WHY THE CHANGE WAS MADE.
 
   For instance:
@@ -840,24 +807,16 @@
   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.
+The previous behavior violated the ANSI SQL 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.
 
@@ -866,30 +825,21 @@
   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>
+<h4>Application Changes Required</h4>
 
+<p>
+Typically none, but applications must handle that the correct results are now returned.
 </p>
 
+
 </blockquote>
 <hr>
 <h3>
-<a name="Note for DERBY-2108"></a>Note for DERBY-2108</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-1852"></a>Note for DERBY-1852</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-1828"></a>Note for DERBY-1828</h3>
+<a name="Note for DERBY-3026"></a>Note for DERBY-3026</h3>
 <blockquote>
 
-<!--
+<!-- 
   SUMMARIZE THE ISSUE. This is a one line summary of the issue.
 
   For instance:
@@ -901,11 +851,11 @@
 <h4>Summary of Change</h4>
 
 <p>
-Most authorization failures have new error codes.
+The <code>frameworks</code> directory (and its contents) has been removed.
 </p>
 
 
-<!--
+<!-- 
   DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
 
   For instance:
@@ -921,16 +871,14 @@
 <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>
 
+</p>
+Users and applications that rely on any of the scripts or HTML files in the 
+<code>frameworks</code> directory (which has been deprecated since the 10.2.1.6 
+release) or any of its subdirectories will no longer be able to find those files 
+in the same location.
 
-<!--
+<!-- 
   OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
 
   For instance:
@@ -939,15 +887,15 @@
   fail.
 -->
 
-
 <h4>Incompatibilities with Previous Release</h4>
 
 <p>
-Applications that are dependant on authorization error codes may fail.
+Applications or commands referencing files in the <code>frameworks</code> 
+directory will fail.
 </p>
 
 
-<!--
+<!-- 
   DESCRIBE WHY THE CHANGE WAS MADE.
 
   For instance:
@@ -960,12 +908,25 @@
 <h4>Rationale for Change</h4>
 
 <p>
-The old error codes violated the SQL standard. The new error codes
-are correct.
+In the 10.2.1.6 release, new and improved scripts were added in a new <code>bin</code> 
+directory, intended to replace the scripts in the <code>frameworks</code> 
+directory. The new scripts follow Apache conventions, and all scripts are 
+located in a single directory, making them easier to find. Removing the old and 
+deprecated scripts and the <code>frameworks</code> directory itself will 
+eliminate a potential source of confusion and annoyance among users.</p>
+
+<p>
+The <code>frameworks</code> directory has been deprecated since the 10.2.1.6 
+release, and has not been maintained since then. The 10.2.1.6 release notes 
+announced the deprecation of the scripts in the <code>frameworks</code> 
+directory, and an additional file (<code>frameworks.DEPRECATED.txt</code>) was 
+added in the top-level directory of the 10.3.1.4 release, with the purpose of 
+alerting users about this change. A warning message was also added to the 
+scripts in the <code>frameworks</code> directory at the same time.
 </p>
 
 
-<!--
+<!-- 
   OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
   OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
 
@@ -978,8 +939,9 @@
 <h4>Application Changes Required</h4>
 
 <p>
-Applications that are dependant on authorization error codes must be
-recoded to expect the new codes.
+All references to the <code>frameworks</code> directory or its contents must be 
+updated. The scripts in the <code>bin</code> directory may be used instead of 
+the old scripts.
 </p>
 
 
@@ -987,14 +949,10 @@
 </blockquote>
 <hr>
 <h3>
-<a name="Note for DERBY-1501"></a>Note for DERBY-1501</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-1484"></a>Note for DERBY-1484</h3>
+<a name="Note for DERBY-3013"></a>Note for DERBY-3013</h3>
 <blockquote>
 
-<!--
+<!-- 
   SUMMARIZE THE ISSUE. This is a one line summary of the issue.
 
   For instance:
@@ -1006,11 +964,13 @@
 <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 and getExportedKeys.
+The column default value can now also be specified as CURRENT_USER or
+SESSION_USER. 
+
 </p>
 
 
-<!--
+<!-- 
   DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
 
   For instance:
@@ -1026,11 +986,11 @@
 <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. Furthermore, Derby now raises an SQLException if the table name is null.
+None
 </p>
 
 
-<!--
+<!-- 
   OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
 
   For instance:
@@ -1043,11 +1003,11 @@
 <h4>Incompatibilities with Previous Release</h4>
 
 <p>
-Calls to the specified methods now fail if the table name parameter is null (SQLException is thrown) or is a pattern (no information is returned).
+None
 </p>
 
 
-<!--
+<!-- 
   DESCRIBE WHY THE CHANGE WAS MADE.
 
   For instance:
@@ -1060,11 +1020,11 @@
 <h4>Rationale for Change</h4>
 
 <p>
-The previous behavior violated the JDBC standard. The new behavior is correct.
+Extend Derby's support for standard SQL constructions.
 </p>
 
 
-<!--
+<!-- 
   OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
   OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
 
@@ -1077,7 +1037,7 @@
 <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.
+None.
 </p>
 
 
@@ -1085,13 +1045,10 @@
 </blockquote>
 <hr>
 <h3>
-<a name="Note for DERBY-729"></a>Note for DERBY-729</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-415"></a>Note for DERBY-415</h3>
+<a name="Note for DERBY-2892"></a>Note for DERBY-2892</h3>
 <blockquote>
-<!--
+
+<!-- 
   SUMMARIZE THE ISSUE. This is a one line summary of the issue.
 
   For instance:
@@ -1099,13 +1056,16 @@
   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.
+  DERBY-2892 fixes the bug: "Closing a resultset after retrieving a large &gt; 32665 bytes value with Network Server does not release locks." The fix  changes the JDBC retrieval of BLOB/CLOB columns release locks and the lob locator after calls to ResultSet.getString(), ResultSet.getCharacterStream(), ResultSet.getBytes() or ResultSet.getBinaryStream().  Previously locks would remain held after these calls.  Note: Locks will still be held for calls to ResultSet.getClob() or ResultSet.getBlob().  The user must call free() or commit or rollback the transation to release these locks.
+
 </p>
 
-<!--
+
+<!-- 
   DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
 
   For instance:
@@ -1117,15 +1077,17 @@
   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.
+
+  Users will no longer see locks being held for calls to ResultSet.getString(), ResultSet.getCharacterStream(), ResultSet.getBytes() or ResultSet.getBinaryStream(). 
+
 </p>
 
-<!--
+
+<!-- 
   OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
 
   For instance:
@@ -1134,13 +1096,15 @@
   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.
+As part of the implementation of this change, BLOB/CLOB columns can be retrieved only once through JDBC, for each row. For example, if the user calls ResultSet.getString() on a BLOB or CLOB column, they cannot make a subsequent call to ResultSet.getCharacterStream()  for the same column on the same row. An Exception will be thrown if this is attempted. 
 </p>
-<!--
+
+
+<!-- 
   DESCRIBE WHY THE CHANGE WAS MADE.
 
   For instance:
@@ -1149,13 +1113,15 @@
   is correct.
 -->
 
+
 <h4>Rationale for Change</h4>
 
 <p>
-The behavior has changed in order to eliminate a confusing diagnostic
-            message.
+In order to ensure the proper locking behavior, the change to throw an exception when a BLOB/CLOB column is retrieved more than once for a row was required. 
 </p>
-<!--
+
+
+<!-- 
   OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
   OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
 
@@ -1164,19 +1130,21 @@
   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.
+Users should retrieve the field only once and save the value for reuse, rather than making multiple calls to ResultSet.getXXXX methods.
 </p>
 
+
+
 </blockquote>
 <hr>
 <h3>
-<a name="Note for DERBY-119"></a>Note for DERBY-119</h3>
+<a name="Note for DERBY-2351"></a>Note for DERBY-2351</h3>
 <blockquote>
-<!--
+<!-- 
   SUMMARIZE THE ISSUE. This is a one line summary of the issue.
 
   For instance:
@@ -1186,12 +1154,13 @@
 
 <h4>Summary of Change</h4>
 
-<p>
-The ALTER TABLE statement now includes the additional ability to alter
-the NULL / NOT NULL constraint on a column in a table.
-</p>
-
-<!--
+<p>An ORDER BY clause of a DISTINCT query which specifies to order by a
+column which was not in the DISTINCT list is now rejected, because the
+intent of the query is ambiguous. Previously, Derby instead produced
+non-distinct results.
+Also, an ORDER BY clause which specifies a table-name-qualified column alias
+is now rejected as invalid, where previously it was accepted.</p>
+<!-- 
   DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
 
   For instance:
@@ -1205,30 +1174,188 @@
 
 <h4>Symptoms Seen by Applications Affected by Change</h4>
 
+<h5>New rules for DISTINCT and ORDER BY</h5>
+
+<p>
+Applications which specify certain combinations of SELECT DISTINCT with
+ORDER BY will now receive an error message, whereas formerly such applications
+received non-distinct results.</p>
+
+<p>As an example, take the following: </p>
+
+<p style="font-family: monospace;">
+create table person (name varchar(10), age int);<br>
+insert into person values ('John', 10);<br>
+insert into person values ('John', 30);<br>
+insert into person values ('Mary', 20);<br>
+
+<br>
+SELECT DISTINCT name FROM person ORDER BY age;<br>
+
+</p>
+
+<p>The query above is now rejected, with the error message:</p>
+
+<blockquote>
+	ERROR 42879: The ORDER BY clause may not contain column 'AGE',
+	since the query specifies DISTINCT and that column does not appear
+	in the query result.
+</blockquote>
+
+<p>If the AGE column is included in the DISTINCT list in the above query,
+there is no ambiguity</p>
+
+<h5>New column alias rules</h5>
+
 <p>
-The syntax is:
+Applications which specify a column alias for a column in the SELECT
+statement, and which specify an ORDER BY clause which specifies that
+column alias qualified by the table name, will now receive an error
+indicating that the ORDER BY clause is invalid.
 </p>
 
+<p>As an example, take the following: </p>
+
+<p style="font-family: monospace;">  create table t1 (i int, j int);<br>
+  select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.idcolumn1, t1.idcolumn2;</p>
+
+<p>This query is now rejected, as there is no column named 'idcolumn1'
+in table 't1'. The error message is:</p>
 
 <blockquote>
-<pre>
-ALTER TABLE table ALTER [COLUMN] column [NOT] NULL
-</pre>
+	ERROR 42X04: Column 'T1.IDCOLUMN1' is either not in any table in
+	the FROM list or appears within a join specification and is outside
+	the scope of the join specification or appears in a HAVING clause
+	and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE 
+	statement then 'T1.IDCOLUMN1' is not a column in the target table.
+</blockquote>
+
+<p>Valid forms of the query above are:</p>
+
+<p style="font-family: monospace;">
+  select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by idcolumn1, idcolumn2;</p>
+
+<p>or</p>
+
+<p style="font-family: monospace;">
+  select t1.id as idcolumn1, t1.id as idcolumn2 from t1 order by t1.id, t1.id;</p>
+
+
+<h4>Rationale for Change</h4>
+
+<p>When the query ambiguously specifies both DISTINCT and ORDER BY, Derby
+was unsure whether to return the rows properly ordered, but non-distinct,
+or to return a distinct set of rows, but in an unknown order. Since no
+clear resolution of the ambiguity could be found, we chose instead to
+reject the query.</p>
+
+<p>The rules for resolving column references in ORDER BY clauses have been
+enhanced to consider column aliases and column names more fully.
+Derby now uses different resolution rules depending on whether
+the ORDER BY column reference is table.column, or just column:
+<ul>
+	
+<li>if the table name is provided, we match against the
+	underlying table name, and don't consider any aliases</li>
+	
+<li>if the table name is NOT provided, we first match against
+	the alias name, if present, and if no alias name matches
+	then we match against the underlying source column name. </li>
+
+</ul>
+
+</p>
+<!-- 
+  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
+  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
+
+  For instance:
+
+  Users must recode applications which open multiple streams on the same column.
+-->
+
+<h4>Application Changes Required</h4>
+
+<p>
+A query which specifies ordering by a non-distinct column should instead
+include the ORDER BY column in the DISTINCT list, to resolve the ambiguity
+about which values of that column should be used to distinctly identify
+the resulting rows.</p>
+
+<p>
+A query which specifies table-name.alias-name should be rewritten to specify
+either simply alias-name, or table-name.column-name.
+</p>
+
 </blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2065"></a>Note for DERBY-2065</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>
+Error code changed for embedded connection when  a connection with an open transaction is attempted 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>
-You cannot remove the NOT NULL constraint if the column is used
-in a PRIMARY KEY or UNIQUE constraint.
+In the previous release, calling Connection.close() on a connection
+with an open transaction raised an error with error code 25001 with
+the client driver, whereas the embedded driver raised error code
+25000. The embedded driver has now been changed to raise the same
+error code as the client driver, i.e. 25001, as specified by the SQL
+standard.
 </p>
 
 
+<!-- 
+  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 addition, you cannot add the NOT NULL constraint if there are existing NULL
-values for the column in the table.
+Embedded applications that are dependent on the error code
+<i>ever</i> being "25000" could start failing.
+
+Embedded applications that are dependent on the error code
+<i>never</i> being "25001" could start failing.
 </p>
 
-<!--
+
+<!-- 
   DESCRIBE WHY THE CHANGE WAS MADE.
 
   For instance:
@@ -1237,36 +1364,65 @@
   is correct.
 -->
 
+
 <h4>Rationale for Change</h4>
 
 <p>
-Users have requested this feature and other databases support it.
+Harmonize error codes raised by the client and embedded drivers,
+thereby also making the embedded driver compatible with the SQL
+standard.
+</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 dependent on the error code must be changed to expect the new code.
 </p>
 
+
+
 </blockquote>
 </blockquote>
 <h2>
 <a name="Build Environment"></a>Build Environment</h2>
 <blockquote>
-<p>Derby release 10.3.0.0 was built using the following environment:</p>
+<p>Derby release 10.4.1.0 was built using the following environment:</p>
 <ul>
 <li>
-<b>Branch</b> - Source code came from the 10.3 branch.</li>
+<b>Branch</b> - Source code came from the 10.4 branch.</li>
 <li>
-<b>Machine</b> - Cygwin on Microsoft Windows XP Professional Version 2002 Service Pack 2.</li>
+<b>Machine</b> - SunOS khepri32 5.10 Generic_127112-01 i86pc i386 i86pc</li>
 <li>
-<b>Ant</b> - Apache Ant version 1.6.5 compiled on June 2 2005.</li>
+<b>Ant</b> - Apache Ant version 1.7.0 compiled on December 13 2006</li>
 <li>
-<b>JDK 1.4</b> - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03).</li>
+<b>JDK 1.4</b> - java version "1.4.2_05"
+Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
+Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
+</li>
 <li>
-<b>Java 6</b> -  Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-b105).</li>
+<b>Java 6</b> - java version "1.6.0_04"
+Java(TM) SE Runtime Environment (build 1.6.0_04-b06)
+Java HotSpot(TM) Server VM (build 10.0-b18, mixed mode)
+</li>
 <li>
-<b>OSGi</b> - The osgi.jar was used to build org.apache.derby.osgi.EmbeddedActivator.</li>
+<b>OSGi</b> - The felix.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>
+<b>Compiler</b> - 
+The 1.6.0_04 javac was used to compile all classes.
+  </li>
 <li>
-<b>JSR 169</b> - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).</li>
+<b>JSR 169</b> - J2ME support was built using java.sun.com/j2me (cdc-1_1-fr-ri, jdbc_cdc1.0).</li>
 </ul>
 </blockquote>
 </body>



Mime
View raw message