Join Firebird!

Join Firebird Foundation to support Firebird SQL development and receive multiple bonuses

Follow Us

Select your media preference

Newsletter

Subscribe to Firebird’s Newsletter to receive the latest news

News & Events
December 31, 2013
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. 
 
Warm Regards,
Firebird Project
 
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. 
 
Warm Regards,
Firebird Project
 
December 07, 2013
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 error when setting connection charset equal to "file.encoding" java property (JDBC-314)
  • Fixed connection character set not correctly set when specifying the Java connection characterset (charSet or localEncoding property) (JDBC-315)
  • Fixed incorrect lengths and/or radix reported by getTypeInfo and getColumns metadata (JDBC-317, JDBC-318)
  • Initial Java 8 / JDBC 4.2 support (JDBC-319)
  • Firebird 3 BOOLEAN type support, see Support for Firebird 3 BOOLEAN type in the release notes for more details (JDBC-321)
  • Added fallback of loading GDSFactoryPlugin implementations to prevent NullPointerException in Hibernate reverse engineering wizard in NetBeans (JDBC-325)
  • 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.

The release is also available on maven(*):
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.4</version>

*The artifactId depends on your target Java version: jaybird-jdk15, jaybird-jdk16, jaybird-jdk17 or jaybird-jdk18.
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 error when setting connection charset equal to "file.encoding" java property (JDBC-314)
  • Fixed connection character set not correctly set when specifying the Java connection characterset (charSet or localEncoding property) (JDBC-315)
  • Fixed incorrect lengths and/or radix reported by getTypeInfo and getColumns metadata (JDBC-317, JDBC-318)
  • Initial Java 8 / JDBC 4.2 support (JDBC-319)
  • Firebird 3 BOOLEAN type support, see Support for Firebird 3 BOOLEAN type in the release notes for more details (JDBC-321)
  • Added fallback of loading GDSFactoryPlugin implementations to prevent NullPointerException in Hibernate reverse engineering wizard in NetBeans (JDBC-325)
  • 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.

The release is also available on maven(*):
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.4</version>

*The artifactId depends on your target Java version: jaybird-jdk15, jaybird-jdk16, jaybird-jdk17 or jaybird-jdk18.
November 28, 2013
Firebird seminars took place in Siegburg (November 22, 2013) and Prague (November 25, 2013). 39 and 50 attendees were there, photo reports are available at Facebook page of FirebirdSQL. Stay tuned for the next seminar date and place! The speakers were Vlad Khorsun (Firebird Core Team), Alexey Kovyazin (IBSurgeon), and Dmitry Kuzmenko (IBSurgeon).

More details about seminar schedule: http://www.firebirdsql.org/en/firebird-conference-tour-2013/
Firebird seminars took place in Siegburg (November 22, 2013) and Prague (November 25, 2013). 39 and 50 attendees were there, photo reports are available at Facebook page of FirebirdSQL. Stay tuned for the next seminar date and place! The speakers were Vlad Khorsun (Firebird Core Team), Alexey Kovyazin (IBSurgeon), and Dmitry Kuzmenko (IBSurgeon).

More details about seminar schedule: http://www.firebirdsql.org/en/firebird-conference-tour-2013/
August 29, 2013