These notes describe the difference between Apache Derby release 10.9.2.0 and the preceding release 10.9.1.0.
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:
Java and JDBC versions supported:
This is a maintenance release. No new features were added.
The following issues are addressed by Derby release 10.9.2.0. These issues are not addressed in the preceding 10.9.1.0 release.
Issue Id | Description |
DERBY-5999 | Improve documentation on index key lengths |
DERBY-5998 | Replication tests fail on CDC platforms without optional JSSE package |
DERBY-5993 | The Reference Manual shows an embedded url in its example for the client-side-only retrieveMessageText attribute. |
DERBY-5961 | Developer's guide mentions SQL state 40XL2 which is no longer used |
DERBY-5954 | NPE in SELECT involving subselects and windows functions |
DERBY-5951 | Missing method exception raised when using Clobs with territory based collation |
DERBY-5948 | Update JVMInfo.java to include JDK 8 |
DERBY-5937 | File handle is leaked when a Slave replication is shutdown with failover=true |
DERBY-5925 | Document derby.log changes resulting from DERBY-5240 |
DERBY-5918 | CREATE TABLE AS SELECT doesn't work on tables with BOOLEAN columns |
DERBY-5916 | java.lang.NullPointerException org.apache.derby.impl.store.raw.data.BaseDataFileFactory.stop() connecting to network server |
DERBY-5912 | testIsValidImplemented fails for NetworkServer in some slow running machines/configurations |
DERBY-5911 | WHERE condition getting pushed into sub-query with FETCH |
DERBY-5910 | Document use of Connection.close() with try-with-resources |
DERBY-5909 | The lang attribute in toc.html always says 'en-us' |
DERBY-5906 | In the Reference Manual, sin() is used as the example for the sinh() function. |
DERBY-5905 | Derby html documentation doesn't render properly and prints garbage on Internet Explorer |
DERBY-5900 | Need to correct Reference Guide description of contents of SYS.SYSPERMS.OBJECTTYPE |
DERBY-5898 | add ibm18 class to functionTests.harness |
DERBY-5839 | dblook run on toursdb fails on triggers with java.lang.StringIndexOutOfBoundsException in dblook.log |
DERBY-5838 | By using syscs_set_database_property, you can set the database version to a garbage string which prevents you from booting the database. |
DERBY-5830 | Make DoubleProperties.propertyNames() thread-safe |
DERBY-5822 | Document the new SQL standard behavior of the SPACE_TABLE vti |
DERBY-5816 | store.ServicePropertiesFileTest fails on z/OS |
DERBY-5805 | Database encryption topics in Reference Manual need more information |
DERBY-5799 | add more info on when Derby chooses 32k page size for tables. |
DERBY-5797 | AssertionFailedError in functionTests.tests.lang.UpdateStatisticsTest.testDisposableStatsEagerness |
DERBY-5795 | Documentation in release doesn't include stylesheets |
DERBY-5775 | Upgrade tests should print full IOException stack trace when it fails to access old versions |
DERBY-5663 | Getting NPE when trying to set derby.language.logStatementText property to true inside a junit suite. |
DERBY-5622 | Reduce the chance for hash collisions when checking bootPassword at boot time and when changing password. |
DERBY-5561 | Race conditions in LogicalConnection checking for a null physical connection |
DERBY-5531 | Assert failure when inserting NULL into indexed column with territory-based collation |
DERBY-5425 | Updateable holdable ResultSet terminates early after 65638 updates |
DERBY-5424 | On z/OS testConnectWrongSubprotocolWithSystemProperty(org.apache.derbyTesting.functionTests.tests.tools.ConnectWrongSubprotocolTest)junit.framework.Asserti ailedError |
DERBY-5407 | When run across the network, dblook produces unusable DDL for VARCHAR FOR BIT DATA columns. |
DERBY-5358 | SYSCS_COMPRESS_TABLE failed with conglomerate not found exception |
DERBY-5240 | Log Operating system information to derby.log on boot |
DERBY-4279 | Statement cache deadlock |
DERBY-4229 | encryptionKeyLength connection attribute should be documented |
DERBY-1721 | DOCS - Remove duplicate information in Dev Guide re: Encryption |
DERBY-1400 | Cleanup code in network server's DRDAStatement class |
Compared with the previous release (10.9.1.0), there are no issue specific release notes.
Derby release 10.9.2.0 was built using the following environment:
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.