db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r1456972 - /db/derby/code/trunk/RELEASE-NOTES.html
Date Fri, 15 Mar 2013 14:44:56 GMT
Author: rhillegas
Date: Fri Mar 15 14:44:56 2013
New Revision: 1456972

URL: http://svn.apache.org/r1456972
Log:
DERBY-6104: Check in third draft of release notes for 10.10.1.

Modified:
    db/derby/code/trunk/RELEASE-NOTES.html

Modified: db/derby/code/trunk/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/RELEASE-NOTES.html?rev=1456972&r1=1456971&r2=1456972&view=diff
==============================================================================
--- db/derby/code/trunk/RELEASE-NOTES.html (original)
+++ db/derby/code/trunk/RELEASE-NOTES.html Fri Mar 15 14:44:56 2013
@@ -128,6 +128,9 @@ This is a feature release. The following
 </th><th>Description</th>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6106">DERBY-6106</a></td><td>Remove
the outdated Japanese and Portuguese docs</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-6100">DERBY-6100</a></td><td>Upgrade
tests fail on compact2</td>
 </tr>
 <tr>
@@ -137,6 +140,12 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-6097">DERBY-6097</a></td><td>Management
test suite fails when JMX is not supported</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6094">DERBY-6094</a></td><td>Derby
ignores DriverManager.setLoginTimeout()</td>
+</tr>
+<tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6089">DERBY-6089</a></td><td>CallableStatement#registerOutParameter
on client lacks check of legal types.</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-6088">DERBY-6088</a></td><td>PreparedStatementTest42
lacks "fail" call when operation unexpectedly succeeds</td>
 </tr>
 <tr>
@@ -266,6 +275,9 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-6001">DERBY-6001</a></td><td>ErrorMessageTest
assert failure: Only one of the waiters should be aborted</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-6000">DERBY-6000</a></td><td>Implement
support for JDBC 4.2</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5999">DERBY-5999</a></td><td>Improve
documentation on index key lengths</td>
 </tr>
 <tr>
@@ -434,6 +446,9 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5880">DERBY-5880</a></td><td>Move
java.sql.Wrapper implementations to base classes in embedded driver</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5878">DERBY-5878</a></td><td>Add
message argument names, as comments, to English message file produced by MessageBuilder.</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5877">DERBY-5877</a></td><td>Prune
the brokered class tree</td>
 </tr>
 <tr>
@@ -590,6 +605,9 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5740">DERBY-5740</a></td><td>Remove
unsued code in AlterTableConstantaction.columnDroppedAndTriggerDependencies</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5632">DERBY-5632</a></td><td>Logical
deadlock happened when freezing/unfreezing the database</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5622">DERBY-5622</a></td><td>Reduce
the chance for hash collisions when checking bootPassword at boot time and when changing password.</td>
 </tr>
 <tr>
@@ -605,6 +623,9 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5462">DERBY-5462</a></td><td>ant
release needs to accommodate for different ant executables on different systems</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5460">DERBY-5460</a></td><td>ant
release should allow local.properties to exist</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5425">DERBY-5425</a></td><td>Updateable
holdable ResultSet terminates early after 65638 updates</td>
 </tr>
 <tr>
@@ -629,6 +650,12 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5213">DERBY-5213</a></td><td>Write
tests to verify the interaction of TRUNCATE TABLE and online backup</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-4841">DERBY-4841</a></td><td>Improve
projecthelp for the top level Derby build script</td>
+</tr>
+<tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-4811">DERBY-4811</a></td><td>Remove
unused clean targets from the Derby build.</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-4323">DERBY-4323</a></td><td>test
failure in lang.ErrorMessageTest with IBM iseries IBM 1.5</td>
 </tr>
 <tr>
@@ -665,6 +692,9 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-2601">DERBY-2601</a></td><td>Server
SQLException error codes are not returned to client</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-2572">DERBY-2572</a></td><td>Write
a master script which creates a release branch.</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-2516">DERBY-2516</a></td><td>Network
Client allows execution of callable statement when one of the parameters is not set</td>
 </tr>
 <tr>
@@ -674,6 +704,9 @@ This is a feature release. The following
 <td><a href="https://issues.apache.org/jira/browse/DERBY-2076">DERBY-2076</a></td><td>Rewrite
junitTests/derbyNet/CompatibilityTest to conform to current JUnit usage</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-1982">DERBY-1982</a></td><td>Remove
support for JDK 1.3 in 10.3 and onwards</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-1721">DERBY-1721</a></td><td>DOCS
- Remove duplicate information in Dev Guide re: Encryption</td>
 </tr>
 <tr>
@@ -693,11 +726,6 @@ This is a feature release. The following
 <p>Compared with the previous release (10.9.1.0), Derby release 10.10.0.0 introduces
the following new features and incompatibilities. These merit your special attention.</p>
 <ul>
 <li>
-<a href="#Note for DERBY-5996"><span>Note for DERBY-5996: 
-Hard upgrade to Derby 10.10 will create readme files named "README_DO_NOT_TOUCH_FILES.txt".
The content of these files warn users against touching any files in the database directories.
-</span></a>
-</li>
-<li>
 <a href="#Note for DERBY-5969"><span>Note for DERBY-5969: 
 A SQLWarning is now raised if you try to change the encryption state
 of an already booted database.
@@ -715,6 +743,11 @@ same query block.
 </span></a>
 </li>
 <li>
+<a href="#Note for DERBY-5578"><span>Note for DERBY-5578: 
+A new system procedure helps correct misbehaving triggers and metadata queries.
+</span></a>
+</li>
+<li>
 <a href="#Note for DERBY-5546"><span>Note for DERBY-5546: 
 ResultSet#updateBigDecimal on a REAL or DOUBLE column now does underflow checking.
 </span></a>
@@ -736,68 +769,6 @@ lifted.  
 </ul>
 <hr>
 <h3>
-<a name="Note for DERBY-5996"></a>Note for DERBY-5996</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.
-
-  For instance:
-
-  Applications may no longer open two InputStreams on the same ResultSet column.
--->
-
-
-<h4>Summary of Change</h4>
-
-<p>
-Hard upgrade to Derby 10.10 will create readme files named "README_DO_NOT_TOUCH_FILES.txt".
The content of these files warn users against touching any files in the database directories.
-</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>
-Adding/editing/deleting any of the database files can leave the database in a non-recoverable
state. 
-</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>
-Unintentional editing of the database files by the users can leave the database in a non-recoverable
state. To caution users against such an action, a hard upgrade to Derby 10.10 will create
three readme files which will warn users against touching any files in the various database
directories. The locations of the readme files are 1)the top database directory 2)the "seg0"
directory and 3)the log directory.
-</p>
-
-
-
-</div>
-<hr>
-<h3>
 <a name="Note for DERBY-5969"></a>Note for DERBY-5969</h3>
 <div>
 
@@ -1180,6 +1151,78 @@ where T.A = S.A;
 </div>
 <hr>
 <h3>
+<a name="Note for DERBY-5578"></a>Note for DERBY-5578</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.
+
+  For instance:
+
+  Applications may no longer open two InputStreams on the same ResultSet column.
+-->
+
+
+<h4>Summary of Change</h4>
+
+<p>
+A new system procedure helps correct misbehaving triggers and metadata queries.
+</p>
+
+
+<!-- 
+  DESCRIBE WHAT IT IS THAT THE USER ACTUALLY SEES WHEN THE PROBLEM OCCURS.
+
+  For instance:
+
+  In the previous release, applications were able to open two
+  InputStreams on the same column. Depending on how these streams
+  interacted, the value siphoned out of the column was erratic. Now
+  Derby raises a SQLException when the application attempts to create
+  the second InputStream.
+-->
+
+
+<h4>Symptoms Seen by Applications Affected by Change</h4>
+
+<p>
+Applications did not have a way to recompile metadata queries and
+triggers if a Derby bug made the queries and triggers behave
+incorrectly. If you suspect that your metadata queries or triggers are
+misbehaving, you may be able to fix their behavior by calling the
+following new system procedure:
+</p>
+
+
+<pre>
+CALL SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS()
+</pre>
+
+
+<!-- 
+  DESCRIBE WHY THE CHANGE WAS MADE.
+
+  For instance:
+
+  The previous behavior violated the JDBC standard. The new behavior
+  is correct.
+-->
+
+
+<h4>Rationale for Change</h4>
+
+<p>
+The new SYSCS_UTIL.SYSCS_INVALIDATE_STORED_STATEMENTS procedure was
+introduced as a workaround when Derby bugs break metadata queries and triggers.
+</p>
+
+
+
+</div>
+<hr>
+<h3>
 <a name="Note for DERBY-5546"></a>Note for DERBY-5546</h3>
 <div>
 



Mime
View raw message