Release Notes for Apache Derby 10.14.1.0

These notes describe the difference between Apache Derby release 10.14.1.0 and the preceding release 10.13.1.1.

Overview

The most up to date information about Derby releases can be found on the Derby download page.

Apache Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs. More information about Derby can be found on the Apache web site. Derby functionality includes:

Support for Java SE 8 is being sunsetted and will not be supported by the next (10.15) release family. The 10.14 release family supports the following Java and JDBC versions:

New Features

This is a feature release. The following new features were added:

Bug Fixes

The following issues are addressed by Derby release 10.14.1.0. These issues are not addressed in the preceding 10.13.1.1 release.

Issue Id
Description
DERBY-6962Forbid ALTER TABLE ... SET CYCLE on identity columns in pre-10.11 databases
DERBY-6961SET CYCLE fails to let an identity column cycle if the range is already exhausted
DERBY-6959Require the Standard SET keyword in the syntax for changing the cycle behavior of identity columns
DERBY-6956Create table as Select cannot copy Decimal columns
DERBY-6936Documentation for changes made as part of DERBY-6904
DERBY-6935Test Coverage for added features.
DERBY-6918Problem with schema name starting with number followed by a dot
DERBY-6916Doc of derbyrun.jar should describe complete list of referenced jars
DERBY-6906Allow a GENERATED column to explicitly specify NO CYCLE
DERBY-6903ALTER TABLE ALTER COLUMN resets CYCLE option of IDENTITY column
DERBY-6899Improve docs build.xml to remove CLASSPATH requirement
DERBY-6898Improve developer documentation for docs
DERBY-6857Deprecate support for building Derby under JDKs 6 and 7

Issues

No issues required detailed release notes.

Build Environment

Derby release 10.14.1.0 was built using the following environment:

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 that you verify your downloads with both PGP and MD5.