Jaybird 3.0.9 Release Notes

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. 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.

女主直播给粉丝脱内衣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 application with Jaybird 3.0 before using it in production.

Although Jaybird 3 is still maintained, we recommend updating to Jaybird 4.

女主直播给粉丝脱内衣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 .

2 Support

If you need support with Jaybird, join the and mailing list. You can subscribe by sending an email to firebird-java+subscribe@googlegroups.com.

Looking for professional support of Jaybird? Jaybird is now part of the .

See also Where to get help

2.1 Supported Firebird versions

Jaybird 3.0 was tested against Firebird 2.5.9, and 3.0.5, but should also support other Firebird versions from 2.0 and up. Firebird 4 is not fully supported in Jaybird 3.x.

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.

2.1.1 Notes on Firebird 3 support

Jaybird 3.0.4 added support for wire protocol encryption and database encryption. See Wire encryption support and Database encryption support女主直播给粉丝脱内衣 for more information.

Jaybird 3.0 does not support the Firebird 3 zlib compression.

2.1.2 Notes on Firebird 4 support

女主直播给粉丝脱内衣Jaybird 3.0 can connect and query Firebird 4. Longer object names are supported.

The new data types introduced in Firebird 4 are not supported. Support for data types like DECFLOAT and NUMERIC/DECIMAL with precision higher than 18 will be introduced in Jaybird 4.

The Srp256 authentication plugin is supported, but the other SrpNNN plugins are not supported; support for these plugins has been introduced in Jaybird 4.

女主直播给粉丝脱内衣Jaybird 3.0 does not support the Firebird 4 zlib compression.

For improved support of Firebird 4, we recommend updating to Jaybird 4.

2.2 Supported Java versions

Jaybird 3 supports Java 7 (JDBC 4.1), Java 8 (JDBC 4.2), and Java 9 and higher (JDBC 4.3). Support for earlier Java versions has been dropped.

For the time being, there will be no Java 9+ specific builds, the Java 8 builds have the same source and all JDBC 4.3 related functionality.

Given the limited support period for Java 9 and higher versions, we limit support on those versions to the most recent LTS version and the latest release. As of May 2020, this means Java 11 and Java 14 are supported.

Jaybird 3.0 is not modularized, but since Jaybird 3.0.3, it declares the automatic module name org.firebirdsql.jaybird.

2.3 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 and higher 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.

3 Getting Jaybird 3.0

3.1 Jaybird 3.0.9

3.1.1 Maven

女主直播给粉丝脱内衣Jaybird 3.0.9 is available from Maven central:

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

女主直播给粉丝脱内衣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.4.0 as a dependency:


For Windows and Linux, you can add the org.firebirdsql.jdbc:fbclient dependency on your classpath to provide the native libraries for the native and local protocol. Be aware that this dependency does not support embedded.

See also Type 2 (native) and embedded driver.

3.1.2 Download

You can download the latest versions from http://1688shucai.com/en/jdbc-driver/

At minimum Jaybird 3.0 requires jaybird-3.0.9.jar and connector-api-1.5.jar. You can also use jaybird-full-3.0.9.jar which includes the connector-api files.

If you deploy your application to a Java EE application server, then you must use jaybird-3.0.9.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.7.jar on your classpath.

For native, local or embedded support, you will need to include jna-4.4.0.jar on your classpath. See also Type 2 (native) and embedded driver.

4 Upgrading from Jaybird 2.2 to Jaybird 3.0

4.1 Maven

Upgrade the version of the dependency to 3.0.9. 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.

4.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.9.jar
    • jaybird-full-2.2.x.jar with jaybird-full-3.0.9.jar
  2. If installed, remove antlr-runtime-3.4.jar and replace it with antlr-runtime-4.7.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.4.0.jar to the classpath of your application. This library is necessary for native, local and embedded support. For more information, see Type 2 (native) and embedded driver

4.3 Gotcha’s

If you find a problem while upgrading, or other bugs: please report it on .

5 Jaybird 3.0.x changelog

5.1 Changes in Jaybird 3.0.9

The following has been changed or fixed since Jaybird 3.0.8:

5.1.1 Known issues in Jaybird 3.0.9

See Known Issues

5.2 Changes in Jaybird 3.0.8

The following has been changed or fixed since Jaybird 3.0.7:

5.3 Changes in Jaybird 3.0.7

The following has been changed or fixed since Jaybird 3.0.6

5.4 Changes in Jaybird 3.0.6

The following has been changed or fixed since Jaybird 3.0.5

5.5 Changes in Jaybird 3.0.5

The following has been changed or fixed since Jaybird 3.0.4

5.6 Changes in Jaybird 3.0.4

The following has been changed or fixed since Jaybird 3.0.3

5.7 Changes in Jaybird 3.0.3

The following has been changed or fixed since Jaybird 3.0.2

5.8 Changes in Jaybird 3.0.2

女主直播给粉丝脱内衣The following has been changed or fixed since Jaybird 3.0.1

5.9 Changes in Jaybird 3.0.1

The following has been changed or fixed since Jaybird 3.0.0

5.10 Changes in Jaybird 3.0.0

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

5.11 Changes in Jaybird 3.0.0-beta-3

女主直播给粉丝脱内衣The following has been changed or fixed since Jaybird 3.0.0-beta-2

5.12 Changes in Jaybird 3.0.0-beta-2

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

6 What’s new in Jaybird 3.0

For a full list of changes, see .

6.1 Java support

6.1.1 Java 6

女主直播给粉丝脱内衣Support for Java 6 has been dropped.

6.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)

6.1.3 Java 9 and higher

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

For compatibility with Java 9+ modules, versions 2.2.14 and 3.0.3 introduced the automatic module name org.firebirdsql.jaybird女主直播给粉丝脱内衣. This guarantees a stable module name for Jaybird, and allows for future modularization of Jaybird.

You can use the Java 8 driver under Java 9+. Contrary to earlier Jaybird 3.0 test releases, it is not necessary to add the java.xml.bind module using --add-modules java.xml.bind女主直播给粉丝脱内衣, as we removed its use (see caveat below for the Java 7 version of Jaybird).

Given the limited support period for Java 9 and higher versions, we limit support on those versions to the most recent LTS version and the latest release. As of November 2019, this means Java 11 and Java 13 are supported.

We recommend to only use the Java 8 version of Jaybird with Java 9+, and not use the Java 7 version of Jaybird. The Java 7 version doesn’t implement all of the JDBC 4.3 features that are implemented in the Java 8 version. In addition, since Jaybird 3.0.4, the Java 7 version of Jaybird needs the java.xml.bind module, where the Java 8 version doesn’t need that module.

6.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 and Srp256 (Jaybird 3.0.5) authentication plugins. Version 13 support provides Firebird 3.0 wire encryption support since Jaybird 3.0.4. Support for zlib compression is not planned yet.

See also on the wiki.

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

Partial Firebird 4 support:

For improved support of Firebird 4, we recommend updating to Jaybird 4.

6.2.1 Other Firebird feature support

  • Add support for streaming backup and restore ()
    This feature was contributed by

6.2.2 Limited support for new Firebird 4 data types

For improved support of Firebird 4 datatypes, we recommend updating to Jaybird 4.

Jaybird 3 does not support the new Firebird 4 data types TIME WITH TIME ZONE, TIMESTAMP WITH TIME ZONE, DECFLOAT and NUMERIC/DECIMAL with precision greater than 18. As an accommodation, Jaybird 3.0.9 and higher has limited support for the following Firebird connection properties:

  • dataTypeBind (alias: set_bind) which accepts a list of semicolon-separated bind definitions. See details below in Notes on dataTypeBind.
  • sessionTimeZone (alias: session_time_zone) configures the server-side session time zone used for conversion of WITH TIME ZONE to WITHOUT TIME ZONE and values generated by CURRENT_TIME, LOCALTIME, etc.
    Valid values are Firebird time zone names or offsets. See also the Firebird 4 documentation. For important caveats, see Notes on sessionTimeZone.

These properties can be used as connection properties with DriverManager. When specified in a JDBC URL, make sure to encode the ; in a dataTypeBind value with %3B. For Jaybird data sources, the properties must be set using setNonStandardProperty as corresponding setters have not been defined.

To be able to use WITH TIME ZONE types with Jaybird 3, you must use dataTypeBind=time with time zone to legacy;timestamp with time zone to legacy. Setting sessionTimeZone is optional, see also Notes on sessionTimeZone.

We recommend using varchar for decfloat and numeric/decimal(38) (as shown in the next section) because that will allow you to use to full range of values without overflow or loss of precision through get/setBigDecimal. Alternatively, you can use double precision, although this may result in overflow for very large decfloat(34) values.

Important: These features requires Firebird 4 beta 2 or higher (or a snapshot build version or later). It will be ignored in builds before 1481 as the necessary database parameter buffer item does not exist, and it will raise an error in versions between 1481 and 1682 as there the DPB item points to the removed DPB item isc_time_zone_bind. Notes on dataTypeBind

Firebird 4 (build or later) introduced the SET BIND statement and isc_dpb_set_bind女主直播给粉丝脱内衣 DPB item. This allows you to define data type conversion rules for compatibility or ease of processing data.

In Jaybird this feature is exposed as connection property dataTypeBind (alias set_bind). The value of this connection property is a semicolon-separated list of data type bind definitions.

A data type bind definition is of the form <from-type> TO <to-type>. A definition is the same as the second half of a SET BIND statement after the OF. See the Firebird documentation of SET BIND for more information. Invalid values or impossible mappings will result in an error on connect.

When using the dataTypeBind connection property in a JDBC URL, the semicolons of the list need to be encoded as %3B, as semicolons in the JDBC URL are an alternative to & as the separator between properties.

女主直播给粉丝脱内衣For example:

String jdbcUrl = "jdbc:firebirdsql://localhost/database?charSet=utf-8"
        + "&dataTypeBind=decfloat to varchar%3Btimestamp with time zone to legacy

When the property is set through a Properties object or a DataSource configuration, encoding the semicolon is not necessary or possible, and will result in errors.

女主直播给粉丝脱内衣For example:

Properties props = new Properties();
        "decfloat to varchar;timestamp with time zone to legacy"

Values set through this connection property will be the session default configuration, which means that they are retained (or reverted to) when executing ALTER SESSION RESET.

This feature replaces the connection properties timeZoneBind and decfloatBind from earlier Jaybird 4 versions. The timeZoneBind and decfloatBind properties are no longer supported.

To remap the Firebird 4 types, you will need to specify:

"decfloat to varchar;numeric(38) to varchar;decimal(38) to varchar" +
  ";time with time zone to legacy;timestamp with time zone to legacy"

Instead of legacy, you can also explicitly specify time and timestamp respectively. Notes on sessionTimeZone

In Jaybird 3 sessionTimeZone will only configure the server-side session time zone. Client-side, Jaybird will continue to use the JVM default time zone for parsing the value to the java.sql.Time/Timestamp/Date types. In Jaybird 4, this property will also configure client-side parsing of values to these legacy types.

When Jaybird 3 and Firebird 4 are hosted on machines with different time zone settings, setting sessionTimeZone can result in changes in current time values (eg for CURRENT_TIME) as Firebird 4 will base these values on the session time zone.

Setting sessionTimeZone女主直播给粉丝脱内衣 to the JVM default time zone will yield the best (ie correct) values, but not setting it (and thus using the server default) will retain behaviour that is backwards compatible with behaviour of previous versions of Jaybird.

When setting sessionTimeZone, we recommend to use the long-form time zone names (eg Europe/Amsterdam) and not the short-form ids (eg CET).

In general, we recommend not setting this property, or setting it to the default JVM time zone. If you set it to a different time zone, then we recommend that you do not use the legacy java.sql.Time/Timestamp/Date types, but instead use java.time.LocalTime/LocalDateTime/LocalDate.

6.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.

6.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:

6.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:


6.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 format:




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

6.7 Wire encryption support

女主直播给粉丝脱内衣Added in 3.0.4, back-ported from Jaybird 4

Jaybird 3.0.4 adds support for the Firebird 3 ARC4 wire encryption. The encryption is configured using the connection property wireCrypt, with the following (case-insensitive) values:

The default value acts as ENABLED for pure Java connections, for JNA (native) connections this wil use the fbclient default (either Enabled or the configured value of WireCrypt from a firebird.conf read by the native library).

Connection property wireCrypt=REQUIRED will not女主直播给粉丝脱内衣 reject unencrypted connections when connecting to Firebird 2.5 or lower. This behavior matches the Firebird 3 client library behavior. The value will also be ignored when using native connections with a Firebird 2.5 client library.

Using wireCrypt=DISABLED when Firebird 3 or higher uses setting WireCrypt = Required (or vice versa) will yield error “Incompatible wire encryption levels requested on client and server” (error: isc_wirecrypt_incompatible / 335545064).

The same error is raised when connecting to Firebird 3 and higher with a legacy authentication user with connection property wireCrypt=REQUIRED.

女主直播给粉丝脱内衣Alternative wire encryption plugins are currently not supported, although we made some preparations to support this. If you want to develop such a plugin, contact us on the Firebird-Java mailing list so we can work out the details of adding plugin support.


女主直播给粉丝脱内衣The implementation comes with a number of caveats:

6.8 Database encryption support

Added in 3.0.4. This feature was sponsored by IBPhoenix.

Jaybird 3.0.4 adds support for Firebird 3 database encryption callbacks in the pure Java implementation of the version 13 protocol.

The current implementation is simple and only supports replying with a static value from a connection property. Be aware that a static value response for database encryption is not very secure as it can easily lead to replay attacks or unintended key exposure.

女主直播给粉丝脱内衣Future versions of Jaybird (likely 4, maybe 5) will introduce plugin support for database encryption plugins that require a more complex callback.

The static response value of the encryption callback can be set through the dbCryptConfig connection property. Data sources and ServiceManager implementations have an equivalent property with the same name. This property can be set as follows:

Because of the limitation of connection URL parsing, we strongly suggest to avoid plain string values with & or ;. Likewise, avoid : so that we can support other prefixes similar to base64: in the future. If you need these characters, consider using a base64 encoded value instead.

For service operations, as implemented in the org.firebirdsql.management package, Firebird requires the KeyHolderPlugin configuration to be globally defined in firebird.conf. Database-specific configuration in databases.conf will be ignored for service operations. Be aware that some service operations on encrypted databases are not supported by Firebird 3 (eg gstat equivalents other than gstat -h or gstat -e).

Other warnings and limitations

6.9 Case sensitive user names

女主直播给粉丝脱内衣Jaybird 3.0.6 adds support for case sensitive user names.

Case sensitive user names were introduced in Firebird 3. A case sensitive user name must be enclosed in double quotes. Similar to other quoted object names in Firebird, quoted user names can contain (almost) the full range of UNICODE_FSS女主直播给粉丝脱内衣 characters, including whitespace, etc.

For example, to login with the case sensitive user name CaseSensitive, use:

DriverManager.getConnection(url, "\"CaseSensitive\"", password); 

Normal, case insensitive, user names can also be enclosed in double quotes. This follows the same rules as applied to table, column and other object names in Firebird, so the user name must then be in upper case, eg instead of sysdba, use "SYSDBA".

女主直播给粉丝脱内衣If a user name contains double quotes, it must be escaped by another double quote. A singular double quote within a user name is a syntax error and will truncate the user name, leading to a login failure (unless a user exists with the truncated name and the same password).

6.10 Connection property ignoreProcedureType

Jaybird 3.0.6 adds a boolean connection property ignoreProcedureType.

On Firebird 2.1 and higher, Jaybird will use the procedure type information from the database metadata to decide how to execute CallableStatement. When a procedure is selectable, Jaybird will automatically transform a call-escape or EXECUTE PROCEDURE statement to a SELECT.

In some cases this automatic transformation to use a SELECT leads to problems. You can explicitly set FirebirdCallableStatement.setSelectableProcedure(false) to fix most of these issues, but this is not always an option. For example spring-data-jpa’s @Procedure will not work correctly with selectable procedures, but you can’t call setSelectableProcedure.

To disable this automatic usage of procedure type information, set connection property ignoreProcedureType=true. When necessary you can use FirebirdCallableStatement.setSelectableProcedure(true) to execute a procedure using SELECT.

Be aware though, when EXECUTE PROCEDURE is used with a selectable procedure, it is executed only up to the first SUSPEND女主直播给粉丝脱内衣, and the rest of the stored procedure is not executed.

女主直播给粉丝脱内衣For Firebird 2.0 and lower this property has no effect, as there the procedure type information is not available.

6.11 URL encoding in query part of JDBC URL

女主直播给粉丝脱内衣Added in Jaybird 3.0.9, backported from Jaybird 4.

女主直播给粉丝脱内衣Jaybird now supports UTF-8 URL encoded values (and keys) in the query part of the JDBC URL.

女主直播给粉丝脱内衣As a result of this change, the following previously unsupported characters can be used in a connection property value when escaped:

URL encoding can also be used to encode any unicode character in the query string. Jaybird will always use UTF-8 for decoding.

This change introduces the following backwards incompatibilities:

Invalid URL encoded values will now throw a SQLNonTransientConnectionException.

The reason for this changes is that the new setBind connection property requires semicolon-separated values, but Jaybird supports semicolon-separated key/value connection properties in the query part. To be able to support this new property in the connection string, we had to introduce URL encoding.

This change only applies to the JDBC URL part after the first ?. This change does not apply to connection properties set through java.util.Properties or on a javax.sql.DataSource.

6.12 Potentially breaking changes

女主直播给粉丝脱内衣Jaybird 3.0 contains a number of changes that might break existing applications.

See also Compatibility changes for details.

6.12.1 Specifying connection character set is now required

Jaybird 3.0.0 and 3.0.1 required you to specify the connection character set by either specifying encoding=<Firebird encoding> or charSet=<Java encoding>.

女主直播给粉丝脱内衣This requirement has been dropped again in 3.0.2.

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

6.12.2 ANTLR 4 runtime

The generated keys functionality now requires ANTLR 4.7. Make sure to replace antlr-runtime-3.4.jar with the antlr-runtime-4.7.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.

6.12.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 ()

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

6.12.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.

6.13 Other fixes and changes

6.14 Removal of deprecated classes and packages

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

7 Known Issues

8 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 .女主直播给粉丝脱内衣 It might have been a change we forgot to document, but it could just as well be an implementation bug.

8.1 Character set handling

8.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.

8.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, when using connection character set NONE, that columns with 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.

8.1.3 Connection rejected without an explicit character set

Jaybird version 3.0.0 and 3.0.1 would not connect if no connection character set had been specified. This requirement has been dropped again. See Connecting without explicit character set for more information on the behavior in Jaybird 3.0.2 and higher.

8.1.4 Connecting without explicit character set

If no connection character set has been specified (using connection property encoding or charSet or their aliases), then - by default - Jaybird 3.0.2 and higher will default to connection character set NONE. Be aware that NONE in Jaybird 3 does not behave the same as in Jaybird 2.2 and earlier, see Connection character set NONE for information.

Using NONE女主直播给粉丝脱内衣 can result in incorrect character set handling when the database is used from different locales.

You can explicitly set the connection character set using one of the following options:

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

  • Use connection property charSet (alias: 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.

To control how Jaybird handles connections without explicit character sets, you can use the following options:

  • You can configure a default Firebird character set - overriding the default of NONE - 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.

  • You can require an explicit character set to be specified with system property org.firebirdsql.jdbc.requireConnectionEncoding set to true. With this property specified, a connection character set must have been specified using connection properties or using the system property org.firebirdsql.jdbc.defaultConnectionEncoding.

    This is the behaviour that was the default in Jaybird 3.0.0 and 3.0.1.

    This property will cause Jaybird to reject the connection, if no character set has been set, 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.”.

8.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.

8.3 Exceptions

8.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.

8.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.

8.6 Stricter JDBC compliance

女主直播给粉丝脱内衣In Jaybird 3.0 a number of changes were made for stricter compliance to the JDBC specification.

8.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.0, but there are still some cases left to fix (which we might do in point releases).

8.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), Statement.executeUpdate(String, int) or Statement.executeLargeUpdate(String ,int) with value Statement.RETURN_GENERATED_KEYS,
    • Statement.execute(String, int[]), Statement.executeUpdate(String, int[]) or Statement.executeLargeUpdate(String, int[]),
    • Statement.execute(String, String[])m Statement.executeUpdate(String, String[]) or Statement.executeLargeUpdate(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.

8.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.

8.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.

8.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.

8.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.

8.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 it is 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")

8.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.

8.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 jna-4.4.0.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 (as an absolute or relative path to the directory/directories containing the library file(s)).

For Windows and Linux, you can add the org.firebirdsql.jdbc:fbclient dependency on your classpath to provide the native libraries for the native and local protocol. Be aware that this dependency does not support embedded.


女主直播给粉丝脱内衣In the future we will move the Type 2 support to a separate library and provide JNA-compatible jars that provide the embedded libraries of a specific Firebird version.

8.9 Incompatibilities due to URL encoding in JDBC URL query part

With the introduction in Jaybird 3.0.9 of URL encoding for the query part of the JDBC URL, the use of characters + and % in the query part of a JDBC URL now have different meaning and can lead to errors or unexpected results.

See URL encoding in query part of JDBC URL女主直播给粉丝脱内衣 for more information.

8.10 Removal of deprecated classes, packages and methods

8.10.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 4.

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 , or .

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).

8.10.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.

8.10.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)

8.10.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.

8.11 Miscellaneous

8.12 Breaking changes for Jaybird 3.1

女主直播给粉丝脱内衣The version previously announced as 3.1 will be released as Jaybird 4.

8.13 Breaking changes for Jaybird 4

女主直播给粉丝脱内衣With Jaybird 4 the following breaking changes will be introduced.

8.13.1 Dropping support for Firebird 2.0 and 2.1

Jaybird 4 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.

8.13.2 Dropping support for Java 7

Jaybird 4 will be the last version to support Java 7, Jaybird 5 will drop support for Java 7.

8.13.3 Removal of deprecated methods

女主直播给粉丝脱内衣The following methods will be removed in Jaybird 4:

  • Character set mapping (translation) will be removed entirely. Connection property useTranslation (and it’s alias mapping_path) will no longer be available.

    Similar effects can be achieved by a custom encoding implementation.

    As part of this change the following parts of the implementation will be removed (note that most are internal to Jaybird):

    • org.firebirdsql.encodings.CharacterTranslator will be removed entirely
    • DatatypeCoder#encodeString(String value, String javaEncoding, String mappingPath)
    • DatatypeCoder#encodeString(String value, Encoding encoding, String mappingPath)
    • DatatypeCoder#decodeString(byte[] value, String javaEncoding, String mappingPath)
    • DatatypeCoder#decodeString(byte[] value, Encoding encoding, String mappingPath)
    • Encoding#withTranslation(CharacterTranslator translator)
    • EncodingFactory#getEncoding(String encoding, String mappingPath)
    • EncodingFactory#getEncoding(Charset charset, String mappingPath)
    • FirebirdConnectionProperties#setUseTranslation(String translationPath) (and on data sources)
    • FirebirdConnectionProperties#getUseTranslation (and on data sources)
    • IEncodingFactory#getCharacterTranslator(String mappingPath)
  • 女主直播给粉丝脱内衣The following connection properties will be removed:

    • useTranslation: See previous item
    • octetsAsBytes: Since Jaybird 3 octets is always handled as BINARY
    • noResultSetTracking: Option does nothing since Jaybird 3
    • paranoia_mode: Option does nothing since Jaybird 2.2 (maybe earlier)
  • 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.

  • FBBlob#copyCharacterStream(Reader reader, long length, String encoding)

  • FBBlob#copyCharacterStream(Reader reader, String encoding)

8.13.4 Removal of deprecated constants

The following constants will be removed in Jaybird 4:

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