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 rh...@apache.org on 2011/03/15 15:01:12 UTC

svn commit: r1081788 - in /db/derby/code/trunk: RELEASE-NOTES.html releaseSummary.xml

Author: rhillegas
Date: Tue Mar 15 14:01:12 2011
New Revision: 1081788

URL: http://svn.apache.org/viewvc?rev=1081788&view=rev
Log:
DERBY-5016: 7th version of the 10.8.1 release notes.

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

Modified: db/derby/code/trunk/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/RELEASE-NOTES.html?rev=1081788&r1=1081787&r2=1081788&view=diff
==============================================================================
--- db/derby/code/trunk/RELEASE-NOTES.html (original)
+++ db/derby/code/trunk/RELEASE-NOTES.html Tue Mar 15 14:01:12 2011
@@ -93,7 +93,11 @@ change in a future release in the highly
 	
 
 <li>
-<b>Improved interrupt handling </b> - Interrupting connection threads no longer crashes the Derby engine.</li>
+<b>Automatic calculation of index statistics</b> - Applications can ask Derby to automatically refresh statistics which help Derby pick better query plans.</li>
+	
+
+<li>
+<b>Improved interrupt handling</b> - Interrupting connection threads no longer crashes the Derby engine.</li>
 	
 
 <li>
@@ -120,6 +124,9 @@ change in a future release in the highly
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5124">DERBY-5124</a></td><td>NPE or assert failure printed when dropping table while statistics are written out</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-5119">DERBY-5119</a></td><td>testQualifiers(org.apache.derbyTesting.functionTests.tests.store.AccessTest)java.sql.SQLException: Table/View 'FOO' already exists in Schema 'APP'.</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-5117">DERBY-5117</a></td><td>ParameterMetaDataJdbc30Test fails with "'DUMMYINT' is not recognized as a function or procedure"</td>
 </tr>
 <tr>
@@ -501,6 +508,12 @@ change in a future release in the highly
 <td><a href="https://issues.apache.org/jira/browse/DERBY-4573">DERBY-4573</a></td><td>Reference manual is unclear about the purpose of REFERENCEDCOLUMNS in SYSTRIGGERS table.</td>
 </tr>
 <tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-4540">DERBY-4540</a></td><td>'AssertionFailedError' in 'store.AccessTest.testCS4595B_UniqueIndex(AccessTest.java:1729)' on SUSE Linux / IBM JIT  - r9</td>
+</tr>
+<tr>
+<td><a href="https://issues.apache.org/jira/browse/DERBY-3980">DERBY-3980</a></td><td>Conflicting select then update with REPEATABLE_READ gives lock timeout instead of deadlock</td>
+</tr>
+<tr>
 <td><a href="https://issues.apache.org/jira/browse/DERBY-3258">DERBY-3258</a></td><td>'Unexpected row count: expected:&lt;0&gt; but was:&lt;3&gt;' in testReleaseCompileLocks</td>
 </tr>
 <tr>

Modified: db/derby/code/trunk/releaseSummary.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/releaseSummary.xml?rev=1081788&r1=1081787&r2=1081788&view=diff
==============================================================================
--- db/derby/code/trunk/releaseSummary.xml (original)
+++ db/derby/code/trunk/releaseSummary.xml Tue Mar 15 14:01:12 2011
@@ -120,7 +120,9 @@ This is a feature release. The following
 the pre-GA OpenJDK 7 build 131 available at http://download.java.net/jdk7/ on March 3, 2011. Derby's implementation of these interfaces may
 change in a future release in the highly unlikely event that the actual GA version of these interfaces changes.</li>
 	
-<li><b>Improved interrupt handling </b> - Interrupting connection threads no longer crashes the Derby engine.</li>
+<li><b>Automatic calculation of index statistics</b> - Applications can ask Derby to automatically refresh statistics which help Derby pick better query plans.</li>
+	
+<li><b>Improved interrupt handling</b> - Interrupting connection threads no longer crashes the Derby engine.</li>
 	
 <li><b>MAX optimization</b> - On indexed tables, MAX queries run faster in more cases.</li>