Apache Derby 10.1.1.0 Release

Use the links below to download a distribution of Apache Derby from the archives. It is good practice to verify the integrity of the distribution files.

There are three different distributions:

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

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

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

db-derby-10.1.1.0-src.zip [PGP] [MD5]
db-derby-10.1.1.0-src.tar.gz [PGP] [MD5]

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.1.1.zip [PGP] [MD5]
derby_ui_plugin_1.1.0.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.1 Core and 1.1 UI Derby plug-ins page.

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

What's new in 10.1.1.0:

• New open source Derby network client driver
• Support for J2ME/CDC/Foundation with JSR-169 JDBC subset
• Online compress functionality for reclaiming disk space during operation
• XA support for Network Server
• Increased identifier lengths to 128 characters for all identifiers
• Added SQL: INTERSECT and EXCEPT
• Added SQL: SYNONYM
• JDBC Updatable Result Sets
• ORDER by expressions
• Allow insertions into an identity column
• Support for explicit Java method signature in function and procedure defintions

For a comprehensive list of changes, consult the CHANGES file in your distribution.

10.1.1.0 functionality includes:

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

SQL support:

• Schemas, tables, tempoaray tables, views, triggers, indexes, savepoints
• Java procedures and functions
• Standard datatypes including BLOB and CLOB
• Sub-queries and joins
• Primary key, foreign key, unique and check constraints
• Referential actions

Other features:

• Full ACID transaction support with all four isolation levels
• Row and table level locking
• Configurable authentication including LDAP support
• Import/Export
• On-line backup and recovery support
• Optional on-disk encryption
• Platform independent database format
• Full support for Java 2 Security Manager

JDK/JDBC support:

• JDK 1.3, 1.4, 1.5, and J2ME support
• JSR-169, JDBC 2.1, and JDBC 3.0 support

Derby version 10.1.1.0

This is the first official release for Derby as a subproject of the Apache DB proejct. The build number of this release is 208786. For information on getting started using Derby, refer to the Getting Started manual.

The IBM Universal JDBC Driver is no longer required to use the Derby Network Server. A new Derby network client driver, packaged as derbyclient.jar, is now provided for remote network access to the Derby Network Server. For more information on using the Derby network client driver, see the Derby Server and Administration Guide.

A detailed list of changes can be found in the CHANGES file in each of the distributions listed below.

This release fixes the following reported JIRA issues since the 10.0.2.1 release:

Below is a list of open code issues documented in the JIRA bug tracking system for the project at the time of the release:

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

Several test issues were reported, but no specific code issues were noted.

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.

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.