Jaybird 3.0.0-beta-3 Release Notes


Jaybird 3 is still in development. This version is provided for testing purposes only. We'd appreciate your feedback, but we'd like to emphasize that this version is not intended for production.

The protocol implementation has been fundamentally rewritten and changes have been made for stricter JDBC conformance. As a result the driver might exhibit different behavior than previous versions. Read these release notes carefully to see if those differences are intentional.

Bug reports about undocumented changes in behavior are appreciated. Feedback can be sent to the Firebird-java mailing list or reported on the issue tracker http://tracker.firebirdsql.org/browse/JDBC.

1 General Notes

Jaybird is a JCA/JDBC driver suite to connect to Firebird database servers.

This driver is based on both the JCA standard for application server connections to enterprise information systems and the well-known JDBC standard. The JCA standard specifies an architecture in which an application server can cooperate with a driver so that the application server manages transactions, security, and resource pooling, and the driver supplies only the connection functionality. While similar to the JDBC XADataSource concept, the JCA specification is considerably clearer on the division of responsibility between the application server and driver.

1.1 About this version

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

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

1.2 Supported Firebird versions

Jaybird 3.0 was tested against Firebird 2.5.7, and 3.0.0, but should also support other Firebird versions from 2.0 and up.

Formal support for Firebird 1.x has been dropped (although in general we expect the driver to work). The Type 2 and embedded server JDBC drivers use JNA to access the Firebird client or embedded library.

This driver does not support InterBase servers due to Firebird-specific changes in the protocol and database attachment parameters that are sent to the server.

Jaybird 3.0 is the last version to support Firebird 2.0 and 2.1.

1.3 Supported Java versions

Jaybird 3.0 supports Java 7 (JDBC 4.1) and Java 8 (JDBC 4.2). Support for earlier Java versions has been dropped.

Rudimentary support for Java 9 (JDBC 4.3) is available using the Java 8 version, but real module support will not be available until Jaybird 3.1 (or even later).

Jaybird 3.0 is the last version to support Java 7.

1.4 Specification support

Jaybird supports the following specifications:

Specification Notes
JDBC 4.3 Driver implements all JDBC 4.3 methods for features supported by Firebird; Java 9 supported using the Java 8 driver.
JDBC 4.2 Driver implements all JDBC 4.2 methods for features supported by Firebird.
JDBC 4.1 Driver implements all JDBC 4.1 methods for features supported by Firebird.
JDBC 4.0 Driver implements all JDBC 4.0 interfaces and supports exception chaining.
JCA 1.0 Jaybird provides implementation of javax.resource.spi.ManagedConnectionFactory and related interfaces. CCI interfaces are not supported. Although Jaybird depends on the JCA 1.5 classes, JCA 1.5 compatibility is currently not guaranteed.
JTA 1.0.1 Driver provides an implementation of javax.transaction.xa.XAResource interface via JCA framework and XADataSource implementation.
JMX 1.2 Jaybird provides a MBean to manage Firebird servers and installed databases via JMX agent.

2 Getting Jaybird 3.0

2.1 Jaybird 3.0.0-beta-3

2.1.1 Maven

Jaybird 3.0.0-beta-3 is available from Maven central:

Groupid: org.firebirdsql.jdbc,
Artifactid: jaybird-jdkXX (where XX is 17 or 18).
Version: 3.0.0-beta-3

For example:


If your application is deployed to a Java EE application server, you will need to exclude the javax.resource:connector-api dependency, and add it as a provided dependency:


If you want to use Type 2 support (native, local or embedded), you need to explicitly include JNA 4.2.2 as a dependency:


We plan to make native and embedded support a separate library in future releases, and provide Firebird client libraries as Maven dependencies as well.

2.1.2 Download

You can download the latest versions from http://www.firebirdsql.org/en/jdbc-driver/

At minimum Jaybird 3.0 requires jaybird-3.0.0-beta-3.jar and connector-api-1.5.jar. You can also use jaybird-full-3.0.0-beta-3.jar as it includes the connector-api files.

If you deploy your application to a Java EE application server, then you must use jaybird-3.0.0-beta-3.jar (not -full!), and not include connector-api-1.5.jar as this dependency will be provided by your application server.

For getGeneratedKeys support you will need to include antlr-runtime-4.6.jar on your classpath.

For native, local or embedded support, you will need to include jna-4.2.2.jar on your classpath.

3 Upgrading from Jaybird 2.2 to Jaybird 3.0

3.1 Maven

Upgrade the version of the dependency to 3.0.0-beta-3. If you use native or embedded, you will no longer need the jaybird22.dll or libjaybird22.so, see the next section.

For more detailed instructions, see also the information on Maven in Getting Jaybird 3.0.

3.2 Manual install

If you manage your dependencies manually, you need to do the following:

  1. Replace the Jaybird library 2.2 with the 3.0
    • jaybird-2.2.x.jar with jaybird-3.0.0-beta-3.jar
    • jaybird-full-2.2.x.jar with jaybird-full-3.0.0-beta-3.jar
  2. If installed, remove antlr-runtime-3.4.jar and replace it with antlr-runtime-4.6.jar. This library is necessary for getGeneratedKeys support.

  3. If you use native (or embedded) you can remove the native library:
    • jaybird22.dll,
    • libjaybird22.so,
    • jaybird22_x64.jar or
    • libjaybird22_x64.so

    Instead you need to add jna-4.2.2.jar to the classpath of your application. This library is necessary for native, local and embedded support.

3.3 Gotcha's

3.3.1 Wildfly

When you use Jaybird 3 in Wildfly (or JBoss), you will need to add the module javax.xml.bind.api to your module to get it to work.

The minimal module.xml to use Jaybird 3 under Wildfly is:

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.firebirdsql">
    <resource-root path="jaybird-3.0.0-beta-3.jar"/>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
    <module name="javax.resource.api"/>
    <module name="javax.xml.bind.api"/> <!-- Add this -->

4 Jaybird 3.0.x changelog

4.1 Changes in Jaybird 3.0.0-beta-3

The following has been changed or fixed since Jaybird 3.0.0-beta-2

4.2 Changes in Jaybird 3.0.0-beta-2

The following has been changed or fixed since Jaybird 3.0.0-beta-1

5 What's new in Jaybird 3.0

For a full list of changes, see Firebird tracker for Jaybird 3.0.0.

5.1 Java support

5.1.1 Java 6

Support for Java 6 has been dropped.

5.1.2 Java 7 and 8

The driver supports Java 7 and 8 and provides improved support for JDBC 4.1 and JDBC 4.2 features.

The improved support includes

  • Support for java.time in set/get/updateObject
  • Support for java.math.BigInteger in set/get/updateObject
    Contrary to the support required by JDBC (BIGINT, VARCHAR and LONGVARCHAR), we also support it for SMALLINT, INTEGER, NUMERIC and DECIMAL). In the case of numeric and decimal, the value will be rounded for non-zero decimal fractions using the logic applied by BigDecimal.toBigInteger().
  • Support for getObject(int/String, Class<?>)
  • Support for setBinaryStream/setCharacterStream with no length or (long) length beyond Integer.MAX_VALUE
  • Support for large update counts (but not setLargeMaxRows)

5.1.3 Java 9

Jaybird currently does not formally support Java 9 (JDBC 4.3), although most of the JDBC 4.3 features have been implemented (in as far as they are supported by Firebird).

You can use the Java 8 driver under Java 9, but it is necessary to add the java.xml.bind module using --add-modules java.xml.bind.

Jaybird cannot be fully tested under Java 9 at this moment, as some of our tests fail due to recent changes, that prevent JMock (or specifically cglib) from dynamically generating classes.

5.2 Firebird support

Support for Firebird 1.0 and 1.5 has been dropped. See Firebird 1.0 and 1.5 no longer supported for details.

Firebird 2.1 support is improved with the implementation of wire protocol version 11.

Firebird 2.5 support is improved with the implementation of wire protocol version 12.

Firebird 3.0 support is improved with the (partial) implementation of wire protocol 13 and support for the Srp authentication plugin. Version 13 support does not yet provide Firebird 3.0 wire encryption and zlib compression. Wire encryption is planned for Jaybird 3.1. Support for zlib compression is not planned yet.

See also Jaybird and Firebird 3 on the wiki.

Support for protocol version 13 and the SRP authentication was contributed by Hajime Nakagami.

5.2.1 Other Firebird feature support

5.3 New low-level implementation

Jaybird 3.0 has a substantially rewritten low-level implementation (the wire protocol and native implementation) and a number of changes for JDBC conformance.

The rewrite of the low-level implementation was prompted by the new authentication (and wire encryption) in Firebird 3.0 (protocol version 13), and the fact that other improvements in the Firebird wire protocol (versions 11 and 12) were not yet available in the pure Java implementation in Jaybird. The old implementation of the wire protocol did not lend itself for - easily - supporting multiple protocol versions.

The new low-level implementation also means that the old GDS API (org.firebirdsql.gds.GDS) has been removed and is no longer available.

For the native, local and embedded support the use of jaybirdxx.dll/libjaybirdxx.so is no longer necessary. For more details, see Type 2 (native) and embedded driver.

5.4 Support for java.util.logging added

We have added support for java.util.logging, and made it the default logging implementation.

We have applied the following mapping for the log levels:

Jaybird log level jul log level
Logger.trace Level.FINER
Logger.debug Level.FINE
Logger.info Level.INFO
Logger.warn Level.WARNING
Logger.error Level.SEVERE
Logger.fatal Level.SEVERE

We have also added some options to control logging behavior:

5.5 Support for log4j 1.x removed

Support for Log4J 1.x has been removed. If you really need it, you can implement the interface org.firebirdsql.logging.Logger with a public constructor accepting a single String parameter (the logger name).

To instruct Jaybird to use this logger implementation, specify the system property org.firebirdsql.jdbc.loggerImplementation with the class name.

Say you have created the following implementation

package org.example.jaybird.logging;

public class Log4jLogger implements org.firebirdsql.logging.Logger {
    public Log4jLogger(String name) {
        // create the logger    
    // implementation of interface

You will need to specify:


5.6 IPv6 address literal support in connection string

Added support for IPv6 address literals in the connection string. This is only supported for the modern-style connection URLs, using the RFC2732 format:




IPv6 literals are not supported in the legacy URL format (the <host>[/port]:<path-or-alias> format).

5.7 Potentially breaking changes

Jaybird 3.0 contains a number of changes that might break existing applications.

See also Compatibility changes for details.

5.7.1 Specifying connection character set is now required

Jaybird 3.0 requires you to specify the connection character set by either specifying encoding=<Firebird encoding> or charSet=<Java encoding>.

For more information see: Connection rejected without an explicit character set

5.7.2 ANTLR 4 runtime

The generated keys functionality now requires ANTLR 4.6. Make sure to replace antlr-runtime-3.4.jar with the antlr-runtime-4.6.jar included in the distribution zip. If you use maven this will happen automatically.

As in previous versions: if the ANTLR runtime is not on the classpath, then the generated keys functionality will not be available.

5.7.3 Handling of character set OCTETS

Columns of type CHAR and VARCHAR with character set OCTETS are now handled as JDBC type BINARY and VARBINARY, respectively (JDBC-240)

See also Character set OCTETS handled as JDBC (VAR)BINARY.

5.7.4 Changes to character set handling

We reimplemented the character set handling in Jaybird which may lead to different behavior, especially when using NONE as the connection character set.

See also Character set handling.

5.8 Other fixes and changes

5.9 Removal of deprecated classes and packages

See Removal of deprecated classes, packages and methods in Compatibility changes for more details.

6 Known Issues

7 Compatibility changes

Jaybird 3.0 introduces some changes in compatibility and announces future breaking changes.

The changes due to the new protocol implementation and/or JDBC conformance are listed below.

The list might not be complete, if you notice a difference in behavior that is not listed, please report it as bug. It might have been a change we forgot to document, but it could just as well be an implementation bug.

7.1 Character set handling

7.1.1 Character set OCTETS handled as JDBC (VAR)BINARY

Columns of type CHAR(n) CHARACTER SET OCTETS and VARCHAR(n) CHARACTER SET OCTETS are now handled as JDBC type java.sql.Types.BINARY and java.sql.Types.VARBINARY, respectively.

The connection property octetsAsBytes no longer has any effect, metadata and usage will always be (VAR)BINARY.

With this change the getters (on result set/callable statement) and setters (prepared/callable statement) and update methods (result set) for columns of this type have been restricted to:

  • set/get/updateNull
  • get/set/updateBytes
  • get/set/updateBinaryStream
  • get/set/updateAsciiStream
  • get/set/updateString (using the default encoding or connection encoding)
  • get/set/updateCharacterStream (using the default encoding or connection encoding)
  • get/set/updateObject (with String, byte[], InputStream, Reader)

Other getters/setters/updaters or object types supported for 'normal' (VAR)CHAR fields are not available.

7.1.2 Connection character set NONE

Jaybird will now use the (VAR)CHAR or BLOB SUB_TYPE TEXT character set information for decoding. This means that when using connection character set NONE that columns which have an explicit character set will be decoded and encoded using that character set instead of using the platform default encoding (or explicitly specified Java character set when specifying both encoding=NONE and charSet=<some java charset>).

This may lead to unexpected character conversions if - for example - you have always been reading and writing Cp1251 data from a WIN1252 column: it will now be read as Cp1252. You will need to convert the column and data to the right character set.

7.1.3 Connection rejected without an explicit character set

If no explicit character set has been set, Jaybird 3.0 will reject the connection with an SQLNonTransientConnectionException with message "Connection rejected: No connection character set specified (property lc_ctype, encoding, charSet or localEncoding). Please specify a connection character set (eg property charSet=utf-8) or consult the Jaybird documentation for more information." (JDBC-446)

In Jaybird 2.2 and earlier, Jaybird would default to connection character set NONE if no character set had been specified (through encoding and/or charSet). This can result in incorrect character set handling when the database is used from different locales.

To prevent potential data-corruption, we no longer allow connecting without an explicit connection character set.

To address this change, explicitly set the connection character set using one of the following options:

  • Use connection property encoding (or lc_ctype) with a Firebird character set name.

    Use encoding=NONE for the old default behavior (with some caveats, see other sections).

  • Use connection property charSet (or localEncoding) with a Java character set name.

  • Use a combination of encoding and charSet, if you want to reinterpret a Firebird character set in a Java character set other than the default mapping.

  • By providing a default Firebird character set with system property org.firebirdsql.jdbc.defaultConnectionEncoding. Jaybird will apply the specified character set as the default when no character set is specified in the connection properties.

    This property only supports Firebird character set names.

    Use -Dorg.firebirdsql.jdbc.defaultConnectionEncoding=NONE to revert to the old behavior (with some caveats, see other sections).

7.2 Logging

Support for log4j has been removed, and we now default to java.util.logging. The previous default was no logging.

See also Support for java.util.logging added and Support for log4j 1.x removed.

7.3 Exceptions

7.4 Firebird 1.0 and 1.5 no longer supported

Support for Firebird 1.0 and 1.5 has been dropped in Jaybird 3.0. In general we expect the driver to remain functional, but chances are certain metadata (eg DatabaseMetaData) will break if we use features introduced in newer versions.

In general we will no longer fix issues that only occur with Firebird 1.5 or earlier.

7.5 Java 5 and 6 no longer supported

Support for Java 6 (JDBC 4.0) has been dropped in Jaybird 3.0. The Jaybird 3.0 sources no longer compile with Java 6 due to use of Java 7 language features and JDBC 4.1 specific features.

Support for Java 5 was already removed with Jaybird 2.2.8.

7.6 Stricter JDBC compliance

In Jaybird 3.0 a number of changes were made for stricter compliance to the JDBC specification.

7.6.1 General

Most methods in JDBC objects are required to throw an SQLException if the object is closed or otherwise invalid. Not all Jaybird methods followed this requirement. We have improved this in Jaybird 3, but there are still some cases left to fix (which we might do in point releases).

7.6.2 Statement

Unless explicitly indicated, changes also apply to PreparedStatement and CallableStatement

  • Generated keys ResultSet is only available through getGeneratedKeys.

    The generated keys ResultSet from a statement is no longer available through getResultSet, but only through getGeneratedKeys as the JDBC specification does not consider the generated keys ResultSet a normal ResultSet.

    This applies to statements executed (or prepared) using:

    • Statement.execute(String, int) or Statement.executeUpdate(String, int) with value Statement.RETURN_GENERATED_KEYS,
    • Statement.execute(String, int[]) or Statement.executeUpdate(String, int[]),
    • Statement.execute(String, String[]) or Statement.executeUpdate(String, String[]),
    • Connection.prepareStatement(String, int) with value Statement.RETURN_GENERATED_KEYS,
    • Connection.prepareStatement(String, int[]),
    • Connection.prepareStatement(String, String[]).

    This change does not apply to executing INSERT ... RETURNING ... as a normal statement.

  • Update count immediately available after executing generated keys queries.

    Previously the update count of a generated keys query was only available after calling getMoreResults followed by a call to getUpdateCount. This change means that executeUpdate will now correctly return the update count (usually 1) instead of -1. The same applies to calling getUpdateCount after execute (without the need to call getMoreResults).

    For the definition of generated keys queries see the previous item.

  • Use of function escapes ({fn ...}) not defined in the JDBC standard will now throw an FBSQLParseException, previously the escape was removed and the function was used as is.

7.6.3 PreparedStatement

Unless explicitly indicated, changes also apply to CallableStatement

  • Method setUnicodeStream now always throws an SQLFeatureNotSupportedException. The previous implementation did not conform to the (deprecated) JDBC requirements and instead behaved like setBinaryStream.

    For the behavior in Jaybird 2.2 and earlier, use setBinaryStream. Otherwise use setCharacterStream.

  • Methods setNString, setNClob, and setNCharacterStream will now behave as their counterpart without N (ie setString, setClob, and setCharacterStream)

    This implementation is not compliant with the JDBC requirements for NVARCHAR/NCHAR/NCLOB support, it is only provided for compatibility purposes.

7.6.4 CallableStatement

  • Methods getNString, getNClob, and getNCharacterStream will now behave as their counterpart without N (ie getString, getClob, and getCharacterStream)

    This implementation is not compliant with the JDBC requirements for NVARCHAR/NCHAR/NCLOB support, it is only provided for compatibility purposes.

7.6.5 ResultSet

  • Method getUnicodeStream now always throws an SQLFeatureNotSupportedException. The previous implementation did not conform to the (deprecated) JDBC requirements and instead behaved like getBinaryStream.

    For the behavior in Jaybird 2.2 and earlier, use getBinaryStream. Otherwise use getCharacterStream.

  • Methods getNString, updateNString, getNClob, updateNClob, getNCharacterStream, and updateNCharacterStream will now behave as their counterpart without N (ie getString, updateString, getClob, updateClob, getCharacterStream, and updateCharacterStream)

    This implementation is not compliant with the JDBC requirements for NVARCHAR/NCHAR/NCLOB support, it is only provided for compatibility purposes.

7.6.6 Clob

  • The Clob implementations of the driver now also implement NClob so they can be returned from getNClob.

    This implementation is not compliant with the JDBC requirements for NVARCHAR/NCHAR/NCLOB support, it is only provided for compatibility purposes.

7.6.7 DatabaseMetaData Pattern parameters

The java.sql.DatabaseMetaData implementation has been changed to follow the JDBC requirements for object name pattern or object name parameters (referred to as patterns in the rest of this section).

These changes affect all methods that accept one or more pattern or name parameters and return a ResultSet. This includes, but is not limited to, getTables and getColumns.

In Firebird unquoted object names are stored upper case, while quoted object names are stored as is. The JDBC specification states that the pattern must match the object name as stored in the database. This means the pattern should be case sensitive.

The changes made are as follows:

  • null will always be interpreted as "%" (before this rule was applied inconsistently)
  • Empty string will no longer match (ie they are no longer interpreted as "%") unless explicitly allowed by the method javadoc (usually only the catalogPattern and schemaPattern, which are always ignored by Jaybird as Firebird currently doesn't support this)
  • Double quotes around a pattern will no longer be stripped, and therefor will now never match existing object names (unless those double quotes are part of the actual object name)
  • The driver will no longer try the uppercase variant of the provided pattern(s) if the original value(s) did not yield a result
  • Object name parameters that are not patterns (as indicated by the absence of Pattern in the parameter name) will no longer have backslashes removed

Review your DatabaseMetaData usage and make the following changes:

  • Empty string parameters: replace with "%" (or null)
  • Double quotes around patterns: remove the double quotes
  • Casing of patterns should be reviewed for correctness
  • Non-pattern parameters containing \ should be reviewed for correctness

Some examples:

CREATE TABLE tablename ( -- tablename is stored as TABLENAME in metadata
   column1 INTEGER,      -- column1 is stored as COLUMN1 in metadata
   "column2" INTEGER     -- "column2" is stored as column2 in metadata

In Jaybird 2.2 using getColumns(null, null, "tablename", "column%") returns COLUMN1(!). In Jaybird 3.0 this produces no rows as tablename does not match TABLENAME.

Changing the query to getColumns(null, null, "TABLENAME", "column%") in Jaybird 2.2 and 3.0 produces only one row (column2), as COLUMN1 does not match column%.

In Jaybird 2.2 using getColumns(null, null, "\"TABLENAME\"", "column%") returns column2, in Jaybird 3.0 this produces no rows as quotes are no longer stripped.

In Jaybird 2.2 using getColumns(null, null, "TABLENAME", "") returns all columns of the table, in Jaybird 3.0 this produces no rows as empty string does not match any column. Instead, you should use getColumns(null, null, "TABLENAME", "%"). getTables

Apart from the change described above, the following has changed for getTables

  • The result set is now sorted by TABLE_TYPE and then by TABLE_NAME as required by the JDBC API doc, previously we only only sorted on TABLE_NAME.
  • Support for table type "GLOBAL TEMPORARY" added for databases with ODS 11.2 or higher (Firebird 2.5 or higher). In previous versions, the global temporary tables were reported as normal tables (type "TABLE")

7.7 Removal of old GDS API

The old GDS API (org.firebirdsql.gds.GDS) and its implementations have been removed. This removal includes a number of related classes and methods. Classes and interfaces in the org.firebirdsql.gds package and sub-packages that still exist may have moved to other packages, or may have a changed API.

In general we advise you to not use the low-level implementation directly. If you see something that is only possible through the low-level API, please file an improvement ticket or create a pull request to add it to the JDBC or management classes.

7.8 Type 2 (native) and embedded driver

Jaybird no longer needs a jaybirdxx.dll or libjaybirdxx.so for the Type 2 and embedded driver. Jaybird now uses JNA to access the client library.

If you want to use the Type 2 driver, or Firebird embedded, then you need to include the jna-4.2.2.jar on the classpath.

When using Maven, you need to specify the dependency on JNA yourself, as we don't depend on it by default:


The fbclient.dll, fbembed.dll, libfbclient.so, or libfbembed.so need to be on the path, or the location needs to be specified in the system property jna.library.path.

In the future we will move the Type 2 support to a separate library and provide JNA-compatible jars that provide the native libraries of a specific Firebird version.

7.9 Removal of deprecated classes, packages and methods

7.9.1 DataSource and connection pooling

The classes in org.firebirdsql.pool and org.firebirdsql.pool.sun have been removed completely, with the exception of org.firebirdsql.pool.FBSimpleDataSource. This class has been moved to org.firebirdsql.ds.FBSimpleDataSource. A subclass with the same name is kept in org.firebirdsql.pool for backwards compatibility. This subclass will be removed in Jaybird 3.1.

With this change, there are no javax.sql.DataSource implementations in Jaybird that provide connection pooling (the javax.sql.ConnectionPoolDataSource implementations are for use by a connection pool and not a connection pool themselves). Either use the connection pool provided by your application server, or use a third-party connection pool like c3p0, Apache DBCP or HikariCP.

The class org.firebirdsql.jca.FBXADataSource has been removed as well. Its replacement is org.firebirdsql.ds.FBXADataSource (which was introduced in Jaybird 2.2).

7.9.2 FirebirdSavepoint

All method definitions in the interface org.firebirdsql.jdbc.FirebirdSavepoint were removed, and methods referencing this interface in org.firebirdsql.jdbc.FirebirdConnection have been removed as the interface duplicated the java.sql.Savepoint interface and related methods in java.sql.Connection. The interface itself remains for potential future Firebird-specific extensions.

7.9.3 Reducing visibility of implementation

The following classes, interfaces and/or methods had their visibility reduced as they are implementation artifacts, and should not be considered API:

  • org.firebirdsql.jdbc.FBDriverPropertyManager (to package private)

7.9.4 FBMaintenanceManager

In FBMaintenanceManager the following changes have been made:

  • getLimboTransactions() will return long[] instead of int[]
  • limboTransactionsAsList() will return List<Long> instead of List<Integer>
  • getLimboTransactionsAsLong() (introduced in 2.2.11) has been removed in favor of getLimboTransactions()
  • limboTransactionsAsLongList (introduced in 2.2.11) has been removed in favor of limboTransactionsAsList

These methods were previously not defined in the MaintenanceManager interface.

7.10 Miscellaneous

7.11 Breaking changes for Jaybird 3.1

With Jaybird 3.1 the following breaking changes will be introduced.

7.11.1 Dropping support for Firebird 2.0 and 2.1

Jaybird 3.1 will drop support for Firebird 2.0 and 2.1. In general we expect the driver to remain functional, but chances are certain metadata (eg DatabaseMetaData) will break if we use features introduced in newer versions.

7.11.2 Dropping support for Java 7

Jaybird 3.1 will very likely drop support for Java 7 (this decision is not final yet).

7.11.3 Removal of deprecated methods

The following methods will be removed in Jaybird 3.1:

  • CharacterTranslator.getMapping(), use CharacterTranslator.getMapping(char) instead.

    Complete removal of the character translation support is also being considered, as similar effects can be achieved by a custom encoding implementation.

  • GDSHelper.iscVaxInteger(byte[] buffer, int pos, int length) use VaxEncoding.iscVaxInteger(byte[] buffer, int startPosition, int length) instead.
  • GDSHelper.iscVaxLong(byte[] buffer, int pos, int length) use VaxEncoding.iscVaxLong(byte[] buffer, int startPosition, int length) instead.
  • MaintenanceManager.commitTransaction(int transactionId), use MaintenanceManager.commitTransaction(long transactionId) instead.
  • MaintenanceManager.rollbackTransaction(int transactionId), use MaintenanceManager.rollbackTransaction(long transactionId) instead.

7.11.4 Removal of deprecated constants

The following constants will be removed in Jaybird 3.1:

  • All SQL_STATE_* constants in FBSQLException, FBResourceTransactionException, FBResourceException, and FBDriverNotCapableException will be removed. Use equivalent constants in org.firebirdsql.jdbc.SQLStateConstants.