Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 77424 invoked from network); 21 Dec 2007 22:31:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Dec 2007 22:31:54 -0000 Received: (qmail 55265 invoked by uid 500); 21 Dec 2007 22:31:43 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 55245 invoked by uid 500); 21 Dec 2007 22:31:43 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 55234 invoked by uid 99); 21 Dec 2007 22:31:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 14:31:43 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 22:31:35 +0000 Received: by eris.apache.org (Postfix, from userid 65534) id 9A7101A9858; Fri, 21 Dec 2007 14:31:02 -0800 (PST) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r606336 [7/8] - in /db/derby/site/trunk: build/ build/site/ build/site/dev/ build/site/images/ build/site/integrate/ build/site/integrate/plugin_help/ build/site/manuals/ build/site/papers/ build/site/papers/DerbyTut/ build/site/releases/ b... Date: Fri, 21 Dec 2007 22:30:44 -0000 To: derby-commits@db.apache.org From: fuzzylogic@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20071221223102.9A7101A9858@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: db/derby/site/trunk/build/site/quick_start.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/quick_start.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/quick_start.html (original) +++ db/derby/site/trunk/build/site/quick_start.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby: Quick Start @@ -16,49 +16,88 @@
+
+
+
- +  
+ + +
  - +
+
+
+ +
-
-Font size: +
Font size:       @@ -299,21 +352,30 @@
+
 
Send feedback about the website to: derby-user@db.apache.org
+
Modified: db/derby/site/trunk/build/site/releases/release-10.0.2.1.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.0.2.1.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.0.2.1.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.0.2.1.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.0.2.1 Incubator Release @@ -16,49 +16,88 @@
+
+
+
- +  
+ + +
  - +
+
+
+ +
-
-Font size: +
Font size:       @@ -586,21 +639,30 @@
+
 
Send feedback about the website to: derby-user@db.apache.org
+ Modified: db/derby/site/trunk/build/site/releases/release-10.1.1.0.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.1.1.0.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.1.1.0.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.1.1.0.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.1.1.0 Release @@ -17,49 +17,88 @@
+
+
+
- +  
+ + +
  - +
+
+
+ +
-
-Font size: +
Font size:       @@ -804,21 +857,30 @@

We strongly recommend you verify your downloads with both PGP and MD5.

+
 
Send feedback about the website to: derby-user@db.apache.org
+ Modified: db/derby/site/trunk/build/site/releases/release-10.1.2.1.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.1.2.1.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.1.2.1.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.1.2.1.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.1.2.1 Release @@ -17,49 +17,88 @@
+
+
+
- +  
+ + +
  - +
+
+
+ +
-
-Font size: +
Font size:       @@ -339,21 +392,30 @@

We strongly recommend you verify your downloads with both PGP and MD5.

+
 
Send feedback about the website to: derby-user@db.apache.org
+ Modified: db/derby/site/trunk/build/site/releases/release-10.1.3.1.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.1.3.1.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.1.3.1.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.1.3.1.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.1.3.1 Release @@ -17,49 +17,88 @@
+
+
+
- +  
+ + +
  - +
+
+
+ +
-
-Font size: +
Font size:       @@ -584,21 +637,30 @@

We strongly recommend you verify your downloads with both PGP and MD5.

+
 
Send feedback about the website to: derby-user@db.apache.org
+ Modified: db/derby/site/trunk/build/site/releases/release-10.2.1.6.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.2.1.6.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.2.1.6.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.2.1.6.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.2.1.6 Release @@ -17,49 +17,88 @@
+
+
+
- +  
+ +
+
  - +
+
+
+ +
-
-Font size: +
Font size:       @@ -363,43 +416,43 @@ DERBY-253
  • -DERBY-668 +DERBY-668
  • -DERBY-721 +DERBY-721
  • -DERBY-781 +DERBY-781
  • -DERBY-822 +DERBY-822
  • -DERBY-1130 +DERBY-1130
  • -DERBY-1295 +DERBY-1295
  • -DERBY-1314 +DERBY-1314
  • -DERBY-1323 +DERBY-1323
  • -DERBY-1357 +DERBY-1357
  • -DERBY-1384 +DERBY-1384
  • -DERBY-1621 +DERBY-1621
  • -DERBY-1652 +DERBY-1652
  • -DERBY-1867 +DERBY-1867
    • @@ -540,7 +593,7 @@
  • JSR-169, JDBC 2.1, and JDBC 3.0 support
    • - +

    JDBC 4.0 Support

    Derby 10.2.1.6 comes with source code for drivers which conform to a beta version of the JDBC standard, JDBC 4.0. This source code conforms to the following state of the JDBC 4.0 specification:

    @@ -552,7 +605,7 @@

    Due to license restrictions on the beta builds of JDK 6, Derby 10.2.1.6 does not contain compiled versions of JDBC 4.0 drivers. When run on Java SE 6, Derby 10.2.1.6 exposes the same JDBC 3.0 implementation seen when run on JDK 1.4 and 1.5. You may, however, compile Derby's JDBC 4.0 support yourself. This will let you use JDBC 4.0 features when you run Derby 10.2.1.6 on Java SE 6.

    To build this optional JDBC 4.0 support yourself, please download the source distribution and consult BUILDING.txt. You may also follow a simplified set of instructions for building JDBC 4.0 support, which you may find in the "Building the Optional JDBC4 Support" section of the Derby 10.2 wiki page.

    - +

    XML Support

    If you intend to use any of the Derby XML operators, you must ensure that you have:

    @@ -562,11 +615,11 @@

    Apache Derby 10.2.1.6 has been tested with Xalan-Java Version 2.7.0. If you have a version of Xalan that is earlier than 2.7, the Derby XML operators may still work. However, it is possible that you will experience unexpected errors when using the Derby XML operators.

    - +

    New Features

    These features appear in Derby 10.2.1.6 but not in the preceding release 10.1.3.1.

    - +
    @@ -658,11 +711,11 @@
    Master JIRANew Feature
    - +

    Bug Fixes

    List the bugs fixed by this release. These are bug fixes which turn up in Derby 10.2.1.6 but not in the preceding 10.1.3.1 release.

    - +
    @@ -1171,12 +1224,12 @@
    Issue IdDescription
    - +

    Issues

    Please be aware of the following issues:

    - +

    DERBY-253

    Problem @@ -1199,7 +1252,7 @@

    Use setCharacterStream() and getCharacterStream() instead of setUnicodeStream() and getUnicodeStream().

    - +

    DERBY-668

    Problem @@ -1222,7 +1275,7 @@

    No workaround. The behavior is now correct.

    - +

    DERBY-721

    Problem @@ -1245,7 +1298,7 @@

    Users must recode Applications which open multiple streams on the same column.

    - +

    DERBY-781

    Problem @@ -1271,7 +1324,7 @@

    There is no way to disable/workaround this new behavior since the symptom as described above is a good one for Derby.

    That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer enhancement, is encouraged to visit the performance diagnosis page and to follow up with his/her findings on the Derby mailing lists.

    - +

    DERBY-822

    Problem @@ -1294,7 +1347,7 @@

    Application code needs to be changed to adjust error handling if needed.

    - +

    DERBY-1130

    Problem @@ -1321,7 +1374,7 @@

    If using release prior to version 10.2, make sure database name is set only as a DataSource property when using Derby's client DataSources.

    - +

    DERBY-1295

    Problem @@ -1344,7 +1397,7 @@

    Fix applications which rely on the previous, non-standard behavior.

    - +

    DERBY-1314

    Problem @@ -1371,7 +1424,7 @@

    Use execute() instead of executeUpdate()/executeQuery() to invoke a stored procedure which does not return exactly 0 or 1 ResultSet objects.

    - +

    DERBY-1323

    Problem @@ -1394,7 +1447,7 @@

    Fix applications which rely on this non-standard behavior.

    - +

    DERBY-1357

    Problem @@ -1419,7 +1472,7 @@

    There is no way to disable/workaround this new behavior since the symptom as described above is a good one for Derby.

    That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer change, is encouraged to visit the performance diagnosis page and to follow up with his/her findings on the Derby mailing lists.

    - +

    DERBY-1384

    Problem @@ -1442,7 +1495,7 @@

    Fix applications which rely on Derby rejecting LOBs that are bigger than 1M.

    - +

    DERBY-1621

    Problem @@ -1505,7 +1558,7 @@

    None.

    - +

    DERBY-1652

    Problem @@ -1556,7 +1609,7 @@

    In the above statement, the trigger will only fire when an update is made to the "info" column instead of any column(s).

    - +

    DERBY-1867

    Problem @@ -1579,7 +1632,7 @@

    If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is available in the JCE provider that is available with a particular JVM. For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.

    - +

    Build Environment

    Derby release 10.2.1.6 was built using the following environment:

    @@ -1604,7 +1657,7 @@ JSR 169 - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).
    - +

    Testing

    Tests were run on the following platforms. Results are listed separately for each platform.

    @@ -1734,7 +1787,7 @@

    Tests for a specific platform can be run using the derbyTesting.jar file that can be found in the lib directory of the -lib or -bin distributions.

    Instructions on how to run the tests can be found in the testing README.

    - +

    Verifying releases

    It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.

    @@ -1757,21 +1810,30 @@

    We strongly recommend you verify your downloads with both PGP and MD5.

    +
     
    Send feedback about the website to: derby-user@db.apache.org
    + Modified: db/derby/site/trunk/build/site/releases/release-10.2.2.0.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.2.2.0.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.2.2.0.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.2.2.0.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.2.2.0 Release @@ -17,49 +17,88 @@
    +
    +
    +
    - +  
    + +
    +
      - +
    +
    +
    + +
    -
    -Font size: +
    Font size:       @@ -477,16 +530,16 @@
  • JSR-169, JDBC 2.1, JDBC 3.0, and JDBC 4.0 support
    • - +

    New Features

    Release 10.2.2.0 is a bug-fix release. No new features were added since 10.2.1.6.

    - +

    Bug Fixes

    The following bug fixes turn up in Derby 10.2.2.0 but not in the preceding 10.2.1.6 release.

    - +
    @@ -563,12 +616,12 @@
    Issue IdDescription
    - +

    Issues

    Applications which run against Derby 10.0 or 10.1 may rely on incorrect Derby behavior. After upgrading to 10.2, those applications may need some recoding so that they no longer rely on bad behavior which has been fixed. Please consult the following list of issues which may require some application recoding. Note that 10.2.2.0 does not introduce any additional issues beyond the issues introduced by 10.2.1.6:

    - +

    DERBY-253

    See DERBY-253.

    @@ -592,7 +645,7 @@

    Use setCharacterStream() and getCharacterStream() instead of setUnicodeStream() and getUnicodeStream().

    - +

    DERBY-668

    See DERBY-668.

    @@ -616,7 +669,7 @@

    Grant these permissions so that sysinfo can run correctly under the Java security manager.

    - +

    DERBY-721

    See DERBY-721.

    @@ -640,7 +693,7 @@

    Users must recode Applications which open multiple streams on the same column.

    - +

    DERBY-781

    See DERBY-781.

    @@ -667,7 +720,7 @@

    There is no way to disable/workaround this new behavior. The increased compilation time buys better performance at query execution time.

    That said, any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer enhancement, is encouraged to visit the performance diagnosis page and to follow up with his/her findings on the Derby mailing lists.

    - +

    DERBY-822

    See DERBY-822.

    @@ -691,7 +744,7 @@

    Application code needs to be changed to adjust error handling if needed.

    - +

    DERBY-1130

    See DERBY-1130.

    @@ -719,7 +772,7 @@

    When upgrading an application to run against Derby 10.2, make sure the database name is set only as a DataSource property when using Derby's client DataSources.

    - +

    DERBY-1295

    See DERBY-1295.

    @@ -743,7 +796,7 @@

    Fix applications which rely on the previous, non-standard behavior.

    - +

    DERBY-1314

    See DERBY-1314.

    @@ -772,7 +825,7 @@

    Use execute() instead of executeUpdate()/executeQuery() to invoke a stored procedure which does not return exactly 0 or 1 ResultSet objects.

    - +

    DERBY-1323

    See DERBY-1323.

    @@ -797,7 +850,7 @@

    Fix applications which rely on this non-standard behavior.

    - +

    DERBY-1357

    See DERBY-1357.

    @@ -821,7 +874,7 @@

    In general, the performance of these queries should stay the same or improve. However, it is possible that performance may degrade for some queries. Any user who notices a negative performance change after moving to Derby 10.2, and who believes that the difference in performance is related to this optimizer change, is encouraged to visit the performance diagnosis page and to follow up with his/her findings on the Derby mailing lists.

    - +

    DERBY-1384

    See DERBY-1384.

    @@ -845,7 +898,7 @@

    Fix applications which rely on Derby rejecting LOBs that are bigger than 1M.

    - +

    DERBY-1652

    See DERBY-1652.

    @@ -898,7 +951,7 @@

    In the above statement, the trigger will only fire when an update is made to the "info" column instead of any column(s).

    - +

    DERBY-1867

    See DERBY-1867.

    @@ -922,7 +975,7 @@

    If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is available in the JCE provider that is available with a particular JVM. For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.

    - +

    Build Environment

    Derby release 10.2.2.0 was built using the following environment:

    @@ -947,7 +1000,7 @@ JSR 169 - J2ME support was built using java.sun.com/j2me (j2me_cdc_fp-1_0_2).
    - +

    Testing

    Tests were run on the following platforms. Results are listed separately for each platform.

    @@ -1033,7 +1086,7 @@

    Tests for a specific platform can be run using the derbyTesting.jar file that can be found in the lib directory of the -lib or -bin distributions.

    Instructions on how to run the tests can be found in the testing README.

    - +

    Verifying releases

    It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.

    @@ -1056,21 +1109,30 @@

    We strongly recommend you verify your downloads with both PGP and MD5.

    +
     
    Send feedback about the website to: derby-user@db.apache.org
    + Modified: db/derby/site/trunk/build/site/releases/release-10.3.1.4.html URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/releases/release-10.3.1.4.html?rev=606336&r1=606335&r2=606336&view=diff ============================================================================== --- db/derby/site/trunk/build/site/releases/release-10.3.1.4.html (original) +++ db/derby/site/trunk/build/site/releases/release-10.3.1.4.html Fri Dec 21 14:30:38 2007 @@ -1,9 +1,9 @@ - + - + Apache Derby 10.3.1.4 Release @@ -17,49 +17,88 @@
    +
    +
    +
    - +  
    + +
    +
      - +
    +
    +
    + +
    -
    -Font size: +
    Font size:       @@ -500,7 +553,7 @@

    This is a minor release. The following table lists new features that were added and notable improvements that were made:

    - +
    @@ -571,11 +624,11 @@
    FeatureDescriptionIssue Id(s)
    - +

    CHANGES

    The following issues are addressed by Derby release 10.3.1.4. These issues are not addressed in the preceding 10.2.2.0 release.
    This list includes bugs and improvements, and sub-tasks if the super-task is not fixed in 10.3.1.4, but not issues with only test or web content changes.

    - +
    @@ -1334,12 +1387,12 @@
    Issue IdDescription
    - +

    Issues

    Compared with the previous release (10.2.2.0), Derby release 10.3.1.4 introduces the following new features and incompatibilities. These merit your special attention.

    - +

    DERBY-2925

    Summary of Change @@ -1368,7 +1421,7 @@

    The application needs to specify a different filename which does not exist or delete the existing file before performing the Export operation.

    - +

    DERBY-2757

    Summary of Change @@ -1393,7 +1446,7 @@

    SecurityExceptions can be avoided by installing your own security manager with your own policy file, which grants the appropriate privileges to your user-written code. Instructions on how to do this can be found in the Derby Developer's Guide in the section titled "Running Derby under a security manager" and in the Derby Server and Administration Guide in the section titled "Running the Network Server under the security manager".

    If for some reason this is not practical, or if the startup performance drag is intolerable, then you can instruct the server to not install a security manager. You do this by booting the server with the "-noSecurityManager" command line option as explained in above-mentioned section of the Derby Server and Administration Guide.

    - +

    DERBY-2729

    Summary of Change @@ -1416,7 +1469,7 @@

    Applications should be revised to not use Blobs and Clobs after the transaction ends or the connection is closed.

    - +

    DERBY-2610

    Summary of Change @@ -1439,7 +1492,7 @@

    Users must recode applications to specify the table names. When information on multiple tables is required, the application first has to get the table names, e.g. by using the DatabaseMetaData method getTables(), and then use the returned table names as input to the method in question.

    - +

    DERBY-2526

    Summary of Change @@ -1454,17 +1507,10 @@

    As an example, take the following:

    create table t1 (c0 int);
    create table x (c1 int, c2 int);
    create table t2 (c3 int, c4 int);
    -
    insert into t1 values 1;
    insert into x values (0, 1);
    insert into t2 values (0, 2);
    -
    -
    -
    -
    -
    -

    +
    insert into t1 values 1;
    insert into x values (0, 1);
    insert into t2 values (0, 2);

    With these tables, the following query should return one row, but was returning zero rows in previous releases:

    select t1.* from t1 JOIN (select * from x) vw(c1,c2) ON (t1.c0 = vw.c2) JOIN t2 ON (vw.c1 = t2.c3)
    -

    This problem has been fixed in Derby 10.3.

    @@ -1484,7 +1530,7 @@

    No application changes should be needed.

    - +

    DERBY-2443

    Summary of Change @@ -1517,7 +1563,7 @@

    Detailed description of these methods can be found in api docs of Java SE 6: ResultSet.

    - +

    DERBY-2430

    Summary of Change @@ -1536,7 +1582,7 @@

    Applications relying on the Client behaving in the old way will have to be adjusted.

    - +

    DERBY-2386

    Summary of Change @@ -1559,7 +1605,7 @@

    SQL functions taking the result of a timestampdiff function as a parameter will have to be modified to take a BIGINT parameter instead of INT.

    - +

    DERBY-2370

    Summary of Change @@ -1592,7 +1638,7 @@

    As a result of the new internal rewrite, any "*" that appears within the EXISTS set operation will now be properly expanded. This means that applications which specify set operations inside of an EXISTS predicate must now ensure that the result sets to which a given set operation applies have the same number of result columns. See the "incompatibilities" section above for details. No other application changes are required.

    - +

    DERBY-2296

    Summary of Change @@ -1624,7 +1670,7 @@

    - +

    DERBY-2264

    Summary of Change @@ -1673,7 +1719,7 @@ select authorizationid from sys.sysschemas where schemaname = 'SYS';

    - +

    DERBY-2256

    Summary of Change @@ -1692,7 +1738,6 @@

    -- Following query was returning zero rows when it should return 1 row.
    select * from t1 where i in (4.23, 4);

    -- Following query should return zero rows but was returning 1 row. select * from t1 where i in (2.8, 4.23);
    -

    This problem has been fixed in Derby 10.3.

    @@ -1711,7 +1756,7 @@

    No application changes should be needed.

    - +

    DERBY-2196

    Summary of Change @@ -1731,7 +1776,7 @@

    Instead of relying on the default policy installed by the Network Server, the user should further limit the scope of privileged operations. In particular, the user should fine-tune the blanket read/write privilege granted on the entire server file system. The user should narrow this privilege to just the directories needed for backup/restore, import/export, and jar file loading. For instructions on how to refine the policy file, please consult the Derby Server and Administration Guide section titled "Customizing the Network Server's security policy".

    This is also an opportunity for the user to enable user authentication if the Network Server currently runs without authentication. Running in a client/server configuration without authentication exposes the application and the server machine to many threats. It is strongly discouraged. For instructions on enabling user authentication, please consult the Derby Developer's Guide section titled "Working with user authentication".

    - +

    DERBY-2108

    Summary of Change @@ -1783,7 +1828,7 @@

    Users must recode applications to recognize the changed messages.

    - +

    DERBY-2020

    Summary of Change @@ -1803,7 +1848,7 @@

    No changes are needed or possible to benefit from this change. If your JVM supports it, it will be used. If Derby detects that your JVM has a bug in the support for "rwd", a message will be printed to derby.log:
    ------------ BEGIN ERROR MESSAGE -------------
    LogToFile.checkJvmSyncError: Your JVM seems to have a problem with implicit syncing of log files. Will use explicit syncing instead.
    ------------ END ERROR MESSAGE -------------

    - +

    DERBY-1942

    Summary of Change @@ -1827,7 +1872,7 @@

    Applications using the TIME data type must use the TIMESTAMP data type instead, if date information is needed besides time information.

    - +

    DERBY-1852

    Summary of Change @@ -1857,11 +1902,6 @@


    -
    -
    -
    -
    -

    In this example the chain of unions is as follows:

                  union_1 all
@@ -1887,7 +1927,7 @@
 
    
 
    No application changes should be needed.
    
 
    
-
+
 
    DERBY-1828
    
 
    
 Summary of Change
@@ -1910,7 +1950,7 @@
 
    
 
    Applications that are dependant on authorization error codes must be recoded to expect the new codes.
    
 
    
-
+
 
    DERBY-1816
    
 
    
 Summary of Change
@@ -1941,7 +1981,7 @@
 
    No application changes should be needed.
    
 
    
 
    
-
+
 
    DERBY-1610
    
 
    
 Summary of Change
@@ -1974,7 +2014,7 @@
 
    
 
    Applications relying on the Client behaving in the old way will have to be adjusted.
    
 
    
-
+
 
    DERBY-1519
    
 
    
 Summary of Change
@@ -1997,7 +2037,7 @@
 
    
 
    Applications accessing Ascii streams from Derby through the client driver must be extended to handle 8-bit values.
    
 
    
-
+
 
    DERBY-1484
    
 
    
 Summary of Change
@@ -2020,7 +2060,7 @@
 
    
 
    Users must recode applications to specify the table names. When information on multiple tables is required, the application first has to get the table names, e.g. by using the DatabaseMetaData method getTables(), and then use the returned table names as input to the method in question.
    
 
    
-
+
 
    DERBY-1341
    
 
    
 Summary of Change
@@ -2057,7 +2097,7 @@
 http://java.sun.com/javase/6/docs/api/java/sql/Clob.html
    - +

    DERBY-729

    Summary of Change @@ -2080,7 +2120,7 @@

    Applications that rely on the old behavior will have to be changed to expect/check for NULL as return value instead of 0.

    - +

    DERBY-415

    Summary of Change @@ -2103,7 +2143,7 @@

    Users who want to check for the presence of the DB2 JCC driver will need to use the new command switch.

    - +

    DERBY-208

    Summary of Change @@ -2130,13 +2170,13 @@

    Applications that access Blob/Clob objects after the transaction they were created in has committed need to be changed. Make sure that the commit of the transaction is delayed until the objects are no longer needed. This means that if the same object is to be used in several statements, these statements will have to run in the same transaction (i.e., auto-commit may not be used in such cases). Also note that if auto-commit is used, a transaction will be committed when the result set is closed. Hence, when using auto-commit one must delay the closing of the result set until the Blob/Clob objects are no longer needed.

    - +

    Open Bugs

    For open bugs please refer to the JIRA bug tracking system: http://issues.apache.org/jira/browse/DERBY

    However, of special interest in particular for existing applications are the following bugs open at the time of the 10.3.1.4 release:

    - +
    @@ -2154,7 +2194,7 @@
    Issue IdDescription
    - +

    Build Environment

    Derby release 10.3.1.4 was built using the following environment:

    @@ -2178,21 +2218,30 @@
    +
     
    Send feedback about the website to: derby-user@db.apache.org
    +