Firebird can be downloaded from the Firebird website, under Downloads, JDBC Driver.
Alternatively, you can go directly to GitHub and download Jaybird from the jaybird releases.
Jaybird is available on maven (since version 2.2.0), with a separate artifact for each supported Java version.
<dependency> <groupId>org.firebirdsql.jdbc</groupId> <artifactId>jaybird-jdk18</artifactId> <version>2.2.10</version> </dependency>
When deploying to a JavaEE environment, exclude the
javax.resource connector-api dependency as this will be provided by the application server.
Occasionally we release a Jaybird 3 snapshot for testing purposes to the Sonatype OSS snapshot repository.
<dependency> <groupId>org.firebirdsql.jdbc</groupId> <artifactId>jaybird-jdk18</artifactId> <version>3.0.0-SNAPSHOT</version> </dependency>
All Jaybird distribution zips contain a
jaybird-<version>-sources.zip with the sources used for that specific version. The full Jaybird sourcecode is also available from GitHub in the jaybird repository:
Each release is also tagged in the repository.
Jaybird JCA/JDBC driver is distributed under the GNU Lesser General Public License (LGPL). Text of the license can be obtained from http://www.gnu.org/copyleft/lesser.html.
Using Jaybird (by importing Jaybird's public interfaces in your Java code), and extending Jaybird by subclassing or implementation of an extension interface (but not abstract or concrete class) is considered by the authors of Jaybird to be dynamic linking. Hence our interpretation of the LGPL is that the use of the unmodified Jaybird source does not affect the license of your application code.
Even more, all extension interfaces to which an application might want to link are released under dual LGPL/modified BSD license. Latter is basically "AS IS" license that allows any kind of use of that source code. Jaybird should be viewed as an implementation of that interfaces and the LGPL section for dynamic linking is applicable in this case.
Current releases of Jaybird do not explicitly specify an LGPL version. This means that you can choose which version applies. Future versions of Jaybird may specify an explicit version, or be released under a different license.
Jaybird 2.2 supports Java 6, 7 and 8.
Jaybird 2.2.4 added basic support for Java 8 (JDBC 4.2), although not all JDBC 4.2 features are supported or fully implemented.
Jaybird 2.2.7 is the last version to support Java 5, support has been dropped with Jaybird 2.2.8.
Jaybird 2.2 is the last version to support Java 6, support will be dropped with Jaybird 3.0.
Jaybird 3.0 will support Java 7 and 8 (actual support subject to change before release).
Jaybird 2.2 supports all Firebird versions 1.0 and higher. Jaybird 2.2.4 added support for new features of Firebird 3 (eg
Jaybird 2.2 is the last version to support Firebird 1.0 and 1.5. Future versions of Jaybird are not guaranteed to work with these versions.
Jaybird 3.0 supports Firebird versions 2.0 and higher.
Jaybird 3.0 is the last version to support Firebird 2.0. Future versions of Jaybird are not guaranteed to work with version 2.0 and earlier.
Jaybird does not support Interbase, and as far as we know connecting to Interbase 6.0 and later will fail due to Firebird specific changes in the implementation.
Apart from this FAQ, you can get additional information from:
The Firebird-Java group and corresponding mailing list email@example.com
You can subscribe to the mailing list by sending an email to firstname.lastname@example.org
Firebird support and other Firebird mailing lists for questions not directly related to Jaybird and java.
There are several ways you can contribute to Jaybird or Firebird in general:
See also http://www.firebirdsql.org/en/consider-your-contribution/
The developers follow the email@example.com list. Join the list and post information about suspected bugs. List members may be able to help out to determine if it is an actual bug, provide a workaround and get you going again, whereas bug fixes might take awhile.
You can report bugs in the Firebird bug tracker, project "Java Client (Jaybird)"
When reporting bugs, please provide a minimal, but complete reproduction, including databases and sourcecode to reproduce the problem. Patches to fix bugs are also appreciated. Make sure the patch is against a recent trunk version of the code.
Default URL format:
This will connect to the database using the Type 4 JDBC driver using the Java implementation of the Firebird wire-protocol. This is best suited for client-server applications with dedicated database server. Port can be omitted (default value is
3050), host name must be present.
<database> part should be replaced with the database alias or the path to the database. In general it is advisable to use database aliases instead of the path of the database file as it hides implementation details like file locations and OS type.
On Linux the root
/ should be included in the path. A database located on
/opt/firebird/db.fdb should use (note the double slash after port!):
Deprecated, but still supported alternative URL format:
Jaybird can be used together with OpenOffice and Libre Office Base. To address some compatibility issues (and differences in interpretation of JDBC specifications) a separate subprotocol is used:
Type 2 driver, will connect to the database using client library (
fbclient.dll on Windows, and
libfbclient.so on Linux). Requires correct installation of the client library and the Jaybird native library.
Type 2 driver in local mode. Uses client library as in previous case, however will not use socket communication, but rather access database directly. Requires correct installation of the client library and the Jaybird native library.
Similar to the Firebird client library, however
fbembed.dll on Windows and
libfbembed.so on Linux are used. Requires correctly installed and configured Firebird embedded library and the Jaybird native library.
WARNING The information in this section is outdated
Jaybird follows the JDBC 4.1 specification with some features and methods not implemented. Some of the unimplemented items are required by the specification and some are optional.
TransactionManagerand JCA deployment support) as well as when used via
ObjectFactoryimplementation for use in environments with JNDI but no
DataSourceimplementations without pooling.
WARNING The information in this section is outdated
The following optional features are NOT supported:
The following optional features and the methods that support it are not implemented:
setRef(int i, Ref x)
setArray(int i, Array x)
getObject(int i, java.util.Map map)
getObject(String columnName, java.util.Map map)
Excluding the unsupported features, the following methods are not yet implemented:
registerOutParameter(int parameterIndex, int sqlType)
registerOutParameter(int parameterIndex, int sqlType, int scale)
getBytes(long pos, int length)
position(byte pattern, long start)
position(Blob pattern, long start)
The following methods are implemented, but do not work as expected:
setObject(index,object,type)This method is implemented but behaves as
setObject(index,object,type,scale)This method is implemented but behaves as
isReadOnly(i)always returns false
isWritable(i)always returns true
isDefinitivelyWritable(i)always returns true
Jaybird itself no longer provides connection pooling. Earlier versions had a
DataSource implementation with connection pooling, but this implementation had severe bugs. This implementation (and all other classes in
org.firebirdsql.pool) was deprecated in 2.2 and dropped in 3.0.
Jaybird provides a basic
DataSource implementation and a
ConnectionPoolDataSource implementation. Contrary to its name the latter does not provide a connection pool, but is intended to be used by a connection pool (as implemented in an application server) to create connections for the connection pool.
If your application is built on an application server, we suggest you use the connection pooling provided by the application server. Either through the resource-adapter of the JCA implementation of Jaybird, or using the
If you develop standalone applications, or you use an application server without connection pooling, we suggest you use third-party libraries like: