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 bp...@apache.org on 2016/10/02 19:22:40 UTC
svn commit: r1763095 - in /db/derby/code/branches/10.13: RELEASE-NOTES.html
releaseSummary.xml
Author: bpendleton
Date: Sun Oct 2 19:22:40 2016
New Revision: 1763095
URL: http://svn.apache.org/viewvc?rev=1763095&view=rev
Log:
DERBY-6911: Update releaseSummary.xml and generate first version of Release Notes for review
Modified:
db/derby/code/branches/10.13/RELEASE-NOTES.html
db/derby/code/branches/10.13/releaseSummary.xml
Modified: db/derby/code/branches/10.13/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.13/RELEASE-NOTES.html?rev=1763095&r1=1763094&r2=1763095&view=diff
==============================================================================
--- db/derby/code/branches/10.13/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.13/RELEASE-NOTES.html Sun Oct 2 19:22:40 2016
@@ -1,10 +1,10 @@
<html lang="en">
-<title>Release Notes for Apache Derby 10.12.0.0</title>
+<title>Release Notes for Apache Derby 10.13.1.0</title>
<body>
<h1>
-<a name="Release Notes for Apache Derby 10.12.0.0"></a>Release Notes for Apache Derby 10.12.0.0</h1>
+<a name="Release Notes for Apache Derby 10.13.1.0"></a>Release Notes for Apache Derby 10.13.1.0</h1>
<div>
-<p>These notes describe the difference between Apache Derby release 10.12.0.0 and the preceding release 10.11.1.1.</p>
+<p>These notes describe the difference between Apache Derby release 10.13.1.0 and the preceding release 10.12.1.1.</p>
</div>
<ul>
<li>
@@ -59,14 +59,12 @@ Derby functionality includes:
<p>
-Support for Java SE 6 and Java SE 7 is being sunsetted. The 10.13 release family will not support those platforms. The 10.12 release family supports the following Java and JDBC versions:
+The 10.13 release family supports the following Java and JDBC versions:
</p>
<ul>
-<li>Java SE 6 and higher with JDBC 4.0, 4.1, and 4.2.</li>
-
-<li>Java SE 8 compact profile 2.</li>
+<li>Java SE 8 </li>
</ul>
@@ -83,22 +81,13 @@ This is a feature release. The following
<ul>
+<li>DERBY-6136: tool for siphoning data out of corrupted databases</li>
-<li>
-<b>ALTER TABLE and identity columns</b> - The ALTER TABLE command can be used to add identity columns now. See the section on this statement in the Derby Reference Manual.</li>
-
-
-<li>
-<b>Cache-monitoring MBean</b> - An MBean has been added for monitoring internal Derby caches. See the description of <i>CacheManagerMBean</i> in the "Introduction to the Derby MBeans" section of the Derby Server and Administration Guide.</li>
-
-
-<li>
-<b>Optional Tool for Handling JSON Data</b> - An optional tool has been added for packing query results into JSON documents and for unpacking JSON documents into tabular result sets. See the section on the <i>simpleJson</i> optional tool in the Derby Tools and Utilities Guide.</li>
-
+<li>DERBY-6725: system function which prints out the name of the current database</li>
-<li>
-<b>Statistics aggregates</b> - SQL Standard VAR_POP(), VAR_SAMP(), STDDEV_POP(), and STDDEV_SAMP() aggregates have been added. See the "Aggregates (set functions)" section in the Derby Reference Manual.</li>
+<li>DERBY-4555: system procedures to import CSV file with headers</li>
+<li>DERBY-6852: allow identity columns to cycle.</li>
</ul>
@@ -107,7 +96,7 @@ This is a feature release. The following
<h2>
<a name="Bug Fixes"></a>Bug Fixes</h2>
<div>
-<p>The following issues are addressed by Derby release 10.12.0.0. These issues are not addressed in the preceding 10.11.1.1 release.</p>
+<p>The following issues are addressed by Derby release 10.13.1.0. These issues are not addressed in the preceding 10.12.1.1 release.</p>
<table border="2">
<tr>
<th>
@@ -115,384 +104,226 @@ This is a feature release. The following
</th><th>Description</th>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6829">DERBY-6829</a></td><td>Document the simpleJson optional tool and the SimpleJsonVTI.</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6825">DERBY-6825</a></td><td>Add basic JSON support to Derby.</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6824">DERBY-6824</a></td><td>Move ShutdownException into shared code area</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6820">DERBY-6820</a></td><td>Improve error handling in XmlVTI</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6807">DERBY-6807</a></td><td>XXE attack possible by using XmlVTI and the XML datatype</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6801">DERBY-6801</a></td><td>Implement MessageUtils class so client and server can share message argument encoding/decoding</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6800">DERBY-6800</a></td><td>Implement DerbySQLIntegrityConstraintViolationException class</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6783">DERBY-6783</a></td><td>WHEN clause in CREATE TRIGGER for UPDATE is not working for the sql script below</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6774">DERBY-6774</a></td><td>background post commit threads cause ASSERTS/errors on interaction with alter table add column</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6769">DERBY-6769</a></td><td>sane.derbyTesting.jar.lastcontents can be "out of date" but no build error results</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6768">DERBY-6768</a></td><td>List the enabled protocols in derby.log for network server configuration</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6753">DERBY-6753</a></td><td>Docs for IDENTITY_VAL_LOCAL needs to be updated to indicate that the return value will be impacted by single row UPDATE of identity column</td>
-</tr>
-<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6751">DERBY-6751</a></td><td>Prevent user code from getting the LanguageConnectionContext from an EmbedConnection</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6900">DERBY-6900</a></td><td>docs build for ref.html gives errors about rrefjavstateautogen.dita -- possible typo?</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6748">DERBY-6748</a></td><td>Localize messages introduced or changed in 10.11.1</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6895">DERBY-6895</a></td><td>Add documentation for new SYSCS_IMPORT_TABLE_BULK, SYSCS_IMPORT_DATA_BULK procedures</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6744">DERBY-6744</a></td><td>Update the documentation of security policy files to include the new usederbyinternals SystemPermission</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6894">DERBY-6894</a></td><td>Enhance COLUMNINDEXES parsing for SYSCS_IMPORT_DATA_BULK to recognize columns by name</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6742">DERBY-6742</a></td><td>For update statement, collect generated keys if Statement.RETURN_GENERATED_KEYS flag is supplied to the JDBC call.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6893">DERBY-6893</a></td><td>Create new SYSCS_IMPORT_DATA_BULK procedure</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6741">DERBY-6741</a></td><td>User code can get the ContextManager from an EmbedConnection</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6892">DERBY-6892</a></td><td>Create new SYSCS_IMPORT_TABLE_BULK procedure</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6737">DERBY-6737</a></td><td>CLOB retrieve exceptions after moving cursor around</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6890">DERBY-6890</a></td><td>ALTER TABLE DROP COLUMN corrupts secondary index collation information</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6733">DERBY-6733</a></td><td>Implement an MBean for monitoring caches</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6886">DERBY-6886</a></td><td>Fix links to CI test results</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6730">DERBY-6730</a></td><td>Cannot create a Lucene index if a key column's name is case-sensitive</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6885">DERBY-6885</a></td><td>Remove ReuseFactory</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6724">DERBY-6724</a></td><td>NPE if insert statement needs recompilation after having fired a trigger</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6884">DERBY-6884</a></td><td>SYSCS_IMPORT_TABLE_LOBS_FROM_EXTFILE can't import more than Integer.MAX_VALUE bytes of blob data</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6722">DERBY-6722</a></td><td>GenericStatementContext.cleanupOnError() needs protection from later errors during statement cleanup</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6883">DERBY-6883</a></td><td>Document the new SET GENERATED clause of ALTER TABLE introduced by DERBY-6882</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6720">DERBY-6720</a></td><td>Add derbyoptionaltools.jar to the maven artifacts we publish</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6882">DERBY-6882</a></td><td>Add functionality to ALTER TABLE: switch from GENERATED ALWAYS to GENERATED BY DEFAULT</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6719">DERBY-6719</a></td><td>Add derbyoptionaltools.jar to the class paths of the scripts in the bin directory</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6881">DERBY-6881</a></td><td>Test failures with JDK 9-ea b111</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6717">DERBY-6717</a></td><td>Policies with multiple SystemPermissions are not handled well</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6880">DERBY-6880</a></td><td>Update failing with java.sql.SQLDataException</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6714">DERBY-6714</a></td><td>RuntimeInfoTest failed with insufficient data from server</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6879">DERBY-6879</a></td><td>Engine deadlock between XA timeout handling and cleanupOnError</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6705">DERBY-6705</a></td><td>Triggers should not allow MERGE statements that reference temporary tables</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6875">DERBY-6875</a></td><td>Partially broken download pages</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6703">DERBY-6703</a></td><td>MERGE statement fails with NullPointerException if ON clause references non-existent column</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6870">DERBY-6870</a></td><td>Google Summer of Code 2016: Derby bug fixing</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6662">DERBY-6662</a></td><td>DatabaseMetaData.usesLocalFiles() returns true for in-memory databases</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6869">DERBY-6869</a></td><td>XMLXXETest fails in non-English locales</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6654">DERBY-6654</a></td><td>Require that generated code live in the org.apache.derby.exe package.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6868">DERBY-6868</a></td><td>Remove the dependency on Jakarta ORO</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6648">DERBY-6648</a></td><td>Application code should not be able to call ContextService.getContextOrNull()</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6866">DERBY-6866</a></td><td>Add URLs to Maven pom files</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6636">DERBY-6636</a></td><td>The public api of BaseDataFileFactory may allow blackhats to assume elevated privileges.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6864">DERBY-6864</a></td><td>RawDBReaderTest fails on Windows</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6635">DERBY-6635</a></td><td>OptimizerTracer.unloadTool() could be used to write garbage over Derby data files.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6860">DERBY-6860</a></td><td>Automatic download of junit.jar broken</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6632">DERBY-6632</a></td><td>Applications may be able to use StorageFactoryService to delete Derby databases and overwrite service.properties.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6852">DERBY-6852</a></td><td>Allow identity columns to cycle (as defined in SQL:2003)</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6631">DERBY-6631</a></td><td>FileMonitor can be used to elevate an application's privileges</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6847">DERBY-6847</a></td><td>Document SYSCS_UTIL.SYSCS_GET_DATABASE_NAME()</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6630">DERBY-6630</a></td><td>Applications can use JCECipherFactory to elevate their privileges to those granted to Derby</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6845">DERBY-6845</a></td><td>Document the rawDBReader optional tool</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6619">DERBY-6619</a></td><td>After silently swallowing SecurityExceptions, Derby can leak class loaders</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6828">DERBY-6828</a></td><td>Network Server don't start in czech localized enviroment due missing key DRDA_MissingNetworkJar.S</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6617">DERBY-6617</a></td><td>Silently swallowed SecurityExceptions may disable Derby features, including security features.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6752">DERBY-6752</a></td><td>AutoloadedDriver tries to load a non-existent class, AutoloadedDriver40</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6592">DERBY-6592</a></td><td>Update the version of ant which we tell new developers to use.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6726">DERBY-6726</a></td><td>NPE from trigger</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6569">DERBY-6569</a></td><td>NULLIF may return incorrect results if first operand calls non-deterministic function</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6725">DERBY-6725</a></td><td>Add a system function which returns the name of the database.</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6475">DERBY-6475</a></td><td>Update documentation for SYSTRIGGERS after DERBY-5866 changes</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6391">DERBY-6391</a></td><td>remove unneeded object creation in newException() calls in releases > 10.10</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-6414">DERBY-6414</a></td><td>Incorrect handling when using an UPDATE to SET an identity column to DEFAULT</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6334">DERBY-6334</a></td><td>Test harness security policy prevents running DatabaseClassLoadingTest twice</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-5466">DERBY-5466</a></td><td>Add support for SQL Standard statistics functions, such as STDDEV_POP, STDDEV_SAMP, VAR_POP, VAR_SAMP</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6136">DERBY-6136</a></td><td>Create a custom/optional tool for dumping the data in a corrupted database.</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-5165">DERBY-5165</a></td><td>Prepared XA transaction locks are not kept across DB restart</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5950">DERBY-5950</a></td><td>PlanExporter and SignatureChecker don't appear in the list of tools supported by derbyrun.</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-4057">DERBY-4057</a></td><td>Space is not reclaimed if transaction is rolled back</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5944">DERBY-5944</a></td><td>The hard-coded PlanExporter help message should be internationalized so that it can be translated</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-3888">DERBY-3888</a></td><td>ALTER TABLE ... ADD COLUMN cannot add identity columns</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5605">DERBY-5605</a></td><td>Calling Blob/Clob free() explicitly after implicit free throws exception in client driver</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-3195">DERBY-3195</a></td><td>Describe if default security manager & policy is installed or not on each of the mechanisms to start the network server.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5585">DERBY-5585</a></td><td>Improve error messages used when Derby can't find the class or method backing up a SQL routine or type</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-3005">DERBY-3005</a></td><td>Document possibility to specify method signature in EXTERNAL NAME when creating a procedure/function</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-4555">DERBY-4555</a></td><td>Expand SYSCS_IMPORT_TABLE to accept CSV file with header lines</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-2238">DERBY-2238</a></td><td>Example of ScalarSubquery in Derby Reference Manual is not ScalarSubquery</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-4091">DERBY-4091</a></td><td>Investigate "size_problem" column in MailJdbc terst</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-2051">DERBY-2051</a></td><td>CachedItem's comments and code are inconsistent wrt. syncronization</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-3181">DERBY-3181</a></td><td>isNullable on ResultSetMetaData from DatabaseMetaData.getBestRowIdentifier values are opposite when there is no rows in ResultSet vs. when there is a row.</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-691">DERBY-691</a></td><td>committed deleted row space reclamation may be missed if delete is actually an aborted insert.</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-1773">DERBY-1773</a></td><td>insertRow() and updateRow() fail with syntax error when column has an alias</td>
</tr>
<tr>
-<td><a href="https://issues.apache.org/jira/browse/DERBY-600">DERBY-600</a></td><td>Document that DB is booted in read-only mode if not able to create db.lck file</td>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-853">DERBY-853</a></td><td>ResultSetMetaData.getScale returns inconsistent values for DOUBLE type.</td>
</tr>
</table>
</div>
<h2>
<a name="Issues"></a>Issues</h2>
<div>
-<p>Compared with the previous release (10.11.1.1), Derby release 10.12.0.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
+<p>Compared with the previous release (10.12.1.1), Derby release 10.13.1.0 introduces the following new features and incompatibilities. These merit your special attention.</p>
<ul>
<li>
-<a href="#Note for DERBY-6807"><span>Note for DERBY-6807:
-XML parsing is now performed more securely.
-</span></a>
-</li>
-<li>
-<a href="#Note for DERBY-6648"><span>Note for DERBY-6648:
-Security policy files must grant a new permission to derby.jar,
-derbynet.jar, and derbyoptionaltools.jar.
-</span></a>
-</li>
-<li>
-<a href="#Note for DERBY-6414"><span>Note for DERBY-6414:
-UPDATE statements now accept DEFAULT as a valid value for identity columns.
+<a href="#Note for DERBY-6852"><span>Note for DERBY-6852:
+When a Derby SEQUENCE cycles, it now cycles to its minimum/maximum value rather than to its start value.
</span></a>
</li>
</ul>
<hr>
<h3>
-<a name="Note for DERBY-6807"></a>Note for DERBY-6807</h3>
+<a name="Note for DERBY-6852"></a>Note for DERBY-6852</h3>
<div>
+<!--
+ SUMMARIZE THE ISSUE. This is a one line, one sentence summary of the
+ issue. It serves as the title for the issue in the Issues section of
+ the full Release Notes.
-<h4>Summary of Change</h4>
-
-<p>
-XML parsing is now performed more securely.
-</p>
-
+ For instance:
-
-<h4>Symptoms Seen by Applications Affected by Change</h4>
-
-<p>
-If no Java Security Manager was in place, Derby applications were vulnerable
-to XML External Entity Expansion attacks (XXE attacks). Such attacks could
-result in disclosure of sensitive information that the application's user
-should not have been allowed to view.
-</p>
-
-<p>
-If a Derby application used the XmlVTI to parse XML documents, that application
-was also vulnerable if not protected by a Security Manager policy.
-</p>
-
-
-
-<h4>Incompatibilities with Previous Release</h4>
-
-<p>
-Applications which depended on the ability to have Derby's XML parser expand
-external entities may now be unable to use that functionality unless they
-correctly deploy a Java Security Manager policy authorizing the filesystem
-access performed by the entity expansion.
-</p>
-
-
-
-<h4>Rationale for Change</h4>
-
-<p>
-This change was made to prevent any unauthorized information disclosure by
-the XML parser.
-</p>
-
-
-<h4>Application Changes Required</h4>
-
-<p>
-For detailed information on configuring Derby with a Java Security Manager
-policy, please see <a href="http://db.apache.org/derby/docs/10.11/security/">
-the Derby Security Guide</a>.
-</p>
-
-
-
-</div>
-<hr>
-<h3>
-<a name="Note for DERBY-6648"></a>Note for DERBY-6648</h3>
-<div>
+ Applications may no longer open two InputStreams on the same ResultSet column.
+-->
<h4>Summary of Change</h4>
<p>
-Security policy files must grant a new permission to derby.jar,
-derbynet.jar, and derbyoptionaltools.jar.
+When a Derby SEQUENCE cycles, it now cycles to its minimum/maximum value rather than to its start value.
</p>
+<!--
+ DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
-<h4>Symptoms Seen by Applications Affected by Change</h4>
-
-<p>
-Unless this new permission is granted, databases won't boot, the
-network server won't come up, and the Lucene plugin won't be usable.
-If Derby runs under a SecurityManager whose policy file doesn't include
-this new permission, then users will see the following error when booting
-databases and servers and when using the Lucene plugin:
-</p>
+ 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.
+-->
-<pre>
-java.security.AccessControlException: access denied org.apache.derby.security.SystemPermission( "engine", "usederbyinternals" )
-</pre>
-
-
-<h4>Incompatibilities with Previous Release</h4>
-
-<p>
-When Derby is run under a Security Manager, databases and servers
-won't boot and the Lucene plugin won't be usable unless a new permission is added to the
-security policy.
-</p>
-
-
-<h4>Rationale for Change</h4>
-
-<p>
-Additional security has been added to Derby. When running under a
-Security Manager, embedding applications and database
-routines can no longer access certain sensitive internal structures.
-</p>
-
-
-<h4>Application Changes Required</h4>
-
-<p>
-Users who run Derby under a SecurityManager must edit the policy file
-and grant the following additional permission to derby.jar,
-derbynet.jar, and derbyoptionaltools.jar:
-</p>
-
-
-<pre>
- permission org.apache.derby.security.SystemPermission "engine", "usederbyinternals";
-</pre>
-
-
-</div>
-<hr>
-<h3>
-<a name="Note for DERBY-6414"></a>Note for DERBY-6414</h3>
-<div>
-
-
-<h4>Summary of Change</h4>
+<h4>Symptoms Seen by Applications Affected by Change</h4>
<p>
-UPDATE statements now accept DEFAULT as a valid value for identity columns.
-</p>
+In previous releases, when a Derby SEQUENCE cycled, it cycled to its start value. But now it cycles to its maximum or minimum value:
+<ul>
+<li>If the SEQUENCE has a positive increment, it cycles to its minimum value.</li>
+<li>If the SEQUENCE has a negative increment, it cycles to its maximum value.</li>
-<h4>Symptoms Seen by Applications Affected by Change</h4>
+</ul>
-<p>
-In previous releases of Derby, the following UPDATE statements would
-raise exceptions:
</p>
+<!--
+ DESCRIBE WHY THE CHANGE WAS MADE.
-<pre>
-create table t1( a int generated always as identity, b int );
-insert into t1( a, b ) values ( default, 100 );
-update t1 set a = default;
-ERROR 42Z23: Attempt to modify an identity column 'A'.
-
-create table t2( a int generated by default as identity, b int );
-insert into t2( a, b ) values ( default, 100 );
-update t2 set a = default;
-ERROR 23502: Column 'A' cannot accept a NULL value.
-</pre>
+ For instance:
-
-<p>
-The fix for DERBY-6414 makes the above two UPDATE statements work. Now
-those statements update the identity columns with their next generated values.
-</p>
+ The previous behavior violated the JDBC standard. The new behavior
+ is correct.
+-->
<h4>Rationale for Change</h4>
<p>
-The new behavior conforms to the SQL Standard.
+The new behaviour remains compliant with the SQL standard, but we believe it is more useful.
</p>
-
-
-<h4>Application Changes Required</h4>
-
<p>
-Applications no longer need to look for exceptions 42Z23 and 23502 when updating identity columns.
+Note that the new behavior is also used for the new CYCLE behavior of IDENTITY columns.
</p>
+
</div>
</div>
<h2>
<a name="Build Environment"></a>Build Environment</h2>
<div>
-<p>Derby release 10.12.0.0 was built using the following environment:</p>
+<p>Derby release 10.13.1.0 was built using the following environment:</p>
<ul>
<li>
-<b>Branch</b> - Source code came from the 10.12 branch.</li>
-<li>
-<b>Machine</b> - Mac OSX 10.7.5.</li>
+<b>Branch</b> - Source code came from the 10.13 branch.</li>
<li>
-<b>Ant</b> - Apache Ant(TM) version 1.9.2 compiled on July 8 2013.</li>
+<b>Machine</b> - Linux Fedora22 4.4.14.fc22.x86_64</li>
<li>
-<b>Compiler</b> - All classes were compiled by the javac from the 1.8.0-b132 JDK, Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode).</li>
+<b>Ant</b> - Apache Ant(TM) version 1.9.5 compiled on May 31 2015</li>
<li>
-<b>JSR 169</b> - Support for JSR 169 has been deprecated.</li>
+<b>Compiler</b> - All classes were compiled by OpenJDK Runtime Environment (build 1.8.0_91-b14)</li>
</ul>
</div>
<h2>
@@ -510,7 +341,7 @@ ensures that the file came from a certai
<a href="http://www.pgpi.org/">PGP</a> or
<a href="http://www.gnupg.org/">GPG</a>.
First download the Apache Derby
-<a href="http://svn.apache.org/repos/asf/db/derby/code/trunk/KEYS">KEYS</a>
+<a href="https://dist.apache.org/repos/dist/release/db/derby/KEYS">KEYS</a>
as well as the <code>asc</code> signature file for the particular
distribution. It is important that you get these files from the ultimate
trusted source - the main ASF distribution site, rather than from a mirror.
Modified: db/derby/code/branches/10.13/releaseSummary.xml
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.13/releaseSummary.xml?rev=1763095&r1=1763094&r2=1763095&view=diff
==============================================================================
--- db/derby/code/branches/10.13/releaseSummary.xml (original)
+++ db/derby/code/branches/10.13/releaseSummary.xml Sun Oct 2 19:22:40 2016
@@ -33,7 +33,7 @@ with real information.
E.g.: 10.2.1.7
-->
-<previousReleaseID>10.11.1.1</previousReleaseID>
+<previousReleaseID>10.12.1.1</previousReleaseID>
<!--
Identifier(s) of previously released versions. Any issue that was fixed in
@@ -47,10 +47,10 @@ with real information.
<buildInfo>
<!-- Machine environment. E.g.: Cygwin on Microsoft Windows XP Professional Version 2002 Service Pack 2. -->
- <machine>Mac OSX 10.7.5.</machine>
+ <machine>Linux Fedora22 4.4.14.fc22.x86_64</machine>
<!-- Ant version. E.g.: Apache Ant version 1.6.5 compiled on June 2 2005. -->
- <antVersion>Apache Ant(TM) version 1.9.2 compiled on July 8 2013.</antVersion>
+ <antVersion>Apache Ant(TM) version 1.9.5 compiled on May 31 2015</antVersion>
<!--
Say which compilers you used.
@@ -59,7 +59,7 @@ with real information.
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.
-->
- <compilers>All classes were compiled by the javac from the 1.8.0-b132 JDK, Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode).</compilers>
+ <compilers>All classes were compiled by OpenJDK Runtime Environment (build 1.8.0_91-b14)</compilers>
</buildInfo>
@@ -85,11 +85,10 @@ Derby functionality includes:
</ul>
<p>
-Support for Java SE 6 and Java SE 7 is being sunsetted. The 10.13 release family will not support those platforms. The 10.12 release family supports the following Java and JDBC versions:
+The 10.13 release family supports the following Java and JDBC versions:
</p>
<ul>
- <li>Java SE 6 and higher with JDBC 4.0, 4.1, and 4.2.</li>
- <li>Java SE 8 compact profile 2.</li>
+ <li>Java SE 8 </li>
</ul>
</overview>
@@ -100,15 +99,10 @@ This is a feature release. The following
</p>
<ul>
-
-<li><b>ALTER TABLE and identity columns</b> - The ALTER TABLE command can be used to add identity columns now. See the section on this statement in the Derby Reference Manual.</li>
-
-<li><b>Cache-monitoring MBean</b> - An MBean has been added for monitoring internal Derby caches. See the description of <i>CacheManagerMBean</i> in the "Introduction to the Derby MBeans" section of the Derby Server and Administration Guide.</li>
-
-<li><b>Optional Tool for Handling JSON Data</b> - An optional tool has been added for packing query results into JSON documents and for unpacking JSON documents into tabular result sets. See the section on the <i>simpleJson</i> optional tool in the Derby Tools and Utilities Guide.</li>
-
-<li><b>Statistics aggregates</b> - SQL Standard VAR_POP(), VAR_SAMP(), STDDEV_POP(), and STDDEV_SAMP() aggregates have been added. See the "Aggregates (set functions)" section in the Derby Reference Manual.</li>
-
+<li>DERBY-6136: tool for siphoning data out of corrupted databases</li>
+<li>DERBY-6725: system function which prints out the name of the current database</li>
+<li>DERBY-4555: system procedures to import CSV file with headers</li>
+<li>DERBY-6852: allow identity columns to cycle.</li>
</ul>
</newFeatures>