db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r538929 [1/2] - in /db/derby/code/trunk: RELEASE-NOTES.html java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java releaseSummary.xml tools/release/build.xml tools/release/templates/releaseSummaryTemplate.xml
Date Thu, 17 May 2007 14:05:19 GMT
Author: rhillegas
Date: Thu May 17 07:05:18 2007
New Revision: 538929

URL: http://svn.apache.org/viewvc?view=rev&rev=538929
Log:
DERBY-2570: Check in first rev of a tool for generating the Release Notes.

Added:
    db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java   (with props)
    db/derby/code/trunk/releaseSummary.xml   (with props)
    db/derby/code/trunk/tools/release/templates/releaseSummaryTemplate.xml   (with props)
Modified:
    db/derby/code/trunk/RELEASE-NOTES.html
    db/derby/code/trunk/tools/release/build.xml

Modified: db/derby/code/trunk/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/RELEASE-NOTES.html?view=diff&rev=538929&r1=538928&r2=538929
==============================================================================
--- db/derby/code/trunk/RELEASE-NOTES.html (original)
+++ db/derby/code/trunk/RELEASE-NOTES.html Thu May 17 07:05:18 2007
@@ -1,253 +1,1208 @@
 <html>
-<title>Release Notes for Derby a?.b?.c?.d?</title>
+<title>Release Notes for Derby 10.3.0.0</title>
 <body>
-<h1>Release Notes for Derby a?.b?.c?.d?</h1>
+<h1>
+<a name="Release Notes for Derby 10.3.0.0"></a>Release Notes for Derby 10.3.0.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>
+</blockquote>
+<ul>
+<li>
+<a href="#Overview">Overview</a>
+</li>
+<li>
+<a href="#New Features">New Features</a>
+</li>
+<li>
+<a href="#Bug Fixes">Bug Fixes</a>
+</li>
+<li>
+<a href="#Issues">Issues</a>
+</li>
+<li>
+<a href="#Build Environment">Build Environment</a>
+</li>
+</ul>
+<h2>
+<a name="Overview"></a>Overview</h2>
+<blockquote>
+
 
 <p>
-This is a template for composing release notes. Please customize this
-for the release you are building.
+Derby is a pure Java relational database engine using standard SQL and
+JDBC as its APIs.
+</p>
+
+
+<p>
+Derby functionality includes:
 </p>
 
+
 <ul>
-<li><a href="#Overview">Overview</a></li>
-<li><a href="#New Features">New Features</a></li>
-<li><a href="#Bug Fixes">Bug Fixes</a></li>
-<li><a href="#Issues">Issues</a></li>
-<li><a href="#Build Environment">Build Environment</a></li>
+
+<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>
 
-<h2><a name="Overview"></a>Overview</h2>
+
+</blockquote>
+<h2>
+<a name="New Features"></a>New Features</h2>
+<blockquote>
+
 
 <p>
-These notes describe the difference between Derby release a?.b?.c?.d?
-and the preceding release e?.f?.g?.h?.
+This is a bug-fix release. No new features were added.
 </p>
 
+
+</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>
+<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-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-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-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-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-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-2529">DERBY-2529</a></td><td>Client PreparedStatement/CallableStatement implementations need to use locators</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-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-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-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-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-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-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-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-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-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-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-2356">DERBY-2356</a></td><td>Make SSL server authentication optional</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-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-2296">DERBY-2296</a></td><td>getProperties method deprecated on ClientDataSource</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-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-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-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-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-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-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-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-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-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-2163">DERBY-2163</a></td><td>Localization jar files incorrectly contain a service extension entry for java.sql.Driver</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-2143">DERBY-2143</a></td><td>Updated localized messages for Derby 10.2</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-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-2131">DERBY-2131</a></td><td>External DTD files are accessed without a privileged block when Derby parses XML values that reference such DTDs.</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-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-2110">DERBY-2110</a></td><td>message typos: error 42X52, XJ100.S, XBCXU/XBCXV...</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-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-2084">DERBY-2084</a></td><td>getTransactionIsolation() in network client should not activate a transaction</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-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-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-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-2030">DERBY-2030</a></td><td>'set schema sys' followed by 'show tables' does not show tables in sys schema</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-2014">DERBY-2014</a></td><td>NullPointerException with NULLIF in GROUP BY clause</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2008">DERBY-2008</a></td><td>NullPointerException with LTRIM, RTRIM and 2-argument SUBSTR() call in GROUP BY clause.</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-1991">DERBY-1991</a></td><td>Misleading stack traces for exceptions raised by the JDBC 4.0 embedded driver</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1986">DERBY-1986</a></td><td>Add crypto notice for users and provide info for ASF exports page</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1967">DERBY-1967</a></td><td>UNION (ALL) contraint violation problem</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-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-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-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-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-1894">DERBY-1894</a></td><td>SQLSTATE 42X10 occurs when qualifying a column with a synonym in ORDER BY clause</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1891">DERBY-1891</a></td><td>error 58009.C.19  refers to non-existent codepoint secktn - needs correcting</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-1866">DERBY-1866</a></td><td>Assert failure in sane mode for queries that used to work in 10.1.2.1</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1862">DERBY-1862</a></td><td>Simple hash improves performance</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-1858">DERBY-1858</a></td><td>A schema can be dropped by a non-schema owner in SQL authorization mode</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1856">DERBY-1856</a></td><td>Multiple communication failures when starting server with derby.drda.timeSlice</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1854">DERBY-1854</a></td><td>SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a primary key and a foreign key</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-1836">DERBY-1836</a></td><td>Message XJ215 should be updated to reflect that Clob/Blob are referring to method calls.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1833">DERBY-1833</a></td><td>Remove messages made unused by implementation of DERBY-690 and DERBY-775</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1811">DERBY-1811</a></td><td>Embedded ResultSet.getTimestamp on a TIME column returns a java.sql.Timestamp with a date portion that can be incorrect.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1809">DERBY-1809</a></td><td>Built-in functions not working in views.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1800">DERBY-1800</a></td><td>testSetBinaryStreamLengthLessOnBlobTooLong fails with 'Unexpected SQL state. expected:&lt;22001&gt; but was:&lt;58009&gt;'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1787">DERBY-1787</a></td><td>The database owner is incorrectly referred to as dba in the code comments that were checked in Derby 10.2 for grant revoke work. We should clean this up at some point.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1786">DERBY-1786</a></td><td>a crash during re-encryption of an existing  database with lot of tables can make database unrecoverable on a  next boot.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1784">DERBY-1784</a></td><td>When qualifying a column name with its synonym name in the select list, Derby throws SQLSTATE 42X04.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1783">DERBY-1783</a></td><td>Logical error in code for determining mode for opening of log files</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1776">DERBY-1776</a></td><td>ERROR 42Z72: XML syntax error; missing keyword(s): 'AS'. - Misleading text</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1775">DERBY-1775</a></td><td>Error 2200M is defined in the SQL standard as 'invalid XML document' and can be used in multiple situations, not just XMLPARSE</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1772">DERBY-1772</a></td><td>Error 42Z78 "Failed to locate 'Xalan' API  classes" should not have sqlstate class '42'</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1770">DERBY-1770</a></td><td>Make "mode db2sql" an optional phrase in the "create trigger" statement</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1756">DERBY-1756</a></td><td>Revert change in client that defaults the secmec to eusridpwd.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1739">DERBY-1739</a></td><td>Index column names in CatalogRowFactory implementations are not required</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1732">DERBY-1732</a></td><td>The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store protocol violation errors</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1729">DERBY-1729</a></td><td>Invoking Java stored procedure that contains GRANT or REVOKE statement with CONTAINS SQL should fail.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1724">DERBY-1724</a></td><td>Executing grant statement within a transaction leads to a NPE later when the db owner attempts to update a table</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1718">DERBY-1718</a></td><td>creating an after insert trigger with trigger action involving  xml datatype throws  java.io.NottSerializableException</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1716">DERBY-1716</a></td><td>Revoking select privilege from a user times out when that user still have a cursor open.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1714">DERBY-1714</a></td><td>huge single insert statements fail with JVM error due to size of generated method</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1708">DERBY-1708</a></td><td>Unprivileged user can perform lock table statement on a table which he/she does not have any access rights</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1707">DERBY-1707</a></td><td>Specifying an incorrect optimizer property (constraint=null) gives NullPointerException</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1706">DERBY-1706</a></td><td>NullPointerException occurs when trying to create a table in schema SESSION</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1700">DERBY-1700</a></td><td>Remove passing of closeCleanup method to every ResultSet type since only the top ResultSet requires it.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1693">DERBY-1693</a></td><td>Out of Memory Error with derby.language.logStatementText=true</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1686">DERBY-1686</a></td><td>Grant/Revoke: Attempt to GRANT access to another user on a VIEW, created by the current user with only SELECT privilege on the base table does not fail</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1681">DERBY-1681</a></td><td>Regression (wrong results): Join predicate can be ignored for left-most child in a chain of nested unions.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1675">DERBY-1675</a></td><td>Network Server should not send to client that it supports EUSRIDPWD when running against Sun JVM</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1645">DERBY-1645</a></td><td>ALTER TABLE ... SET INCREMENT BY X... Turns off the "Generated By Default" identity column constraint</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-1641">DERBY-1641</a></td><td>Conglomerate requested does not exist after syscs_import_table with FK</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1633">DERBY-1633</a></td><td>Regression: The fields of views are not being calculated properly since 10.1.2.4</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-1609">DERBY-1609</a></td><td>Add a runScript method to ij that takes a script as an InputStream and returns the output to a stream.</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-1583">DERBY-1583</a></td><td>With grant revoke enabled, defining a trigger whose actions updates a table (from different schema) results in NPE</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1559">DERBY-1559</a></td><td>when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1547">DERBY-1547</a></td><td>Add svn version  number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion()  to improve supportability</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1538">DERBY-1538</a></td><td>Unexpected behavior on self privilege revocation</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-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-1495">DERBY-1495</a></td><td>Attempt to modify an identity column error after resetting identity column</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-1491">DERBY-1491</a></td><td>Provide ALTER TABLE functionality to change a column's default value</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-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-1326">DERBY-1326</a></td><td>Network server may abandon sessions when Derby system is shutdown and this causes intermittent hangs in the client</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1315">DERBY-1315</a></td><td>Statement optimization/compilation fails with OutOfMemoryException in largeCodeGen test  with embedded and framework DerbyNetClient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1304">DERBY-1304</a></td><td>DROP view does not always completely remove view</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-1231">DERBY-1231</a></td><td>LIKE does not match empty strings when used with a prepared statement</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1204">DERBY-1204</a></td><td>CREATE TRIGGER with an INSERT action statement with multiple rows and a referenced column throws a StringIndexOutOfBoundsException</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-1130">DERBY-1130</a></td><td>Client should not allow databaseName to be set with setConnectionAttributes</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1089">DERBY-1089</a></td><td>Derby fails inserting a join into a table with a generated column</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1072">DERBY-1072</a></td><td>Misleading/wrong error message while dropping a view</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-912">DERBY-912</a></td><td>OutOfMemory error on continuous execution of SQL statement</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-766">DERBY-766</a></td><td>Improve code generation to handle 5000 unions in a select the  union test  in largeCodeGen</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-737">DERBY-737</a></td><td>SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist</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-688">DERBY-688</a></td><td>Enhancements to XML functionality to move toward XPath/XQuery support...</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-638">DERBY-638</a></td><td>Network driver setTransactionIsolation() causes a commit, but does not complete it locally</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-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-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-176">DERBY-176</a></td><td>Derby throws ERROR XBCM1: Java linkage error thrown during load of generated class org.apache.derby.exe.aced07c066x0102xca87x3319x00004aa5686e1 during execution of large query</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-119">DERBY-119</a></td><td>Add ALTER TABLE option to change column from NULL to NOT NULL</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.0.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
+<ul>
+<li>
+<a href="#Note for DERBY-2430">Note for DERBY-2430: ???</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-2196">Note for DERBY-2196: 
+Security enhancements may prevent the Network Server from booting.
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-2108">Note for DERBY-2108: ???</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-1491">Note for DERBY-1491: ???</a>
+</li>
+<li>
+<a href="#Note for DERBY-1484">Note for DERBY-1484: 
+Tablenames can no longer be null in calls to DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys and getExportedKeys.
+</a>
+</li>
+<li>
+<a href="#Note for DERBY-1130">Note for DERBY-1130: ???</a>
+</li>
+<li>
+<a href="#Note for DERBY-729">Note for DERBY-729: ???</a>
+</li>
+<li>
+<a href="#Note for DERBY-688">Note for DERBY-688: ???</a>
+</li>
+<li>
+<a href="#Note for DERBY-415">Note for DERBY-415: ???</a>
+</li>
+<li>
+<a href="#Note for DERBY-119">Note for DERBY-119: ???</a>
+</li>
+</ul>
+<hr>
+<h3>
+<a name="Note for DERBY-2430"></a>Note for DERBY-2430</h3>
+<blockquote></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>
-Derby is a pure Java relational database engine using standard SQL and
-JDBC as its APIs.
-a?.b?.c?.d? is a bug fix?/feature? release.
+ClientDataSource now supports the createDatabase and shutdownDatabase properties.
 </p>
 
-<p>
-The following improvements distinguish a?.b?.c?.d? from e?.f?.g?.h?:
+<!-- 
+  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>Blah blah blah</li>
-<li>Blah blah blah</li>
+
+<li>setCreateDatabase (String) </li>
+
+<li>getCreateDatabase() </li>
+
+<li>setShutdownDatabase (String) </li>
+
+<li>getShutdownDatabase() </li>
+
 </ul>
 
+</blockquote>
+
+
 <p>
-For a comprehensive list of changes, consult the lists of
-<a href="#New Features">new features</a>
-and
-<a href="#Bug Fixes">bug fixes</a>
-below.
+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.
 
-<p>
-a?.b?.c?.d? functionality includes:
+  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.
 
-<ul>
-<li>Embedded engine with JDBC driver</li>
-<li>Network Server</li>
-<li>Network client JDBC driver</li>
-<li>Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)</li>
-</ul>
+  For instance:
+
+  The previous behavior violated the JDBC standard. The new behavior
+  is correct.
+-->
+
+<h4>Rationale for Change</h4>
 
 <p>
-SQL support:
+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.
 
-<ul>
-<li>Schemas, tables, temporary tables, views, triggers, indexes, savepoints</li>
-<li>Java procedures and functions</li>
-<li>Standard datatypes including BLOB and CLOB</li>
-<li>Sub-queries and joins</li>
-<li>Primary key, foreign key, unique and check constraints</li>
-<li>Referential actions</li>
-</ul>
+  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-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>
-Other features:
+Security enhancements may prevent the Network Server from booting.
 </p>
 
-<ul>
-<li>Full ACID transaction support with all four isolation levels</li>
-<li>Row and table level locking</li>
-<li>Configurable authentication including LDAP support</li>
-<li>Import/Export</li>
-<li>On-line backup and recovery support</li>
-<li>Optional on-disk encryption</li>
-<li>Platform independent database format</li>
-<li>Full support for Java 2 Security Manager</li>
-</ul>
+
+<!-- 
+  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>
-JDK/JDBC support:
+The Network Server may fail to boot. The user sees the following
+      error message:
 </p>
 
-<ul>
-<li>JDK 1.3, 1.4, 1.5, and J2ME J2ME/CDC/Foundation Profile</li>
-<li>JSR-169, JDBC 2.1, and JDBC 3.0 support</li>
-</ul>
 
+<blockquote>
+<i>
+Network Server startup failed. User authentication should be enabled
+          before the Network Server installs a security
+          manager. Please either set the
+          'derby.connection.requireAuthentication' system property to
+          true or run the network server with the '-noSecurityManager'
+          option.
+</i>
+</blockquote>
+
+<!-- 
+  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
 
-<h2><a name="New Features"></a>New Features</h2>
+  For instance:
+
+  Applications which open two InputStreams on the ResultSet column now
+  fail.
+-->
+
+
+<h4>Incompatibilities with Previous Release</h4>
 
 <p>
-List the new features introduced by this release. These are features
-which appear in Derby a?.b?.c?.d? but not in the preceding release e?.f?.g?.h?.
+In previous releases, the Network Server booted without requiring user
+      authentication and without installing a default security
+      manager. Now, the Network Server
+      refuses to boot if authentication is not enabled.
 </p>
 
-<TABLE border="2">
-  <TBODY>
-    <TR>
-      <TD><b>Master JIRA</b></TD>
-      <TD><b>New Feature</b></TD>
-    </TR>
-    <TR>
-      <TD><a href="http://issues.apache.org/jira/browse/DERBY-464">DERBY-464</a></TD>
-      <TD>Introduce GRANT/REVOKE functionality.</TD>
-    </TR>
 
-  </TBODY>
-</TABLE>
+<!-- 
+  DESCRIBE WHY THE CHANGE WAS MADE.
+
+  For instance:
+
+  The previous behavior violated the JDBC standard. The new behavior
+  is correct.
+-->
+
 
-<h2><a name="Bug Fixes"></a>Bug Fixes</h2>
+<h4>Rationale for Change</h4>
 
 <p>
-List the bugs fixed by this release. These are bug fixes which turn up
-in Derby a?.b?.c?.d? but not in the preceding release e?.f?.g?.h?.
+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. In doing so, the Network Server
+      expects user authentication to be enabled so that privileged
+      actions can be restricted to authorized users.
 </p>
 
-<TABLE border="2">
-  <TBODY>
-    <TR>
-      <TD><b>Issue Id</b></TD>
-      <TD><b>Description</b></TD>
-    </TR>
-    <TR>
-      <TD><a href="http://issues.apache.org/jira/browse/DERBY-23">DERBY-23</a></TD>
-      <TD> just booting jdbc driver and shutting down seem to leak memory</TD>
-    </TR>
-  </TBODY>
-</TABLE>
 
-<h2><a name="Issues"></a>Issues</h2>
+<!-- 
+  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>
-List the outstanding issues and their workarounds. Use the following
-template.
+As the error message explains, you need to do one of the following:
 </p>
 
+
 <ul>
-<li><a href="#First Problem Short Name">First Problem Short Name</a></li>
-<li><a href="#Second Problem Short Name">Second Problem Short Name</a></li>
+
+<li>
+<b>Authenticate</b> - Enable user authentication for your
+        client/server configuration.</li>
+
+<li>
+<b>Disable</b> - Disable the security checks by setting the
+        '-noSecurityManager' option in your server startup script.</li>
+
 </ul>
 
-<hr/>
-<blockquote>
-<a name="First Problem Short Name"></a>
-<h3>Problem</h3>
-<p>
-Blah blah blah blah.
-</p>
-</blockquote>
 
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-2108"></a>Note for DERBY-2108</h3>
+<blockquote></blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1828"></a>Note for DERBY-1828</h3>
 <blockquote>
-<h3>Symptoms</h3>
+
+<!-- 
+  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>
-Blah blah blah blah.
+Most authorization failures have new error codes.
 </p>
-</blockquote>
 
-<blockquote>
-<h3>Cause</h3>
+
+<!-- 
+  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>
-Blah blah blah blah.
+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>
-</blockquote>
 
-<blockquote>
-<h3>Solution</h3>
+
+<!-- 
+  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 blah.
+Applications that are dependant on authorization error codes may fail.
 </p>
-</blockquote>
 
-<blockquote>
-<h3>Workaround</h3>
+
+<!-- 
+  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>
-Blah blah blah blah.
+The old error codes violated the SQL standard. The new error codes
+are correct.
 </p>
-</blockquote>
 
 
+<!-- 
+  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>
 
-<hr/>
-<blockquote>
-<a name="Second Problem Short Name"></a>
-<h3>Problem</h3>
 <p>
-Blah blah blah blah.
+Applications that are dependant on authorization error codes must be
+recoded to expect the new codes.
 </p>
-</blockquote>
 
+
+
+</blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1491"></a>Note for DERBY-1491</h3>
+<blockquote></blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-1484"></a>Note for DERBY-1484</h3>
 <blockquote>
-<h3>Symptoms</h3>
+
+<!-- 
+  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>
-Blah blah blah blah.
+Tablenames can no longer be null in calls to DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys and getExportedKeys.
 </p>
-</blockquote>
 
-<blockquote>
-<h3>Cause</h3>
+
+<!-- 
+  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>
-Blah blah blah blah.
+In the previous release, the methods returned information on all tables in the schema if the table name parameter was null. Derby now raises an SQLException if the tablename is null.
 </p>
-</blockquote>
 
-<blockquote>
-<h3>Solution</h3>
+
+<!-- 
+  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 blah.
+Calls to the specified methods now fail if the tablename parameter is null.
 </p>
-</blockquote>
 
-<blockquote>
-<h3>Workaround</h3>
+
+<!-- 
+  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>
-Blah blah blah blah.
+The previous behavior violated the JDBC standard. The new behavior is correct.
 </p>
-</blockquote>
 
-<h2><a name="Build Environment"></a>Build Environment</h2>
+
+<!-- 
+  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>
-Derby release a?.b?.c?.d? was built using the following environment:
+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-1130"></a>Note for DERBY-1130</h3>
+<blockquote></blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-729"></a>Note for DERBY-729</h3>
+<blockquote></blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-688"></a>Note for DERBY-688</h3>
+<blockquote></blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-415"></a>Note for DERBY-415</h3>
+<blockquote></blockquote>
+<hr>
+<h3>
+<a name="Note for DERBY-119"></a>Note for DERBY-119</h3>
+<blockquote></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>
 <ul>
-<li><b>Branch</b> - Source code came from the a?.b? branch.</li>
-<li><b>Machine</b> - Describe here the machine used for the
-build. E.g.: Cygwin on Microsoft Windows XP Professional Version 2002 Service
-Pack 2.</li>
-<li><b>Ant</b> - Attach here the output of "ant -version".</li>
-<li><b>JDK 1.4</b> - Attach here the output of "java -version" run
-from your 1.4 installation.</li>
-<li><b>JDK 1.3</b> - Attach here the output of "java -version" run
-from your 1.3 installation.</li>
-<li><b>JDK 1.6</b> - Say here whether you used the 1.6 jdk to build
-the JDBC4 support. Attach here the output of "java -version" run
-from your 1.6 installation.</li>
-<li><b>OSGi</b> - Say here whether you used osgi.jar to build org.apache.derby.osgi.EmbeddedActivator.</li>
-<li><b>Compiler</b> - Say which compiler you used. </li>
-<li><b>JSR 169</b> - Say whether you built the J2ME support and if so,
-which toolkit you used for this (e.g., java.sun.com/j2me or IBM WCTME 5.7).</li>
+<li>
+<b>Branch</b> - Source code came from the 10.3 branch.</li>
+<li>
+<b>Machine</b> - Cygwin on Microsoft Windows XP Professional Version 2002 Service Pack 2.</li>
+<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>



Mime
View raw message