Apache Derby 10.5.3.0 Release

Use the links below to download a distribution of Apache Derby. You should always verify the integrity of distribution files downloaded from a mirror.

There are four different distributions:

• bin distribution - contains the documentation, javadoc, and jar files for Derby.
• lib distribution - contains only the jar files for Derby.
• lib-debug distribution - contains jar files for Derby with source line numbers.
• src distribution - contains the Derby source tree at the point which the binaries were built.

db-derby-10.5.3.0-bin.zip [PGP] [MD5]
db-derby-10.5.3.0-bin.tar.gz [PGP] [MD5]

db-derby-10.5.3.0-lib.zip [PGP] [MD5]
db-derby-10.5.3.0-lib.tar.gz [PGP] [MD5]

db-derby-10.5.3.0-lib-debug.zip [PGP] [MD5]
db-derby-10.5.3.0-lib-debug.tar.gz [PGP] [MD5]

db-derby-10.5.3.0-src.zip [PGP] [MD5]
db-derby-10.5.3.0-src.tar.gz [PGP] [MD5] (Note that, due to long filenames, you will need gnu tar to unravel this tarball.)

There are two separate Eclipse plugins for Derby:

• derby_core_plugin - provides the Derby jar files to other plugins in Eclipse.
• derby_ui_plugin - provides an Apache Derby Nature in Eclipse for easy database application development.

derby_core_plugin_10.5.3.zip [PGP] [MD5]
derby_ui_doc_plugin_1.1.2.zip [PGP] [MD5]

Please note: both plugins must be installed for full functionality. For information on installing and using the Derby plugins for Eclipse, please see the Using the 10 Core and 1.1 UI Derby plug-ins page.

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

Overview

Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs.

Derby functionality includes:

• Embedded engine with JDBC drivers
• Network Server
• Network client JDBC drivers
• Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)

New Features

This is a bug fix release and also provides localization of new 10.5 messages. No new features were added.

Bug Fixes

The following issues are addressed by Derby release 10.5.3.0. These issues are not addressed in the preceding, deprecated 10.5.2.0 release. Most significantly, Derby 10.5.3.0 carries the fix to the wrong-results bug which caused the community to abandon 10.5.2.0: DERBY-4331

The following additional issues are addressed by Derby release 10.5.3.0. These issues are not addressed in the preceding 10.5.1.1 release.

Issues

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

• Note for DERBY-4230: In order to see the fix for DERBY-4230 for a view created with a previous release, users must drop and recreate the view.

• Note for DERBY-3991: Clob.truncate now presents a more specific error message for a negative length.

Note for DERBY-4230

Summary of Change

In order to see the fix for DERBY-4230 for a view created with a previous release, users must drop and recreate the view.

Symptoms Seen by Applications Affected by Change

DERBY-4230 fixed an issue where an extra column might appear in DatabaseMetaData.getColumns() for a view that uses a group by and an expression in the select list. The problem occurred during create view with the old release. After updating your derby jars to a release that has the fix, if you still see the behavior, you will need to drop and recreate the view to get the fix.

Incompatibilities with Previous Release

none

Rationale for Change

The change was made to fix a regression introduced in version 10.3.1.4 by DERBY-681.

Application Changes Required

Users must drop an recreate affected views to see the fix for DERBY-4230.

Note for DERBY-3991

Summary of Change

Clob.truncate now presents a more specific error message for a negative length.

Symptoms Seen by Applications Affected by Change

Specifying a negative length will raise an SQLException with a different state;

• Now: XJ071: Negative length argument '-2' passed in a BLOB or CLOB method.
• Before: XJ070: Negative or zero position argument '-2' passed in a Blob or Clob method.

Incompatibilities with Previous Release

Applications catching a specific exception based on SQLState may behave differently. The incompatibility can only be seen if the application calls Clob.truncate with a negative length using the embedded driver.

Rationale for Change

The embedded driver was changed to be consistent with the client driver for the error message raised when invoking Clob.truncate with a negative length.

Application Changes Required

Look for SQLState XJ071 instead of XJ070 when Clob.truncate is called to catch invocations specifying a negative length.

Build Environment

Derby release 10.5.3.0 was built using the following environment:

• Branch - Source code came from the 10.5 branch.
• Machine - Mac OS X 10.5.7 on Macbook Pro 3,1.
• Ant - Apache Ant version 1.7.1 compiled on June 27 2008
• J2ME/JSR 169 - Sun's phoneME Advanced MR2
• JDK 1.4 - Apple's Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_21-b01-324)
• Java 5 - Apple's Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_19-b02-304)
• Java 6 - Apple's Java(TM) SE Runtime Environment (build 1.6.0_13-b03-211)
• Compiler - The Apple Java 5 compiler was used to compile all classes. Platform-specific code was compiled against the corresponding platform libraries listed above.

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.

The PGP signatures can be verified using PGP or GPG. First download the Apache Derby KEYS as well as the asc signature file for the particular distribution. It is important that you get these files from the ultimate trusted source - the main ASF distribution site, rather than from a mirror. Then verify the signatures using ...

% pgpk -a KEYS
% pgpv db-derby-X.Y.tar.gz.asc

or

% pgp -ka KEYS
% pgp db-derby-X.Y.tar.gz.asc

or

% gpg --import KEYS
% gpg --verify db-derby-X.Y.tar.gz.asc

To verify the MD5 signature on the files, you need to use a program called md5 or md5sum, which is included in many unix distributions. It is also available as part of GNU Textutils. Windows users can get binary md5 programs from here, here, or here.

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