The following has been changed or fixed since Jaybird 3.0.2

• Fixed: Some older versions of JBoss would throw an java.lang.IllegalStateException: Can't overwrite cause when FBResourceException initialised its exception cause. (JDBC-512)
• Improved: Added explicit Automatic-Module-Name: org.firebirdsql.jaybird to manifest for forwards compatibility with Java 9 modularization. (JDBC-511)

See the full release notes for more information.

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>3.0.3</version>

* The artifactId depends on your target Java version: jaybird-jdk18, or jaybird-jdk17

The following has been changed or fixed in Jaybird 2.2.14:

• Fixed: FBTraceManager.loadConfigurationFromFile strips line breaks (JDBC-493)
• Improved: Added explicit Automatic-Module-Name: org.firebirdsql.jaybird to manifest for forwards compatibility with Java 9 modularization. (JDBC-511)

See the full release notes for more information.

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.14</version>

* The artifactId depends on your target Java version: jaybird-jdk18, jaybird-jdk17, or jaybird-jdk16.

The following has been changed or fixed since Jaybird 3.0.1

• Fixed: Specifying an unknown Java character set in connection property charSet or localEncoding was handled as if no connection character set had been specified, now we throw an exception that the character set is unknown. (JDBC-498)
• Changed: Specifying a connection character set is no longer required, and will now default to NONE again, if system property org.firebirdsql.jdbc.defaultConnectionEncoding is not specified. (JDBC-502)
  The new requirement turned out to be too restrictive and hindering adoption of Jaybird 3. If you do want strict behaviour, you can specify system property org.firebirdsql.jdbc.requireConnectionEncoding with value true.

See the full release notes for more information.

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>3.0.2</version>

* The artifactId depends on your target Java version: jaybird-jdk18, or jaybird-jdk17

The following has been changed or fixed in Jaybird 3.0.1:

• Fixed: FBTraceManager.loadConfigurationFromFile strips line breaks (JDBC-493)
• Fixed: FBDatabaseMetaData.getTables does not list tables where rdb$relation_type is null (JDBC-494)
• Improvement: Character sets are now initialized lazily (JDBC-495)
  Under Excelsior Jet, the eager loading of character sets could lead to slow initialization if character sets were excluded from the build.
• Fixed: Memory leak caused by retaining blob handles until connection close (JDBC-497)

See the full release notes for more information.

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>3.0.1</version>

* The artifactId depends on your target Java version: jaybird-jdk18, or jaybird-jdk17

Documentation crowd-funding

The Firebird Project is currently holding a crowd-funding for the Firebird Developer Guide. Your donation is much appreciated!

See https://www.firebirdsql.org/en/doc-funding-2017/ for details.

Jaybird 3.0 is a big change from Jaybird 2.2 and earlier. The entire low-level implementation has been rewritten to be able to support protocol improvements in newer Firebird versions. We have also made changes with a stricter interpretation of the JDBC requirements, and removed some parts that were either obsolete or not functioning correctly.

Most notable changes in Jaybird 3:

• Support for wire protocol versions 11, 12, and 13 (without support for encryption and compression); protocol version 13 contributed by Hajime Nakagami
• Support for the Firebird 3 SRP (Secure Remote Password) authentication mechanism (contributed by Hajime Nakagami)
• Support for streaming backup and restore (contributed by Ivan Arabadzhiev)
• Improved Firebird 3 support
• Improved and stricter JDBC support (including improved java.time support, and more optional methods implemented)
• Initial JDBC 4.3 (Java 9) support (without real module support)
• New implementation of the native/embedded Type 2 driver using JNA (a jaybird .dll/.so is no longer needed)
• Improved character set handling
• Removal of (buggy) connection pool implementation
• Removal/replacement of (internal) GDS API

And a large number of smaller bug fixes, improvements, and changes.

We recommend that you do not consider Jaybird 3.0 a drop-in replacement for Jaybird 2.2, and study the release notes carefully. Test your application with Jaybird 3.0 before using it in production.

Jaybird 3.0 supports Firebird 2.0 and higher, on Java 7, 8 and 9. Basic Java 9 compatibility is provided through the Java 8 version of the driver.

See also:

• Jaybird 3.0.0 release notes
• Jaybird 3.0.0 downloads
• Instructions for Maven

The following has been changed or fixed in Jaybird 2.2.13:

• Improved: Support for Firebird 4 object name length of 63 characters (JDBC-467)
• Various improvements to thread safety and incomplete object validity checks. (JDBC-469) (JDBC-470)
  Some methods did not throw an SQLException when the object (ResultSet, Statement, Connection) was already closed. This sometimes lead to an unclear RuntimeException at a later point. In other cases an SQLException was thrown, even though the object was valid.
• Fixed: Generated keys query for table with space character (or any other character below \u00A0 that was not a-z, A-Z, 0-9, $, _, or :) in its (quoted) name returns empty generated keys result set (JDBC-481)

Known issues in Jaybird 2.2.13

• Connecting to Firebird 2.5 and earlier with a Firebird 3 fbclient.dll may be slow with native connections, see CORE-4658.
  Workaround is to connect to the IPv4 address instead of the hostname, or to use a Firebird 2.5 or earlier fbclient.dll.

See the full release notes for more information.

The release is also available on maven(*):

<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.13</version>

* The artifactId depends on your target Java version: jaybird-jdk18, jaybird-jdk17, or jaybird-jdk16.