You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by my...@apache.org on 2007/07/08 04:46:33 UTC
svn commit: r554300 - in /db/derby/code/branches/10.3: RELEASE-NOTES.html
java/build/org/apache/derbyBuild/JiraConnector.java
java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java
releaseSummary.xml
Author: myrnavl
Date: Sat Jul 7 19:46:32 2007
New Revision: 554300
URL: http://svn.apache.org/viewvc?view=rev&rev=554300
Log:
DERBY-2840 - updating Release Notes.
Also saving changes to JiraConnector and ReleaseNotesGenerator that enabled
me to make the release notes - except for the New Features area which was
done by hand based on JIRA and the DerbyTenThreeRelease wiki.
Modified:
db/derby/code/branches/10.3/RELEASE-NOTES.html
db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/JiraConnector.java
db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java
db/derby/code/branches/10.3/releaseSummary.xml
Modified: db/derby/code/branches/10.3/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/RELEASE-NOTES.html?view=diff&rev=554300&r1=554299&r2=554300
==============================================================================
--- db/derby/code/branches/10.3/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.3/RELEASE-NOTES.html Sat Jul 7 19:46:32 2007
@@ -1,10 +1,10 @@
<html>
-<title>Release Notes for Derby 10.3.1.0 beta</title>
+<title>Release Notes for Derby 10.3.1.1</title>
<body>
<h1>
-<a name="Release Notes for Derby 10.3.1.0 beta"></a>Release Notes for Derby 10.3.1.0 beta</h1>
+<a name="Release Notes for Derby 10.3.1.1"></a>Release Notes for Derby 10.3.1.1</h1>
<blockquote>
-<p>These notes describe the difference between Derby release 10.3.1.0 beta and the preceding release 10.2.2.0.</p>
+<p>These notes describe the difference between Derby release 10.3.1.1 and the preceding release 10.2.2.0.</p>
</blockquote>
<ul>
<li>
@@ -14,7 +14,7 @@
<a href="#New Features">New Features</a>
</li>
<li>
-<a href="#Bug Fixes">Bug Fixes</a>
+<a href="#CHANGES">CHANGES</a>
</li>
<li>
<a href="#Issues">Issues</a>
@@ -56,15 +56,20 @@
<h2>
<a name="New Features"></a>New Features</h2>
<blockquote>
+
+
<p>
This is a minor release. The following new features were added:
</p>
+
+
</blockquote>
+
<ul>
<h4>
<a name="Big Features"></a>Big Features</h4>
<blockquote>
-<p>The following issues are new with Derby release 10.3.1.0. beta.</p>
+<p>The following features are new with Derby release 10.3.1.1:</p>
<table border="2">
<tr>
<td><b>Feature</b></td><td><b>Description</b></td><td><b>Issue Id(s)</b></td>
@@ -95,6 +100,9 @@
<td> SSL/TLS </td><td> Implement SSL/TLS communication between client and server </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-2108">DERBY-2108</a> <a href="https://issues.apache.org/jira/browse/DERBY-2356">DERBY-2356</a> <a href="https://issues.apache.org/jira/browse/DERBY-2272">DERBY-2272</a> <a href="https://issues.apache.org/jira/browse/DERBY-2273">DERBY-2273</a> </td>
</tr>
<tr>
+<td> Blob/Clob API </td><td> Support all JDBC API methods for Blob/Clob, both for embedded driver and client driver </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-1341 ">DERBY-1341 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-1285">DERBY-1285 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-1286">DERBY-1286 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-2443">DERBY-2443 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-2444">DERBY-2444 </a>, <a href="https://issues.apache.org/jira/browse/DERBY-2730">DERBY-2730 </a> </td>
+</tr>
+<tr>
<td> Client Side Tracing </td><td> Provide a way to enable client tracing without changing the application </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-1275">DERBY-1275</a> </td>
</tr>
<tr>
@@ -103,6 +111,12 @@
<tr>
<td> JDBC methods for autogenerated keys </td><td> Implement JDBC methods for autogenerated keys for Embedded </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-2631">DERBY-2631</a> </td>
</tr>
+<tr>
+<td> CREATE TABLE AS <subquery> WITH NO DATA </td><td> Enable Create of a new empty table based upon a sub query </td><td> <a href="https://issues.apache.org/jira/browse/DERBY-64">DERBY-64</a></td>
+</tr>
+<tr>
+<td> XATransaction timeout </td><td> Support for XAResource.setTransactionTimeout</td><td>Master JIRA: <a href="https://issues.apache.org/jira/browse/DERBY-2432">DERBY-2432</a></td>
+</tr>
</table>
</blockquote>
@@ -133,14 +147,64 @@
</ul>
<h2>
-<a name="Bug Fixes"></a>Bug Fixes</h2>
+<a name="CHANGES"></a>CHANGES</h2>
<blockquote>
-<p>The following issues are addressed by Derby release 10.3.1.0 beta. These issues are not addressed in the preceding 10.2.2.0 release.</p>
+<p>The following issues are addressed by Derby release 10.3.1.1. These issues are not addressed in the preceding 10.2.2.0 release. </br>
+Note that some of these issues were discovered during development of the release and may not affect earlier releases. </br>
+This list includes bugs, improvements and new features, including sub-tasks, but not issues with only test or web content changes.</p>
<table border="2">
<tr>
<td><b>Issue Id</b></td><td><b>Description</b></td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2891">DERBY-2891</a></td><td>Clob.getCharacterStream(long,long) ignores position parameter for large (>32k) CLOBs</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2890">DERBY-2890</a></td><td>Simplify handling of maxPos in UpdatableBlobStream and ClobUpdatableReader</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2885">DERBY-2885</a></td><td>Wrong connection object used in EmbedConnection.clearLOBMapping()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2882">DERBY-2882</a></td><td>Remove references to JDK 1.2 and 1.3 in the documentation</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2879">DERBY-2879</a></td><td>CREATE TABLE AS <subquery> does not maintain the collation for character types.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2874">DERBY-2874</a></td><td>NetworkServer not accepting connections with default security manager on Ipv6 machines</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2868">DERBY-2868</a></td><td>BUILDING.txt doesn't mention junit.jar in list of jars installed in tools/java</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2863">DERBY-2863</a></td><td>Collation doc corrections/improvements</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2860">DERBY-2860</a></td><td>Documentation problems for IMPORT/EXPORT LOBs feature</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2858">DERBY-2858</a></td><td>Export exceptions swallow useful information</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2849">DERBY-2849</a></td><td>Add a documentation for derby.jdbc.xaTransactionTimeout system/database property</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2847">DERBY-2847</a></td><td>More clarification issues for the release notes.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2846">DERBY-2846</a></td><td>Fix wrong Javadoc in LOB related Update sensitive streams on the NetworkClient</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2839">DERBY-2839</a></td><td>initial problems with the 10.3.1.0 beta candidate</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2837">DERBY-2837</a></td><td>Update docs on STRONG_PASSWORD_SUBSTITUTE_SECURITY/ENCRYPTED_USER_AND_PASSWORD_SECURITY and JCE support</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2831">DERBY-2831</a></td><td>NullPointerException creating a function in a schema that doesn't exist when the return type is a character type</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2830">DERBY-2830</a></td><td>Rename UpdateableBlobStream to UpdatableBlobStream</td>
</tr>
<tr>
@@ -156,21 +220,36 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2817">DERBY-2817</a></td><td>Error messages for deadlocks contain less information than in 10.2</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2814">DERBY-2814</a></td><td>Specifying derby.* properties used in default policy file in derby.properties does not work</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2812">DERBY-2812</a></td><td>Assessing blob (when its linked to DVD stream, ie large blob) corrupts stream fetched prior to this access.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2811">DERBY-2811</a></td><td>Specifying -h 0.0.0.0 with default security manager bars clients from connecting from any host</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2809">DERBY-2809</a></td><td>Expressions with a parameter can be assigned the incorrect type</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2806">DERBY-2806</a></td><td>calling getByteLength on org.apache.derby.impl.jdbc.StoreStreamClob makes BinaryStream, fetched before this call, unusable</td>
</tr>
<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2805">DERBY-2805</a></td><td>ASSERT failure with sane build if DISTINCT and ORDER BY are present in a query that selects from a diagnostic table function.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2803">DERBY-2803</a></td><td>SSL certificate authentication succeeds unexpectedly</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2802">DERBY-2802</a></td><td>LOBStreamControl.replaceBytes can throw null pointer exception while trying to access databytes after calling init</td>
</tr>
<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2800">DERBY-2800</a></td><td>Implement Clob.truncate for embedded driver</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2796">DERBY-2796</a></td><td>Obscure error messages when using SSL in various combinations</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2795">DERBY-2795</a></td><td>Unable to bring up server with SSL peer authentication enabled</td>
</tr>
<tr>
@@ -183,6 +262,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2789">DERBY-2789</a></td><td>DatabaseMetaData .locatorsUpdateCopy() should return true</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2788">DERBY-2788</a></td><td>Authentication tests fails with 'org.apache.derby.jdbc.EmbeddedDriver is not registered with the JDBC driver manager'</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2787">DERBY-2787</a></td><td>make entry for clob in connection so that temporary file is removed when a connection is closed or transaction is commited/rolledback</td>
</tr>
<tr>
@@ -192,12 +274,18 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2777">DERBY-2777</a></td><td>Parameters should take their collation from the context in which they are getting used rather than the current compilation schema</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2776">DERBY-2776</a></td><td>Internally generated CAST nodes should not use the collation of the current compilation schema. Instead they should use collation of target type passed to it.</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2772">DERBY-2772</a></td><td>Create a procedure to empty the statement cache exposing the existing functionality.</td>
</tr>
<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2770">DERBY-2770</a></td><td>testBlobAfterCommit(....jdbcapi.BlobClob4BlobTest) fails with 'Unexpected SQL state. expected:<XJ[073]> but was:<XJ[215]>'</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2765">DERBY-2765</a></td><td>Make sure that all the DTDs for character string types have correct collation assigned to them.</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2763">DERBY-2763</a></td><td>In the Network Client InputStreams and Readers returned from LOB's should be sensitive to underlying LOB data changes.</td>
</tr>
<tr>
@@ -222,6 +310,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2740">DERBY-2740</a></td><td>LIKE parameter marker combined with index multi-probing leads to ASSERT failure with sane jars, wrong results with insane jars.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2737">DERBY-2737</a></td><td>Change documentation on permissions needed to include read/write for system property derby.storage.jvmInstanceId </td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2735">DERBY-2735</a></td><td>Add a system procedure to set a user's connection level authorization.</td>
</tr>
<tr>
@@ -231,6 +322,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2729">DERBY-2729</a></td><td>temporary lob file should be cleaned when the transaction or connection is no longer valid.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2725">DERBY-2725</a></td><td>If all the operands involved in collation operation have a collation derivation of NONE, then Derby should throw an exception for that as per the SQL standards.</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2724">DERBY-2724</a></td><td>Set correct collation type and derivation for result character string types from CURRENT ISOLATION, CURRENT_USER, SESSION_USER, SYSTEM_USER, CURRENT SCHEMA and CURRENT SQLID.</td>
</tr>
<tr>
@@ -285,6 +379,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2692">DERBY-2692</a></td><td>Client driver doesn't chain exceptions received from the server</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2689">DERBY-2689</a></td><td>Deadlock with GenericPreparedStatement</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2686">DERBY-2686</a></td><td>The skip method for some InputStreams and Readers return invalid values</td>
</tr>
<tr>
@@ -312,6 +409,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2654">DERBY-2654</a></td><td>Document newly-supported (in embedded mode) JDBC methods for autogenerated keys.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2652">DERBY-2652</a></td><td>Clob.setCharacterStream differs between embedded and client driver</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2646">DERBY-2646</a></td><td>Cleanup of Clob control/support structures</td>
</tr>
<tr>
@@ -333,6 +433,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2621">DERBY-2621</a></td><td>Fix javadoc issues related to locator work</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2619">DERBY-2619</a></td><td> A Derby source release must include the documentation source files</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2613">DERBY-2613</a></td><td>upgrade test problem when attempting to test 10.0.2.1 - </td>
</tr>
<tr>
@@ -342,6 +445,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2608">DERBY-2608</a></td><td>Compilation Error of manual in Apache FOP</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2607">DERBY-2607</a></td><td>DatabaseMetaData is not consistent about throwing SqlException when tablename=null</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2606">DERBY-2606</a></td><td>Derby should print the parameters to failed statements to the derby.log when it logs the error </td>
</tr>
<tr>
@@ -357,6 +463,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2600">DERBY-2600</a></td><td>Remove temporary code added to enable testing of CLOB locator related stored procedures.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2599">DERBY-2599</a></td><td>Set correct collation type and derivation on DataTypeDescriptor(DTD).</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2598">DERBY-2598</a></td><td>new upgrade test failures after change 528033</td>
</tr>
<tr>
@@ -396,6 +505,9 @@
<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-2570">DERBY-2570</a></td><td>Create a utility which generates Release Notes</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2566">DERBY-2566</a></td><td>OutOfMemory/Sanity-assert failed when updating database</td>
</tr>
<tr>
@@ -435,6 +547,9 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2511">DERBY-2511</a></td><td>reference manual's description of JDBC4 features has misleading sections</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2509">DERBY-2509</a></td><td>Implement the XA transaction timeout support for client driver.</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2508">DERBY-2508</a></td><td>Implement the XA transaction timeout support for embedded driver.</td>
</tr>
<tr>
@@ -495,6 +610,9 @@
<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-2433">DERBY-2433</a></td><td>Error message when booting server with no authentication is misleading</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2432">DERBY-2432</a></td><td>Unimplemented transaction time out for XA transactions may cause that locks will not be released when client terminates outside a unit of work.</td>
</tr>
<tr>
@@ -588,6 +706,12 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-2336">DERBY-2336</a></td><td>Enable collation based ordering for CHAR data type.</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2335">DERBY-2335</a></td><td>Compare character datatypes with different collation ordering.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-2331">DERBY-2331</a></td><td>Disallow code in installed jars from resolving classes in the org.apache.derby.* namespace except for public apis.</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-2330">DERBY-2330</a></td><td>Disallow user-defined SQL routines to resolve to entry points (methods in classes) in the org.apache.derby.* namespace</td>
</tr>
<tr>
@@ -1047,153 +1171,287 @@
<td><a href="http://issues.apache.org/jira/browse/DERBY-1341">DERBY-1341</a></td><td>LOB set method(s) are currently no supported, but part of the Java 1.4 JDBC interface</td>
</tr>
<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1285">DERBY-1285</a></td><td>Finish JDBC3 Blob implementation</td>
+</tr>
+<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-1275">DERBY-1275</a></td><td>Provide a way to enable client tracing without changing the application</td>
</tr>
<tr>
<td><a href="http://issues.apache.org/jira/browse/DERBY-1132">DERBY-1132</a></td><td>Truncation Error with Concat</td>
</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-1054">DERBY-1054</a></td><td>Starting Derby with the NetServlet inside of tomcat does not allow binding to non localhost interface.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-931">DERBY-931</a></td><td>Until DERBY-911 gets fixed, document the difference in behavior between Nework Client Driver and Embedded Driver for setReadOnly</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-908">DERBY-908</a></td><td>YEAR,SECOND,MONTH, MINUTE, HOUR and DAY functions have incorrect information on durations.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-815">DERBY-815</a></td><td>Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-806">DERBY-806</a></td><td>One each deleted or updated from a heap row a new RowPosition object is created.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-801">DERBY-801</a></td><td>Allow parallel access to data files.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-790">DERBY-790</a></td><td>SQLException used by the networked interface to Derby is not serializable</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-729">DERBY-729</a></td><td>Scalar time and date functions return 0 instead NULL when argument is NULL</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-681">DERBY-681</a></td><td>Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-680">DERBY-680</a></td><td>In ij, executing a prepared statement with numeric/decimal parameter fails with NullPointerException in J2ME/CDC/FP</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-630">DERBY-630</a></td><td>create trigger fails with null pointer exception</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-606">DERBY-606</a></td><td>SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-595">DERBY-595</a></td><td>Using derby.language.logStatementText=true can mask certain exceptions and lead to incorrect behavior in some cases</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-552">DERBY-552</a></td><td>Fetching resources using getResourceAsStream from a jar stored in a database that is archived in a jar file fails</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-538">DERBY-538</a></td><td>Investigate using the standard java.net.URLClassLoader for database class loading.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-537">DERBY-537</a></td><td>SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-415">DERBY-415</a></td><td>sysinfo with -cp client option should not print error saying DB2 jar file and driver class are missing</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-396">DERBY-396</a></td><td>Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-391">DERBY-391</a></td><td>Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-378">DERBY-378</a></td><td>support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-264">DERBY-264</a></td><td>This enhancement to allow expressions in ORDER BY clause will require documentation changes.</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-234">DERBY-234</a></td><td>Documentation of DateTime types is incomplete</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-208">DERBY-208</a></td><td>Add support to retrieve lobs for Network Server by locator rather than matierializing the LOB</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-183">DERBY-183</a></td><td>Parameter names required in CREATE FUNCTION</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-147">DERBY-147</a></td><td>ERROR 42X79 not consistant ? - same column name specified twice</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-64">DERBY-64</a></td><td>Create a table with a query</td>
+</tr>
+<tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-47">DERBY-47</a></td><td>Some possible improvements to IN optimization</td>
+</tr>
</table>
</blockquote>
<h2>
<a name="Issues"></a>Issues</h2>
<blockquote>
-<p>Compared with the previous release (10.2.2.0), Derby release 10.3.1.0 beta introduces the following new features and incompatibilities. These merit your special attention.</p>
+<p>Compared with the previous release (10.2.2.0), Derby release 10.3.1.1 introduces the following new features and incompatibilities. These merit your special attention.</p>
<ul>
<li>
-<a href="#Note for DERBY-2757">Note for DERBY-2757:
+<a href="#Note for DERBY-2757">
+<p>Note for DERBY-2757:
Security enhancements to the Network Server may slow down Derby's runtime performance, and
they may trigger SecurityExceptions when Derby executes user-written
functions and procedures.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2729">Note for DERBY-2729: Blob and Clob objects, irrespective of size, are released once
-transaction is not valid or when connection is closed.</a>
+<a href="#Note for DERBY-2729">
+<p>Note for DERBY-2729: Blob and Clob objects are released when the
+transaction ends and when the connection is closed.</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-2610">Note for DERBY-2610:
+<a href="#Note for DERBY-2610">
+<p>Note for DERBY-2610:
The table name can no longer be a pattern in calls to DatabaseMetaData
methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo,
getVersionColumns, getPrimaryKeys, getImportedKeys, getExportedKeys
and getCrossReference.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2526">Note for DERBY-2526: Queries which use the JOIN ... ON syntax to join with views or other
-non-base table expressions may now return different results.</a>
+<a href="#Note for DERBY-2526">
+<p>Note for DERBY-2526: Queries which use the JOIN ... ON syntax to join with views or other
+non-base table expressions may now return different results.<br>
+
+</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-2443">Note for DERBY-2443:
-Detailed
-description of these methods can be found in api docs of J2SE 6:
+<a href="#Note for DERBY-2443">
+<p>Note for DERBY-2443: Added unimplemented methods introduced in the java.sql.ResultSet
+interface.</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2430">Note for DERBY-2430:
+<a href="#Note for DERBY-2430">
+<p>Note for DERBY-2430:
The application
will see an error in the event of calling setObject(int targetType,
Blob source) and setObject(int targetType, Clob source) with a
targetType other than Blob and Clob. This will be in conformance with
the embedded behaviour.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2386">Note for DERBY-2386:
+<a href="#Note for DERBY-2386">
+<p>Note for DERBY-2386:
The return type of the timestampdiff function has been changed from INT to BIGINT.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2370">Note for DERBY-2370: EXISTS predicates with subqueries that use set operators (UNION,
-INTERSECT, EXCEPT) may now behave differently.</a>
-</li>
-<li>
-<a href="#Note for DERBY-2330">Note for DERBY-2330: ???</a>
+<a href="#Note for DERBY-2370">
+<p>Note for DERBY-2370: EXISTS predicates with subqueries that use set operators (UNION,
+INTERSECT, EXCEPT) may now behave differently.</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-2296">Note for DERBY-2296:
+<a href="#Note for DERBY-2296">
+<p>Note for DERBY-2296:
ClientDataSource now supports the createDatabase and shutdownDatabase properties.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2264">Note for DERBY-2264:
+<a href="#Note for DERBY-2264">
+<p>Note for DERBY-2264:
Henceforth, when authentication is enabled
-(</a>
+(<code>derby.connection.requireAuthentication</code> has the
+value <code>true</code>) <i>and</i> SQL Authentication is enabled
+(<code>derby.database.sqlAuthentication</code> has the
+value <code>true</code>) some database level operations are restricted
+to the <i>database owner</i>.
+</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-2256">Note for DERBY-2256: Use of decimal values in an IN predicate whose left operand is an
-INTEGER may now return different results.</a>
+<a href="#Note for DERBY-2256">
+<p>Note for DERBY-2256: Use of decimal values in an IN predicate whose left operand is an
+INTEGER may now return different results.<br>
+
+</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-2196">Note for DERBY-2196:
+<a href="#Note for DERBY-2196">
+<p>Note for DERBY-2196:
The user should customize the security policy which the Network Server
now installs by default.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2108">Note for DERBY-2108:
+<a href="#Note for DERBY-2108">
+<p>Note for DERBY-2108:
SSL/TLS implemented for client/server communication.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-2020">Note for DERBY-2020:
+<a href="#Note for DERBY-2020">
+<p>Note for DERBY-2020:
Writing of the transaction log to disk has been changed to open log files in "rwd" mode instead of "rws" if the JVM supports it.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-1942">Note for DERBY-1942: The use of the TIME data type is more restricted. </a>
+<a href="#Note for DERBY-1942">
+<p>Note for DERBY-1942: The use of the TIME data type is more restricted. </p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-1852">Note for DERBY-1852: Queries with nested set operators (UNION, INTERSECT, EXCEPT) in a
+<a href="#Note for DERBY-1852">
+<p>Note for DERBY-1852: Queries with nested set operators (UNION, INTERSECT, EXCEPT) in a
FROM list may now return different results.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-1828">Note for DERBY-1828:
+<a href="#Note for DERBY-1828">
+<p>Note for DERBY-1828:
Most authorization failures have new error codes.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-1816">Note for DERBY-1816: ResultSet.getTime() on an SQL TIMESTAMP value now has millisecond
-resolution with the Derby client driver.</a>
+<a href="#Note for DERBY-1816">
+<p>Note for DERBY-1816: ResultSet.getTime() on an SQL TIMESTAMP value now has millisecond
+resolution with the Derby client driver.<br>
+
+</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-1610">Note for DERBY-1610:
-Derby's Client implementation will return an appropriate error, more often matching the behavior with Embedded in the a number of situations related to.setNull(int, int) and set*(int, null, int) methods for PreparedStatement and CallableStatement.
+<a href="#Note for DERBY-1610">
+<p>Note for DERBY-1610:
+In a number of usage cases of setNull(int, int) and set*(int, null, int) methods for PreparedStatement and CallableStatement, Derby's Client implementation has been changed, to correctly behave in the same way as the Embedded implementation.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-1519">Note for DERBY-1519:
+<a href="#Note for DERBY-1519">
+<p>Note for DERBY-1519:
Streams obtained by calling get-/setAsciiStream in the client driver use encoding "ISO-8859-1" instead of "US-ASCII".
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-1484">Note for DERBY-1484:
+<a href="#Note for DERBY-1484">
+<p>Note for DERBY-1484:
The table name can no longer be null in calls to DatabaseMetaData methods getBestRowIdentifier, getColumnPrivileges, getIndexInfo, getVersionColumns, getPrimaryKeys, getImportedKeys and getExportedKeys.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-1341">Note for DERBY-1341: Added unimplemented methods introduced in the JDBC 3.0 and 4.0
-specification. Blob and Clob now support all the methods of JDBC 3.0 and 4.0.</a>
+<a href="#Note for DERBY-1341">
+<p>Note for DERBY-1341: Added unimplemented methods introduced in the JDBC 3.0 and 4.0
+specification. Blob and Clob now support all the methods of JDBC 3.0 and 4.0.</p>
+</a>
</li>
<li>
-<a href="#Note for DERBY-729">Note for DERBY-729:
+<a href="#Note for DERBY-729">
+<p>Note for DERBY-729:
Scalar time and date functions should return NULL when the argument is NULL
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-415">Note for DERBY-415:
+<a href="#Note for DERBY-415">
+<p>Note for DERBY-415:
Sysinfo now presents separate command switches to check the classpath for the presence of the Derby client and the DB2 JCC driver.
+</p>
</a>
</li>
<li>
-<a href="#Note for DERBY-208">Note for DERBY-208: Network Client: Locator-based implementation of Blob/Clob
+<a href="#Note for DERBY-208">
+<p>Note for DERBY-208: Network Client: Locator-based implementation of Blob/Clob
operations.
-</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.
+</p>
</a>
</li>
</ul>
@@ -1345,12 +1603,8 @@
<h4>Summary of Change</h4>
-<p>Blob and Clob objects, irrespective of size, are released once
-transaction is not valid or when connection is closed.</p>
-
-
-
-
+<p>Blob and Clob objects are released when the
+transaction ends and when the connection is closed.</p>
<!--
@@ -1371,44 +1625,10 @@
-<p>While using Embedded Driver</p>
-
-
-
-<ul>
-
-
-
-<li>Short Blob or Clob throwing SQLException with SQLSTATE set to XJ215 when accessed after commit/rollback.</li>
-
-
-
-<li>Short Blob or Clob throwing SQLException with SQLSTATE set to 08003 when accessed after closing connection.</li>
-
-
-
-<li>SQLException with state XJ215 when applications were expecting it to be XJ073.</li>
-
-
-
-</ul>
-
-
-While using Network Client<br>
-
-
-
-<ul>
-
-
-
-<li>Calling any method on Blob or Clob after commit throw
- SQLException with SQLSTATE set to XJ215.</li>
-
-
-
-</ul>
+<p>Applications now get a SQLException with SQL STATE XJ215 when
+ accessing Blobs and Clobs after the transaction ends or the
+ connection is closed.</p>
<!--
OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
@@ -1421,49 +1641,13 @@
<h4>Incompatibilities with Previous Release</h4>
-Blob and Clob objects
-won't be usable if transaction is committed or rolled back (either
-explicitly or indirect commit in case of auto commit is turned on) or if
-a transaction is rolled back in case of an exception with severity level
-TRANSACTION or higher.
-<p>
-
-Embedded Driver</p>
-
-
-
-<ul>
-
-
-
-<li>Short Blob or Clob are not accessible beyond transaction.</li>
-
-
-
-<li>Short Blob or Clob are not accessible after connection is closed.</li>
-
-
-
-</ul>
-
-
-Network Client<br>
-
-
-
-<ul>
-
-
-
-<li>Blob and Clob are not accessible after commit/rollback.</li>
-
-
-
-</ul>
-
-
+<p>
+In the previous release, Blobs and Clobs were sometimes usable even
+ after the transaction ended or the connection was closed. Now Blobs
+ and Clobs are not usable after these events.
+</p>
<!--
DESCRIBE WHY THE CHANGE WAS MADE.
@@ -1478,53 +1662,13 @@
<h4>Rationale for Change</h4>
-
-
-<ul>
-
-
-
-<li>Network Client and Embedded driver have same behavior hence the application are easier to port from one mode to another.</li>
-
-
-</ul>
-
-
-<ul>
-
-
-<li>Small and Large behave same hence user doesn't have to bother about small and large lob.</li>
-
-
-
-</ul>
-
-
-
-<ul>
-
-
-
-
-
-<ul>
-
-
-<li>Concept of small and large lobs is little vague as it depends on
-page size and available space in it. An application can't be sure what
-size will be considered small.</li>
-
-
-
-</ul>
-
-
-
-</ul>
-
-
-
-
+<p>
+Now Blobs and Clobs store their data in temporary files.
+These temporary files are deleted when the transaction ends.
+The Blob.free() and Clob.free() methods also delete these temporary files.
+This erases the transient state of these large objects and makes them
+unusable.
+</p>
<!--
OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
@@ -1539,43 +1683,10 @@
<h4>Application Changes Required</h4>
-
-
-<p>Embedded Driver</p>
-
-
-
-<ul>
-
-
-
-<li>Applications shouldn't try to access lob objects small lob
-objects beyond transaction boundary or after connection is closed.</li>
-
-
-
-</ul>
-
-
-
-<p>Network Client</p>
-
-
-
-<ul>
-
-
-
-<li>Applications should not try to access lob objects beyond transaction boundary.
- </li>
-
-
-
-</ul>
-
-
-
-
+<p>
+Applications should be revised to not use Blobs and Clobs after
+ the transaction ends or the connection is closed.
+</p>
</blockquote>
@@ -1812,8 +1923,8 @@
<h4>Summary of Change</h4>
-<P>Added unimplemented methods introduced in the java.sql.ResultSet
-interface.</P>
+<p>Added unimplemented methods introduced in the java.sql.ResultSet
+interface.</p>
<!-- DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
For instance:
@@ -1829,9 +1940,9 @@
<h4>Symptoms Seen by Applications Affected by Change</h4>
-<P>Existing application won't be effected by it as these methods are
+<p>Existing application won't be effected by it as these methods are
new implementations. Applications won't be getting Not Implemented
-exception anymore.</P>
+exception anymore.</p>
<!-- DESCRIBE WHY THE CHANGE WAS MADE.
@@ -1845,8 +1956,8 @@
<h4>Rationale for Change</h4>
-<P>To add implementations for unimplemented Blob and Clob related
-methods in the ResultSet interface.</P>
+<p>To add implementations for unimplemented Blob and Clob related
+methods in the ResultSet interface.</p>
<!-- OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
@@ -1860,7 +1971,7 @@
<h4>Application Changes Required</h4>
-<P>Applications can now make use of the following new methods</P>
+<p>Applications can now make use of the following new methods</p>
<pre>
@@ -1881,7 +1992,7 @@
<p>
Detailed
-description of these methods can be found in api docs of J2SE 6:
+description of these methods can be found in api docs of Java SE 6:
<a href="http://java.sun.com/javase/6/docs/api/java/sql/ResultSet.html">ResultSet</a>.
</p>
@@ -2006,7 +2117,7 @@
<p>
In the previous release(s), using the builtin timestampdiff function using the SQL_TSI_FRAC_SECOND for the datepart parameter would return an integer overflow error except with very small intervals, less then a second, because the result would exceed the range of an INT.
For intervals larger than a second, SQL_TSI_SECOND had to be used. Now, the result type has been changed to BIGINT and so one can use intervals > 1 sec with SQL_TSI_FRAC_SECOND.
-However as a result of the change SQL functions taking the result of the timestampdiff function as a parameter as INT will no longer be resolved.
+However as a result of the change SQL functions that take the result of the timestampdiff function as a parameter of datatype INT will no longer be resolved.
</p>
@@ -2200,10 +2311,6 @@
</blockquote>
<hr>
<h3>
-<a name="Note for DERBY-2330"></a>Note for DERBY-2330</h3>
-<blockquote></blockquote>
-<hr>
-<h3>
<a name="Note for DERBY-2296"></a>Note for DERBY-2296</h3>
<blockquote>
<!--
@@ -2380,7 +2487,7 @@
</ul>
an SQLException with SQLState "08004" is thrown. For the English
-locale the exception string will be be one of:
+locale the exception string will be one of:
<ul>
<li>User <i>user</i> cannot shut down database <i>database</i>. Only
@@ -3460,7 +3567,7 @@
<h4>Summary of Change</h4>
<p>
-Derby's Client implementation will return an appropriate error, more often matching the behavior with Embedded in the a number of situations related to.setNull(int, int) and set*(int, null, int) methods for PreparedStatement and CallableStatement.
+In a number of usage cases of setNull(int, int) and set*(int, null, int) methods for PreparedStatement and CallableStatement, Derby's Client implementation has been changed, to correctly behave in the same way as the Embedded implementation.
</p>
@@ -3480,28 +3587,29 @@
<h4>Symptoms Seen by Applications Affected by Change</h4>
<p>
-In a number of calls involving null values with PreparedStatement and CallableStatement, Derby's client implementation behaved differently from the Embedded implementation.
+In a number of method calls involving null values for PreparedStatement and CallableStatement, Derby's Client implementation behaved differently from the Embedded implementation.
+Now, in most cases, the Client returns an error where Embedded returns an error and succeeds where Embedded succeeds.
For instance:
<ol>
<li>setNull(LONGVARCHAR) on parameter of type CHAR FOR BIT DATA (Types.BINARY).
-In previous releases, the Client succeeds, embedded fails (state 22005).</li>
+In previous releases, Embedded returned an error (SQLState 22005), but the Client did not. Now, both Embedded and Client will return an error.</li>
<li> setNull(LONGVARBINARY) on parameter of type CHAR FOR BIT DATA (Types.BINARY).
-In previous releases, Embedded succeeds, client fails (state 22005).</li>
+In previous releases, this call succeeded with Embedded, but the Client returned an error (SQLState 22005). Now, such a call will succeed with both Embedded and Client.</li>
<li> setNull(LONGVARBINARY) on parameter of type VARCHAR FOR BIT DATA (Types.VARBINARY).
-In previous releases, Embedded succeeds, client fails (state 22005).</li>
+In previous releases, the call succeeded with Embedded, Client returned an error (SQLState 22005). Now, such a call will succeed with both Embedded and Client.</li>
-<li> setNull(BINARY) on parameter of type LONG VARCHAR FOR BIT DATA (Types.LONGVARBINARY)
-In previous releases, Embedded succeeds, client fails (state 22005).</li>
+<li> setNull(BINARY) on parameter of type LONG VARCHAR FOR BIT DATA (Types.LONGVARBINARY).
+In previous releases, such a call succeeded with Embedded, but Client returned an error (SQLState 22005). Now, such a call will succeed with both Embedded and Client.</li>
<li> setNull(TIME) on parameter of TIMESTAMP.
-In previous releases, Client succeeds, embedded fails (state 22005).</li>
+In previous releases, Embedded returned an error (SQLState 22005), but the Client did not. Now, both Embedded and client will return an error.</li>
</ol>
-Similar difference existed with the set<type>(int, null) calls. In most cases, the Client now returns an error where embedded returns an error.
-Note, that the actual SQLState returned may still be different between the two implementations.
+Similar differences existed with the set<type>(int, null) calls.<br>
+Note, that where an error is returned, the actual SQLState returned may still be different between the two implementations.
</p>
@@ -3518,7 +3626,7 @@
<h4>Incompatibilities with Previous Release</h4>
<p>
-Now, in the cases indicated above, the client and Embedded implementation show the behavior previously shown only with Embedded.
+Now, in the cases indicated above, the Client and Embedded implementation show the behavior previously shown only with Embedded.
</p>
@@ -3896,7 +4004,7 @@
</div>
-Detailed description of these methods can be found in api docs of J2SE 6<br>
+Detailed description of these methods can be found in api docs of Java SE 6<br>
<div style="margin-left: 40px;">
@@ -4202,83 +4310,11 @@
are no longer needed.</p>
</blockquote>
-<hr>
-<h3>
-<a name="Note for DERBY-119"></a>Note for DERBY-119</h3>
-<blockquote>
-<!--
- SUMMARIZE THE ISSUE. This is a one line summary of the issue.
-
- For instance:
-
- Applications may no longer open two InputStreams on the same ResultSet column.
--->
-
-<h4>Summary of Change</h4>
-
-<p>
-The ALTER TABLE statement now includes the additional ability to alter
-the NULL / NOT NULL constraint on a column in a table.
-</p>
-
-<!--
- DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
-
- For instance:
-
- In the previous release, applications were able to open two
- InputStreams on the same column. Depending on how these streams
- interacted, the value siphoned out of the column was erratic. Now
- Derby raises a SQLException when the application attempts to create
- the second InputStream.
--->
-
-<h4>Symptoms Seen by Applications Affected by Change</h4>
-
-<p>
-The syntax is:
-</p>
-
-
-<blockquote>
-<pre>
-ALTER TABLE table ALTER [COLUMN] column [NOT] NULL
-</pre>
-</blockquote>
-
-
-<p>
-You cannot remove the NOT NULL constraint if the column is used
-in a PRIMARY KEY or UNIQUE constraint.
-</p>
-
-
-<p>
-In addition, you cannot add the NOT NULL constraint if there are existing NULL
-values for the column in the table.
-</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>
-Users have requested this feature and other databases support it.
-</p>
-
-</blockquote>
</blockquote>
<h2>
<a name="Build Environment"></a>Build Environment</h2>
<blockquote>
-<p>Derby release 10.3.1.0 beta was built using the following environment:</p>
+<p>Derby release 10.3.1.1 was built using the following environment:</p>
<ul>
<li>
<b>Branch</b> - Source code came from the 10.3 branch.</li>
Modified: db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/JiraConnector.java
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/JiraConnector.java?view=diff&rev=554300&r1=554299&r2=554300
==============================================================================
--- db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/JiraConnector.java (original)
+++ db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/JiraConnector.java Sat Jul 7 19:46:32 2007
@@ -44,15 +44,14 @@
public static String jira_releaseNotesSource =
"http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss" +
- "&pid=10594&sorter/field=issuekey&sorter/order=DESC&tempMax=50" +
- "&reset=true&decorator=none&customfield_12310090=" +
- "Existing+Application+Impact&customfield_12310090=Release+Note+Needed";
+ "&pid=10594&sorter/field=issuekey&sorter/order=DESC&tempMax=100" +
+ "&reset=true&decorator=none&customfield_12310090=Release+Note+Needed";
public static String jira_fixedBugsSource =
"http://issues.apache.org/jira/sr/jira.issueviews:" +
"searchrequest-xml/temp/SearchRequest.xml?&pid=10594&resolution=1&" +
- "fixVersion=10.3.0.0&sorter/field=issuekey&sorter/order=DESC&" +
- "tempMax=1000&reset=true&decorator=none";
+ "fixVersion=10.3.0.0&fixVersion=10.3.1.0&fixVersion=10.3.1.1&sorter/field=issuekey&sorter/order=DESC&" +
+ "tempMax=2000&reset=true&decorator=none";
// other urls to some cute jira reports in xml.
// all
Modified: db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java?view=diff&rev=554300&r1=554299&r2=554300
==============================================================================
--- db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java (original)
+++ db/derby/code/branches/10.3/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java Sat Jul 7 19:46:32 2007
@@ -111,7 +111,7 @@
// major sections
private static final String OVERVIEW_SECTION = "Overview";
private static final String NEW_FEATURES_SECTION = "New Features";
- private static final String BUG_FIXES_SECTION = "Bug Fixes";
+ private static final String BUG_FIXES_SECTION = "CHANGES";
private static final String ISSUES_SECTION = "Issues";
private static final String BUILD_ENVIRONMENT_SECTION = "Build Environment";
@@ -165,6 +165,7 @@
private static final String JIRA_KEY = "key";
private static final String JIRA_NAME = "name";
private static final String JIRA_TITLE = "title";
+ private static final String JIRA_FIXIN = "fixVersion";
// managing releaseNote.html
private static final String RN_SUMMARY_OF_CHANGE = "Summary of Change";
@@ -588,7 +589,12 @@
String previousReleaseID = getPreviousReleaseID( gs );
String deltaStatement =
"The following issues are addressed by Derby release " + releaseID +
- ". These issues are not addressed in the preceding " + previousReleaseID + " release.";
+ ". These issues are not addressed in the preceding " +
+ previousReleaseID + " release." +
+ "Note that some of these issues were discovered during development" +
+ " of the release and may not affect earlier releases. " +
+ "This list includes bugs, improvements and new features, including sub-tasks," +
+ " but not issues with only test or web content changes.";
addParagraph( bugListSection, deltaStatement );
@@ -597,6 +603,8 @@
for ( int i = 0; i < count; i++ )
{
+ if (bugs[i] == null)
+ continue;
JiraIssue issue = bugs[ i ];
Element row = insertRow( table );
Element linkColumn = insertColumn( row );
@@ -631,6 +639,8 @@
int count = bugs.length;
String releaseID = getReleaseID( gs );
String previousReleaseID = getPreviousReleaseID( gs );
+ String greleaseID = releaseID;
+ String gpreviousReleaseID = previousReleaseID;
String deltaStatement =
"Compared with the previous release (" + previousReleaseID +
"), Derby release " + releaseID + " introduces the following new features " +
@@ -642,7 +652,9 @@
for ( int i = 0; i < count; i++ )
{
- JiraIssue issue = bugs[ i ];
+ if (bugs[ i ] == null)
+ continue;
+ JiraIssue issue = bugs[ i ];
Document releaseNote = null;
@@ -1282,6 +1294,19 @@
return retval;
}
+ private Element getNextChild( Element node, String childName, int index )
+ throws Exception
+ {
+ Element retval = (Element) node.getElementsByTagName( childName ).item( index );
+
+ if ( retval == null )
+ {
+ throw new BuildException( "Could not find child element '" + childName + "' in parent element '" + node.getNodeName() + "'." );
+ }
+
+ return retval;
+ }
+
private Element getOptionalChild( Element node, String childName )
throws Exception
{
@@ -1380,7 +1405,17 @@
int count = itemList.getLength();
JiraIssue[] issues = new JiraIssue[ count ];
- for ( int i = 0; i < count; i++ ) { issues[ i ] = makeJiraIssue( (Element) itemList.item( i ) ); }
+
+
+ //for ( int i = 0; i < count; i++ ) { issues[ i ] = makeJiraIssue( (Element) itemList.item( i ) ); }
+ for ( int i = 0; i < count; i++ )
+ {
+ JiraIssue ji = makeJiraIssue( (Element) itemList.item( i ) );
+ if (ji != null)
+ {
+ issues[ i ] = ji;
+ }
+ }
return issues;
}
@@ -1407,7 +1442,82 @@
//
title = title.substring( title.indexOf( ']' ) + 2, title.length() );
- return new JiraIssue( key, title, releaseNoteAttachmentID );
+ //return new JiraIssue( key, title, releaseNoteAttachmentID );
+ String type=squeezeText(getFirstChild(itemElement, "type"));
+ if (!(type.equals("Bug") || type.equals("New Feature") || type.equals("Improvement") || type.equals("Sub-task")))
+ return null;
+
+ try {
+ String component=squeezeText(getOptionalChild(itemElement, "component"));
+ if (component != null)
+ {
+ NodeList subItemList = itemElement.getElementsByTagName( "component" );
+ int compcount = subItemList.getLength();
+ for (int i=0; i<compcount; i++)
+ {
+ if (component.equals("Test") || component.equals("Web content"))
+ return null;
+ try {
+ component = squeezeText(getNextChild(itemElement, "component", i+1));
+ } catch (Exception e) {
+ // nothing...
+ }
+ }
+ }
+ } catch (NullPointerException e) {
+ // do nothing, now...
+ }
+
+ try {
+ String resolution=squeezeText(getOptionalChild(itemElement, "resolution"));
+ if (resolution != null)
+ {
+ if (!resolution.equals("Fixed"))
+ return null;
+ }
+ } catch (Exception e) {
+ return null;
+ }
+
+ String fixVersion=null;
+ try {
+ fixVersion=squeezeText(getOptionalChild(itemElement, JIRA_FIXIN));
+ } catch (Exception e) {
+ return null;
+ }
+
+ while (fixVersion != null)
+ {
+
+ NodeList subItemList = itemElement.getElementsByTagName( JIRA_FIXIN );
+ int fixcount = subItemList.getLength();
+ for (int i=0; i<fixcount; i++)
+ {
+ // if we encounter the previous release's ID, we can do away with entire issue
+ if (_previousReleaseID.equals(fixVersion))
+ {
+ return null;
+ }
+ // hardcode excluding 10.2.1.6; we want to exclude those also
+ if (fixVersion.equals("10.2.1.6"))
+ {
+ return null;
+ }
+ // if the first fixVersion does not match the current release, or the beta,
+ // check the next one
+ if ( (!_releaseID.equals(fixVersion)) && (!"10.3.0.0".equals(fixVersion))) {
+ try {
+ fixVersion = squeezeText(getNextChild( itemElement, JIRA_FIXIN, i+1));
+ continue;
+ } catch (Exception e) {
+ fixVersion=null;
+ return null;
+ }
+ }
+ }
+ return new JiraIssue( key, title, releaseNoteAttachmentID );
+ }
+ return null;
}
/**
Modified: db/derby/code/branches/10.3/releaseSummary.xml
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.3/releaseSummary.xml?view=diff&rev=554300&r1=554299&r2=554300
==============================================================================
--- db/derby/code/branches/10.3/releaseSummary.xml (original)
+++ db/derby/code/branches/10.3/releaseSummary.xml Sat Jul 7 19:46:32 2007
@@ -31,7 +31,7 @@
E.g.: 10.3.0.3
-->
-<releaseID>10.3.0.0</releaseID>
+<releaseID>10.3.1.1</releaseID>
<!--
Identifier of previous release. The release notes describe the