Release Notes for Apache Derby 10.8.2.2

These notes describe the difference between Apache Derby release 10.8.2.2 and the preceding release 10.8.1.2.

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:

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

Java and JDBC versions supported:

• Java SE 1.4 and higher with JDBC 2.1, 3.0, 4.0 and 4.1
• Java ME CDC/Foundation Profile 1.1 with JSR-169 JDBC Optional Package for CDC/Foundation Profile.

This is a bug fix release. No new features were added.

The following issues are addressed by Derby release 10.8.2.2. These issues are not addressed in the preceding 10.8.1.2 release.

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

• Note for DERBY-5395: Now, only the database owner may view several diagnostic VTIs: syscs_diag.statement_cache, syscs_diag.transaction_table, syscs_diag.error_log_reader( ), and syscs_diag.statement_duration().

Note for DERBY-5395

import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;

public class SafeCacheViewer
{
    public  static  ResultSet   safeCacheViewer()   throws SQLException
    {
        return DriverManager.getConnection( "jdbc:default:connection" ).prepareStatement
            ( "select id, schemaName, valid, compiled_at from syscs_diag.statement_cache" ).executeQuery();
    }
}

create function safeCacheViewer()
returns table
(
    id char( 36 ),
    schemaName varchar( 128 ),
    valid boolean,
    compiled_at timestamp
)
language java parameter style derby_jdbc_result_set reads sql data
external security definer
external name 'SafeCacheViewer.safeCacheViewer';

grant execute on function safeCacheViewer to public;

select * from table( test_dbo.safeCacheViewer() ) s;

Derby release 10.8.2.2 was built using the following environment:

• Branch - Source code came from the 10.8 branch.
• Machine - Windows XP Professional Version 2002 Service Pack 3
• Ant - Apache Ant version 1.7.0 compiled on December 13 2006.
• JDK 1.4 - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142ifx-20110211 (SR13 FP8+PM31983)).
• Java 6 - Java(TM) SE Runtime Environment (build pwi3260sr9fp1-2011-0208_03(SR9 FP1) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623).
• Compiler - The 1.6.0-b105 javac was used to compile all classes.
• JSR 169 - Java ME support was built using libraries from IBM's j9 jvm from WEME 6.2.

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.