From all the team here at Firebird Project we wish you and your families all the very best for the Holiday season and the New Year. 2013 has been a fantastic year for Firebird and next 2014 should be even better!

Thanks to all Firebird sponsors and developers, Firebird 3.0 is on the way, the next testing release (Alpha 2) is expected in Q1 2014 with Beta 1 following in Q2 2014.

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.4.

This release contains the following fixes:

Fixed: Exceptions during statement preparation leave connection and transaction open after explicit close (JDBC-311)

Fixed batch update (or insert) with blob set through setBinaryStream() sets empty blob for all but the first batch entry (JDBC-312)

Fixed incomplete checks of database, transaction, statement and blob handle validity before continuing with actions. These incomplete checks could lead to unexpected exceptions (for example a NullPointerException in iscDatabaseInfo) (JDBC-313)

Fixed: Jaybird should specify dialect 3 in dpb when no explicit dialect was set (JDBC-327)

Fixed: several DatabaseMetaData methods defined by JDBC to only accept the actual table name also accepted a LIKE-pattern or empty string or null. This was changed to conform to JDBC. This change can break applications that relied on the incorrect behavior (JDBC-331)

Affected methods are: getPrimaryKeys, getBestRowIdentifier, getImportedKeys, getExportedKeys and getCrossReference. As part of this change getIndexInfo now handles names in the wrong case slightly different.

Jaybird 3.0 will further modify and restrict the pattern matching and case sensitivity of metadata methods. See Future changes to Jaybird in the release notes for more details.