Author: rhillegas Date: Fri Nov 12 19:57:35 2010 New Revision: 1034547 URL: http://svn.apache.org/viewvc?rev=1034547&view=rev Log: DERBY-4864: Attaching second draft of release notes. Modified: db/derby/code/trunk/RELEASE-NOTES.html db/derby/code/trunk/java/build/org/apache/derbyBuild/GeneratorBase.java db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java 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=1034547&r1=1034546&r2=1034547&view=diff ============================================================================== --- db/derby/code/trunk/RELEASE-NOTES.html (original) +++ db/derby/code/trunk/RELEASE-NOTES.html Fri Nov 12 19:57:35 2010 @@ -1,10 +1,10 @@ -Release Notes for Derby 10.7.1.0 +Release Notes for Apache Derby 10.7.1.0

-Release Notes for Derby 10.7.1.0

+Release Notes for Apache Derby 10.7.1.0
-

These notes describe the difference between Derby release 10.7.1.0 and the preceding release 10.6.2.1.

+

These notes describe the difference between Apache Derby release 10.7.1.0 and the preceding release 10.6.2.1.

@@ -105,6 +105,9 @@ This is a feature release. The following Issue IdDescription +DERBY-4899Refactor access to primary structures in AlterTableConstantAction + + DERBY-4898testGetURL test fails in nightly runs. @@ -234,6 +237,9 @@ This is a feature release. The following DERBY-4799IllegalArgumentException when generating error message on server +DERBY-4796Missing escape for apostrophes in many messages + + DERBY-4791LIKE operator optimizations and concatenation @@ -243,6 +249,9 @@ This is a feature release. The following DERBY-4777Different behavior in Client and Embedded modes when update on an invalid cursor +DERBY-4772Data truncation error with XPLAIN-functionality enabled + + DERBY-4767Detailed prompt for Error XCL16 is different between Client and Embed @@ -471,21 +480,30 @@ This is a feature release. The following
  • Note for DERBY-4786: -A shutdown request with no user credentials to a 10.3 and earlier servers from a newer client will give multiple messages on both server and client side. +A shutdown request with no user credentials to a 10.3 (or earlier) +server from a newer client will give multiple messages on both the server and client sides.

  • Note for DERBY-4777: -When update on an invalid cursor in Client mode, 'ERROR 42X30' will be thrown instead of 'ERROR XJ202'. +When a network client attempts to update through an invalid cursor, +Derby now throws 'ERROR 42X30' instead of 'ERROR XJ202'. +

    +
    +
  • +
  • + +

    Note for DERBY-4772: +Column types in the XPLAIN tables changed to accommodate more data.

  • Note for DERBY-4577: - An UPDATE statement may fail with the following error: "ERROR nospc: nospc.U" + UPDATE statements should not raise the following error: "ERROR nospc: nospc.U"

  • @@ -522,7 +540,8 @@ cursor is holdable.

    Summary of Change

    -A shutdown request with no user credentials to a 10.3 and earlier servers from a newer client will give multiple messages on both server and client side. +A shutdown request with no user credentials to a 10.3 (or earlier) +server from a newer client will give multiple messages on both the server and client sides.

    @@ -540,20 +559,33 @@ A shutdown request with no user credenti

    Symptoms Seen by Applications Affected by Change

    -A shutdown request from a 10.4 and higher client with no user credentials to a 10.3 and earlier server will show following messages on server side(Note that the version info about the product will change depending on the release being used for the server).
    + +

    +A shutdown request from a 10.4 (or higher) client with no user +credentials to a 10.3 (or earlier) server shows the following messages +on the server side. (Note that the version info about the product +changes depending on the release being used for the server.) +

    + + +
     java.lang.Throwable: DRDA_UnknownProtocol.S, 2
    -
    Execution failed because of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM;CODPNT arg = 0; Error Code Value = 1. Plaintext connection attempt from an SSL enabled client? -
    Apache Derby Network Server - 10.3.3.1 - (1) shutdown at {2} -
    +
    + + +

    +Messages on the client side appear as follows. (Note that the version +info about the product changes depending on the release being used +for the client.) +

    -
    -Messages on client side will be as follows(Note that the version info about the product will change depending on the release being used for the client). -
    + +
     Invalid reply header from network server: Invalid string . Plaintext connection attempt to an SSL enabled server?
    -
    -Apache Derby Network Server - 10.7.0.0 alpha - (1) shutdown +Apache Derby Network Server - 10.7.1.0 - (1) shutdown +
    +

    Rationale for Change

    -10.3 and earlier versions do not support shutdown command with credentials. That command was introduced in 10.4 at a different protocol level(2). When a shutdown is sent by a 10.4 or higher client, it is sent at protocol level 2 which is not recognized by 10.3 and earlier versions. Because of this, a 10.4 and higher client can't shutdown a 10.3 or lower server. With DERBY-4786, the 10.4 and higher version clients will first try the shutdown at level 2 protocol and if that does not succeed, then it will send the shutdown at level 1 protocol thus allowing 10.4 and higher versions to shutdown 10.3 and lower version servers. +10.3 (and earlier) versions do not support shutdown commands with +credentials. The credential-bearing shutdown command was introduced in +10.4 and requires network +protocol level 2. +10.3 and earlier versions understand protocol level 1 and do not recognize the credential-bearing +shutdown command. Because of this, a 10.4 (or higher) client +can't shutdown a 10.3 (or lower) server. With DERBY-4786, a 10.7 client +will first try the shutdown at protocol level 2. If that does not +succeed, then the 10.7 client will send the shutdown at protocol level 1. +This fix has been backported to the 10.4, 10.5, and 10.6 +branches also. Future releases on those branches will enjoy this ability to +successfully shutdown 10.3 (and earlier) servers.

    @@ -591,7 +635,115 @@ Apache Derby Network Server - 10.7.0.0 a

    Summary of Change

    -When update on an invalid cursor in Client mode, 'ERROR 42X30' will be thrown instead of 'ERROR XJ202'. +When a network client attempts to update through an invalid cursor, +Derby now throws 'ERROR 42X30' instead of 'ERROR XJ202'. +

    + + + + + +

    Symptoms Seen by Applications Affected by Change

    + +

    +In previous releases, Derby threw 'ERROR XJ202' when a network client +tried to update through a closed or nonexistent cursor. +For a cursor named "JDK4", the detailed message was "ERROR XJ202: Invalid cursor name 'JDK4'." +If you are running 10.7, however, Derby now throws 'ERROR 42X30' +instead, and the detailed message is "ERROR 42X30: Cursor 'JDK4' not found. Verify that autocommit is OFF." +

    + + +

    +From now on, DERBY performs identically in Client and Embedded modes +when you attempt to update through a closed or nonexistent cursor. +

    + + + + + +

    Incompatibilities with Previous Release

    + +

    +Applications may fail if they expect 'ERROR XJ202' to be thrown +in this situation. +

    + + + + + +

    Rationale for Change

    + +

    +This change was made so that the Client and Embedded behavior would be similar. +

    + + + + + +

    Application Changes Required

    + +

    +If applications need to track updates through invalid cursors, those +applications should look for 'ERROR 42X30' regardless of whether they +run in Client or Embedded mode. +

    + + + + +
    +

    +Note for DERBY-4772

    +
    + + + + +

    Summary of Change

    + +

    +Column types in the XPLAIN tables changed to accommodate more data.

    @@ -611,12 +763,7 @@ When update on an invalid cursor in Clie

    Symptoms Seen by Applications Affected by Change

    -In previous releases, when an update on an invalid cursor (closed or nonexistent) is attempted in Client mode, -'ERROR XJ202' will be thrown. For instance, if the cursor name is "JDK4", the detailed message is "ERROR XJ202: Invalid cursor name 'JDK4'." -While, in the current release, 'ERROR 42X30' will be thrown, and the detailed message is "ERROR 42X30: Cursor 'JDK4' not found. Verify that autocommit is OFF." -
    -From now on, DERBY will perform the same in both Client and Embedded modes -when update on an invalid cursor (closed or nonexistent). +None.

    @@ -633,8 +780,7 @@ when update on an invalid cursor (closed

    Incompatibilities with Previous Release

    -In previous releases, applications that expect 'ERROR XJ202' is thrown -when update on an invalid cursor (closed or nonexistent) in Client mode will fail. +None, but keeping the old table definitions for the XPLAIN tables may result in data truncation errors (see DERBY-4772 and DERBY-4673).

    @@ -651,9 +797,7 @@ when update on an invalid cursor (closed

    Rationale for Change

    -'ERROR XJ202' should just be used to show the 'name' of a cursor is invalid, -just like using in Statement.setCursorName(), but not the cursor itself is invalid. -If a cursor itself is not invalid, a 'ERROR 42X30' is more suitable. This behavior should be the same for Derby Client and Embedded. +Amount of recorded data was too large to fit into the old column definitions.

    @@ -670,8 +814,7 @@ If a cursor itself is not invalid, a 'ER

    Application Changes Required

    -When update on an invalid cursor (closed or nonexistent) in Client mode, -'ERROR 42X30' should be expected. +It is recommended to drop existing XPLAIN tables and have them recreated with the new table definitions. This can be done by disabling the XPLAIN feature, dropping the tables, and then enable the XPLAIN feature again. Alternatively, if you want to keep existing data, specify a different schema to save XPLAIN data in.

    @@ -686,7 +829,7 @@ When update on an invalid cursor (closed

    Summary of Change

    - An UPDATE statement may fail with the following error: "ERROR nospc: nospc.U" + UPDATE statements should not raise the following error: "ERROR nospc: nospc.U"

    @@ -694,10 +837,10 @@ When update on an invalid cursor (closed

    Symptoms Seen by Applications Affected by Change

    - An UPDATE statement of a row which spans multiple pages could fail with + An UPDATE of a row which spans multiple pages can fail, raising "ERROR nospc: nospc.U". This error should never be returned to the client. - The error is very timing and data dependent, and only has been encountered - in a few applications. + The error is very timing and data dependent, and has been encountered + in only a few applications.

    @@ -707,8 +850,8 @@ When update on an invalid cursor (closed

    Rationale for Change

    - UPDATES of rows failed in some cases, returning an error that should never - be seen by clients of the software. + UPDATES of rows may fail in some cases, returning this error +which clients should never see.

    @@ -716,11 +859,13 @@ When update on an invalid cursor (closed

    Application Changes Required

    - The fix insures that all rows inserted after the fix will not get this error. - To insure that updates of existing rows will not see this error one should - run the SYSCS_UTIL.SYSCS_COMPRESS_TABLE() system procedure on the table. - It is also ok to wait and see if the error is encountered and run the - compress utility as needed on tables that encounter the error. + After applying the fix, clients should not see this error. + To ensure that updates of existing rows no longer see this error, + run the SYSCS_UTIL.SYSCS_COMPRESS_TABLE() system procedure on your tables. +You may want to defensively +compress all of your tables. Alternatively, + it is also ok to wait and see if the error occurs and then only compress + the tables that encounter the error.

    Modified: db/derby/code/trunk/java/build/org/apache/derbyBuild/GeneratorBase.java URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/build/org/apache/derbyBuild/GeneratorBase.java?rev=1034547&r1=1034546&r2=1034547&view=diff ============================================================================== --- db/derby/code/trunk/java/build/org/apache/derbyBuild/GeneratorBase.java (original) +++ db/derby/code/trunk/java/build/org/apache/derbyBuild/GeneratorBase.java Fri Nov 12 19:57:35 2010 @@ -176,7 +176,7 @@ public class GeneratorBase extends Task protected void buildDelta(Element parent) throws Exception { String deltaStatement = - "These notes describe the difference between Derby release " + + "These notes describe the difference between Apache Derby release " + releaseID + " and the preceding release " + previousReleaseID + "."; Modified: db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java?rev=1034547&r1=1034546&r2=1034547&view=diff ============================================================================== --- db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java (original) +++ db/derby/code/trunk/java/build/org/apache/derbyBuild/ReleaseNotesGenerator.java Fri Nov 12 19:57:35 2010 @@ -214,7 +214,7 @@ public class ReleaseNotesGenerator exten * Start the RELEASE_NOTES html docment. */ private void beginOutput() throws Exception { - String titleText = "Release Notes for Derby " + releaseID; + String titleText = "Release Notes for Apache Derby " + releaseID; Element html = outputDoc.createElement(HTML); Element title = createTextElement(outputDoc, "title", titleText); Element body = outputDoc.createElement(BODY); Modified: db/derby/code/trunk/releaseSummary.xml URL: http://svn.apache.org/viewvc/db/derby/code/trunk/releaseSummary.xml?rev=1034547&r1=1034546&r2=1034547&view=diff ============================================================================== --- db/derby/code/trunk/releaseSummary.xml (original) +++ db/derby/code/trunk/releaseSummary.xml Fri Nov 12 19:57:35 2010 @@ -115,7 +115,7 @@ This is a feature release. The following
  • Query plan browsing - A new PlanExporter tool helps developers visualize query plans better.
  • -
  • Unicode database names - Remote clients can now use database names which include unicode characters outside the ascii codeset.
  • +
  • Unicode database names - Remote clients can now use database names which include Unicode characters outside the ASCII codeset.