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
March 11, 2013
FDB release 1.0 is out: http://pypi.python.org/pypi/fdb

Improvements:
  • Removed dependency on presence of fbclient library at import time. This caused some confusion to new users when fdb install failed when Firebird was not (yet) installed.
Bugs Fixed:
FDB release 1.0 is out: http://pypi.python.org/pypi/fdb

Improvements:
  • Removed dependency on presence of fbclient library at import time. This caused some confusion to new users when fdb install failed when Firebird was not (yet) installed.
Bugs Fixed:
February 03, 2013

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

This release contains the following fixes:

  • Fixed: FBMaintenanceManager.listLimboTransactions() reports incorrect transaction id when the result contains multi-site transactions in limbo (JDBC-266)
  • Fixed: Calling PreparedStatement.setClob(int, Clob) with a non-Firebird Clob (eg like Hibernate does) or calling PreparedStatement.setClob(int, Reader) throws FBSQLException: “You can't start before the beginning of the blob” (JDBC-281)
  • Fixed: Connection property types not properly processed from isc_dpb_types.properties (JDBC-284)
  • Fixed: JNI implementation of parameter buffer writes incorrect integers (JDBC-285, JDBC-286)
  • Changed: Throw SQLException when calling execute, executeQuery, executeUpdate and addBatch methods accepting a query string on a PreparedStatement or CallableStatement as required by JDBC 4.0 (JDBC-288)
  • Fixed: LIKE escape character JDBC escape ({escape '<char>'}) doesn't work (JDBC-290)
  • Added: Support for a connect timeout using connection property connectTimeout. This property can be specified in the JDBC URL or Properties object or on the DataSource. If the connectTimeout property is not specified, the general DriverManager property loginTimeout is used. The value is the timeout in seconds. (JDBC-295)

The release is also available on maven(*):

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

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

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

This release contains the following fixes:

  • Fixed: FBMaintenanceManager.listLimboTransactions() reports incorrect transaction id when the result contains multi-site transactions in limbo (JDBC-266)
  • Fixed: Calling PreparedStatement.setClob(int, Clob) with a non-Firebird Clob (eg like Hibernate does) or calling PreparedStatement.setClob(int, Reader) throws FBSQLException: “You can't start before the beginning of the blob” (JDBC-281)
  • Fixed: Connection property types not properly processed from isc_dpb_types.properties (JDBC-284)
  • Fixed: JNI implementation of parameter buffer writes incorrect integers (JDBC-285, JDBC-286)
  • Changed: Throw SQLException when calling execute, executeQuery, executeUpdate and addBatch methods accepting a query string on a PreparedStatement or CallableStatement as required by JDBC 4.0 (JDBC-288)
  • Fixed: LIKE escape character JDBC escape ({escape '<char>'}) doesn't work (JDBC-290)
  • Added: Support for a connect timeout using connection property connectTimeout. This property can be specified in the JDBC URL or Properties object or on the DataSource. If the connectTimeout property is not specified, the general DriverManager property loginTimeout is used. The value is the timeout in seconds. (JDBC-295)

The release is also available on maven(*):

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

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

February 01, 2013
Roger Vellacott Recently we learned with sorrow of the death of Roger Vellacott in November, from cancer.

Roger was a significant contributor to Firebird and its community from the earliest days, as a voting member of the Firebird Foundation and a regular contributor to support forums. The company he led, Passfield Data Systems, in Bath, U.K., is a Firebird sponsor.

We extend our sincere condolences to Roger's family and his colleagues at Passfield.

Firebird Project
Roger Vellacott Recently we learned with sorrow of the death of Roger Vellacott in November, from cancer.

Roger was a significant contributor to Firebird and its community from the earliest days, as a voting member of the Firebird Foundation and a regular contributor to support forums. The company he led, Passfield Data Systems, in Bath, U.K., is a Firebird sponsor.

We extend our sincere condolences to Roger's family and his colleagues at Passfield.

Firebird Project