Author: lilywei Date: Tue Sep 14 18:15:29 2010 New Revision: 997028 URL: http://svn.apache.org/viewvc?rev=997028&view=rev Log: DERBY-4787: For 10.6.2.0 release, check-in the changes for release notes and release stuffs. Modified: db/derby/code/branches/10.6/RELEASE-NOTES.html db/derby/code/branches/10.6/java/build/org/apache/derbyBuild/GeneratorBase.java db/derby/code/branches/10.6/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java db/derby/code/branches/10.6/java/build/org/apache/derbyBuild/ReportParser.java db/derby/code/branches/10.6/releaseSummary.xml db/derby/code/branches/10.6/tools/ant/properties/release.properties db/derby/code/branches/10.6/tools/release/templates/releaseSummaryTemplate.xml Modified: db/derby/code/branches/10.6/RELEASE-NOTES.html URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.6/RELEASE-NOTES.html?rev=997028&r1=997027&r2=997028&view=diff ============================================================================== --- db/derby/code/branches/10.6/RELEASE-NOTES.html (original) +++ db/derby/code/branches/10.6/RELEASE-NOTES.html Tue Sep 14 18:15:29 2010 @@ -1,10 +1,10 @@ -Release Notes for Derby 10.6.1.0 +Release Notes for Derby 10.6.2.0

-Release Notes for Derby 10.6.1.0

+Release Notes for Derby 10.6.2.0
-

These notes describe the difference between Derby release 10.6.1.0 and the preceding release 10.5.3.0.

+

These notes describe the difference between Derby release 10.6.2.0 and the preceding release 10.6.1.0.


-Note for DERBY-3844

+Note for DERBY-4677
- -

Summary of Change

-Applications may no longer obtain a LOB object, or a Reader or an InputStream, from the same column more than once per row. + Unique nullable constraint may be disabled after compress or import operations on the table.

- -

Symptoms Seen by Applications Affected by Change

-Derby will throw an exception with SQLState XCL18 (carrying the message "Stream or LOB value cannot be retrieved more than once") when any of the following result set methods are invoked for the second time on a given column on a row: -

- + Prior to DERBY-4677 fix, the unique nullable constraint might have been disabled or violated after calls to + SYSCS_UTIL.SYSCS_COMPRESS_TABLE, or SYSCS_UTIL.SYSCS_IMPORT_TABLE. While the DERBY-4677 fix corrects the problem for new + indexes, it does not automatically repair damage to existing indexes. Applications using unique nullable indexes, (first + allowed in version 10.4.2.1) may find that duplicate rows exist, despite the table being created with the unique constraint. + In addition to the obvious problem of this being allowed, users may also see incorrect query results where one row is returned + even though there are multiple qualifying rows.

- -

Incompatibilities with Previous Release

+

Rationale for Change

-Applications which obtain two LOB objects from the same result set column on a row now fail. + The change fixed a serious bug that allowed duplicate rows despite a unique index. Users should upgrade and manually resolve + prior damage as described below.

- - -

Rationale for Change

+

Application Changes Required

-Obtaining several LOB objects from the same column causes resource management problems and intermittent errors (see DERBY-3844 for a description). The change is in line with the maximum portability statement found in the JavaDoc for java.sql.ResultSet. -

- - - +
  • 10.4.2.1 (build 956034)
  • +
  • 10.5.3.1 (build 955487)
  • -

    Application Changes Required

    +
  • 10.6.1.1 (build 955790)
  • -

    -Users must recode applications which obtain multiple LOB objects (java.sql.Blob or java.sql.Clob) on the same column. Note that for instance getCharacterStream(1) followed by getClob(1) will also raise the exception. + + The fix will not take care of duplicate rows that may have already made their way into the database. Such duplicate rows will + have to be handled by the user manually. The steps to take would be to drop and recreate unique nullable indexes. During + recreation, user might run into duplicate rows SQL exception. Such duplicate rows will have to be manually handled appropriately + by the user.

    @@ -2059,7 +260,7 @@ Users must recode applications which obt

    -Note for DERBY-2769

    +Note for DERBY-2925