The Firebird JDBC team is happy to announce the release of Jaybird 2.2.11.
The following has been changed or fixed in Jaybird 2.2.11:
- Fixed: Dialect 1,
NUMERIC(15,2)
and DatabaseMetadata.getColumn
returns 0
for DECIMAL_DIGITS
(JDBC-426)
- Updated error messages from latest Firebird 3 to add missing messages (JDBC-428)
- Fixed:
ResultSet.getObject()
returns byte[]
instead of String
for BLOB SUB_TYPE 1
when using octetsAsBytes
(JDBC-431)
- Improvement: Support Firebird 3 48-bit transaction ids. (JDBC-432)
Note that FBMaintenanceManager.commit/rollbackTransaction(long)
with longer than 32 bit transaction ids requires Firebird 3.0.1 because of CORE-5224.
- Fixed: Batch insert with
setBinaryStream
inserts an empty BLOB SUB_TYPE TEXT
(JDBC-433)
This is the same issue as JDBC-312 that was fixed in Jaybird 2.2.4 for BLOB SUB_TYPE BINARY
.
- Changed locking to coarser blocks with - as far as possible - a single lock object per connection for all connection-derived objects (JDBC-435)
This should prevent deadlocks on concurrent access as in some cases locks were obtained in different orders (eg (statement, connection), and (connection, statement)). The downside is reduced concurrency, but as using a connection from multiple threads concurrently is discouraged anyway, that is an acceptable price to pay.
See the
JDBC driver download page for download links. The release is also available on maven, with a separate artifact for each supported Java version:
Groupid: org.firebirdsql.jdbc
, artifactid: jaybird-jdkXX
(where XX
is 16
, 17
or 18
).
Version: 2.2.11
For example:
org.firebirdsql.jdbc
jaybird-jdk18
2.2.11