These notes describe the difference between IBM Derby SDK 10.5 and the preceding release IBM Derby SDK 10.3.
IMPORTANT DISTRIBUTION NOTE: The IBM Derby SDK Common Component is a repackaging of Apache Derby, an Open Source software product. As such it falls under the jurisdiction of the IBM Open Source Steering Committee (OSSC). There are special requirements that must be met by any IBM product using a product like Derby that incorporates third party code. See Stanley Bradbury for details of the current OSSC requirements.
IBM Derby SDK 10.5 is a repackaging of Apache Derby 10.5.3.0. It includes bug fix changes not in the 10.5.3.0 build available at Apache. The version number on the initial IBM Common Component release of Derby 10.5 is 10.5.3.1 (807750).
Between this release (IBM Derby SDK 10.5) and the previous IBM Derby SDK release (10.3) there have been 3 Apache releases that each have their own Release Notes. IBM Derby SDK 10.5 includes all fixes of those previous releases, however, the Release Notes for those releases are not included in the IBM Derby SDK 10.5 release package. For reference, they can be viewed here:
The following issues are in whole, or partially addressed by Derby release 10.5.3.1 (807750) but are not mentioned in the Release Notes for 10.5.2.0/10.5.3.0.:
Issue Id Beetle Id Description DERBY-700 6525 Derby does not prevent a dual boot of database from different classloaders on Linux and Max OS DERBY-4092 10649 You should not be able to invoke a table function as a scalar function DERBY-4330 10920 NullPointerException or assert failure when re-executing PreparedStatement after lock timeout DERBY-1191 7499 Some SQLExceptions, for example those generated from BrokeredStatements, do not print to derby.log even when derby.stream.error.logSeverityLevel=0