Jaybird 2.2.11
The following has been changed or fixed in Jaybird 2.2.11:
- Fixed: Dialect 1,
NUMERIC(15,2)
andDatabaseMetadata.getColumn
returns
0
forDECIMAL_DIGITS
(JDBC-426) - Updated error messages from latest Firebird 3 to add missing messages
(JDBC-428) - Fixed:
ResultSet.getObject()
returnsbyte[]
instead ofString
for
BLOB SUB_TYPE 1
when usingoctetsAsBytes
(JDBC-431) - Improvement: Support Firebird 3 48-bit transaction ids. (JDBC-432)
Note thatFBMaintenanceManager.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 emptyBLOB 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.
Known issues in Jaybird 2.2.11
- Connecting to Firebird 2.5 and earlier with a Firebird 3
fbclient.dll
may
be slow with native connections, see CORE-4658.
Workaround is to connect to the IPv4 address instead of the hostname.
See the full release notes for more information.
The release is also available on maven(*):
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.11</version>
* The artifactId depends on your target Java version: jaybird-jdk18
, jaybird-jdk17
, or jaybird-jdk16
.