db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@apache.org
Subject svn commit: r647759 - /db/derby/code/branches/10.4/RELEASE-NOTES.html
Date Mon, 14 Apr 2008 12:26:46 GMT
Author: dyre
Date: Mon Apr 14 05:26:40 2008
New Revision: 647759

URL: http://svn.apache.org/viewvc?rev=647759&view=rev
Log:
10.4 release preparations: Check in new RELEASE_NOTES.html 

Modified:
    db/derby/code/branches/10.4/RELEASE-NOTES.html

Modified: db/derby/code/branches/10.4/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.4/RELEASE-NOTES.html?rev=647759&r1=647758&r2=647759&view=diff
==============================================================================
--- db/derby/code/branches/10.4/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.4/RELEASE-NOTES.html Mon Apr 14 05:26:40 2008
@@ -1,10 +1,10 @@
 <html>
-<title>Release Notes for Derby 10.4.1.1</title>
+<title>Release Notes for Derby 10.4.1.2</title>
 <body>
 <h1>
-<a name="Release Notes for Derby 10.4.1.1"></a>Release Notes for Derby 10.4.1.1</h1>
+<a name="Release Notes for Derby 10.4.1.2"></a>Release Notes for Derby 10.4.1.2</h1>
 <blockquote>
-<p>These notes describe the difference between Derby release 10.4.1.1 and the preceding
release 10.3.2.1.</p>
+<p>These notes describe the difference between Derby release 10.4.1.2 and the preceding
release 10.3.2.1.</p>
 </blockquote>
 <ul>
 <li>
@@ -109,7 +109,7 @@
 <h2>
 <a name="Bug Fixes"></a>Bug Fixes</h2>
 <blockquote>
-<p>The following issues are addressed by Derby release 10.4.1.1. These issues are not
addressed in the preceding 10.3.2.1 release.</p>
+<p>The following issues are addressed by Derby release 10.4.1.2. These issues are not
addressed in the preceding 10.3.2.1 release.</p>
 <table border="2">
 <tr>
 <td><b>Issue Id</b></td><td><b>Description</b></td>
@@ -118,6 +118,9 @@
 <td><a href="http://issues.apache.org/jira/browse/DERBY-3589">DERBY-3589</a></td><td>AllocPage.createPage()
doesn't initialize minimumRecordSize correctly</td>
 </tr>
 <tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3571">DERBY-3571</a></td><td>LOB
locators are not released if the LOB columns are not accessed by the client</td>
+</tr>
+<tr>
 <td><a href="http://issues.apache.org/jira/browse/DERBY-3538">DERBY-3538</a></td><td>NullPointerException
during execution for query with LEFT OUTER JOIN whose inner table selects all constants.</td>
 </tr>
 <tr>
@@ -139,6 +142,9 @@
 <td><a href="http://issues.apache.org/jira/browse/DERBY-3366">DERBY-3366</a></td><td>Various
formatting erros in L10N property files</td>
 </tr>
 <tr>
+<td><a href="http://issues.apache.org/jira/browse/DERBY-3354">DERBY-3354</a></td><td>Select
from large lob table with embedded gives OutOfMemoryError</td>
+</tr>
+<tr>
 <td><a href="http://issues.apache.org/jira/browse/DERBY-3352">DERBY-3352</a></td><td>truncateTable
crashed, Caused by: java.lang.NullPointerException</td>
 </tr>
 <tr>
@@ -274,9 +280,6 @@
 <td><a href="http://issues.apache.org/jira/browse/DERBY-2935">DERBY-2935</a></td><td>DDMReader.readLengthAndCodePoint()
decodes long integer incorrectly</td>
 </tr>
 <tr>
-<td><a href="http://issues.apache.org/jira/browse/DERBY-2892">DERBY-2892</a></td><td>Closing
a resultset after retrieving a large &gt; 32665 bytes value with Network Server does not
release locks</td>
-</tr>
-<tr>
 <td><a href="http://issues.apache.org/jira/browse/DERBY-2815">DERBY-2815</a></td><td>ij
doesn't start with J2ME / JSR169 / weme6.1 because attempting to find java.sql.Driver if ij.protocol
property is specified</td>
 </tr>
 <tr>
@@ -323,7 +326,7 @@
 <h2>
 <a name="Issues"></a>Issues</h2>
 <blockquote>
-<p>Compared with the previous release (10.3.2.1), Derby release 10.4.1.1 introduces
the following new features and incompatibilities. These merit your special attention.</p>
+<p>Compared with the previous release (10.3.2.1), Derby release 10.4.1.2 introduces
the following new features and incompatibilities. These merit your special attention.</p>
 <ul>
 <li>
 <a href="#Note for DERBY-3585">
@@ -364,14 +367,6 @@
 </a>
 </li>
 <li>
-<a href="#Note for DERBY-2892">
-<p>Note for DERBY-2892: 
-  DERBY-2892 fixes the bug: "Closing a resultset after retrieving a large &gt; 32665
bytes value with Network Server does not release locks." The fix  changes the JDBC retrieval
of BLOB/CLOB columns release locks and the lob locator after calls to ResultSet.getString(),
ResultSet.getCharacterStream(), ResultSet.getBytes() or ResultSet.getBinaryStream().  Previously
locks would remain held after these calls.  Note: Locks will still be held for calls to ResultSet.getClob()
or ResultSet.getBlob().  The user must call free() or commit or rollback the transation to
release these locks.
-
-</p>
-</a>
-</li>
-<li>
 <a href="#Note for DERBY-2351">
 <p>Note for DERBY-2351: An ORDER BY clause of a DISTINCT query which specifies to order
by a
 column which was not in the DISTINCT list is now rejected, because the
@@ -1049,103 +1044,6 @@
 </blockquote>
 <hr>
 <h3>
-<a name="Note for DERBY-2892"></a>Note for DERBY-2892</h3>
-<blockquote>
-
-<!-- 
-  SUMMARIZE THE ISSUE. This is a one line summary of the issue.
-
-  For instance:
-
-  Applications may no longer open two InputStreams on the same ResultSet column.
--->
-
-
-<h4>Summary of Change</h4>
-
-<p>
-  DERBY-2892 fixes the bug: "Closing a resultset after retrieving a large &gt; 32665
bytes value with Network Server does not release locks." The fix  changes the JDBC retrieval
of BLOB/CLOB columns release locks and the lob locator after calls to ResultSet.getString(),
ResultSet.getCharacterStream(), ResultSet.getBytes() or ResultSet.getBinaryStream().  Previously
locks would remain held after these calls.  Note: Locks will still be held for calls to ResultSet.getClob()
or ResultSet.getBlob().  The user must call free() or commit or rollback the transation to
release these locks.
-
-</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>
-
-  Users will no longer see locks being held for calls to ResultSet.getString(), ResultSet.getCharacterStream(),
ResultSet.getBytes() or ResultSet.getBinaryStream(). 
-
-</p>
-
-
-<!-- 
-  OPTIONAL: DESCRIBE INCOMPATIBILITIES WITH PREVIOUS RELEASE, IF ANY.
-
-  For instance:
-
-  Applications which open two InputStreams on the ResultSet column now
-  fail.
--->
-
-
-<h4>Incompatibilities with Previous Release</h4>
-
-<p>
-As part of the implementation of this change, BLOB/CLOB columns can be retrieved only once
through JDBC, for each row. For example, if the user calls ResultSet.getString() on a BLOB
or CLOB column, they cannot make a subsequent call to ResultSet.getCharacterStream()  for
the same column on the same row. An Exception will be thrown if this is attempted. 
-</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>
-In order to ensure the proper locking behavior, the change to throw an exception when a BLOB/CLOB
column is retrieved more than once for a row was required. 
-</p>
-
-
-<!-- 
-  OPTIONAL: DESCRIBE HOW TO REVERT TO THE PREVIOUS BEHAVIOR OR
-  OTHERWISE AVOID THE INCOMPATIBILITIES INTRODUCED BY THIS CHANGE.
-
-  For instance:
-
-  Users must recode applications which open multiple streams on the same column.
--->
-
-
-<h4>Application Changes Required</h4>
-
-<p>
-Users should retrieve the field only once and save the value for reuse, rather than making
multiple calls to ResultSet.getXXXX methods.
-</p>
-
-
-
-</blockquote>
-<hr>
-<h3>
 <a name="Note for DERBY-2351"></a>Note for DERBY-2351</h3>
 <blockquote>
 <!-- 
@@ -1401,7 +1299,7 @@
 <h2>
 <a name="Build Environment"></a>Build Environment</h2>
 <blockquote>
-<p>Derby release 10.4.1.1 was built using the following environment:</p>
+<p>Derby release 10.4.1.2 was built using the following environment:</p>
 <ul>
 <li>
 <b>Branch</b> - Source code came from the 10.4 branch.</li>



Mime
View raw message