The following has been changed or fixed in Jaybird 2.2.12:
0for computed columns in
Firebird 2.5 and earlier (JDBC-450)
If Firebird reports precision
0, Jaybird will now estimate it to be
precision 19 (not 18). This will be improved in Jaybird 3 to report 18.
executeBatch()on a statement prepared with one of
the generated keys options will now throw an
instead of an unclear
Support for batch execution on a prepared statement with
support will be added in Jaybird 3.0 (see JDBC-452).
ResultSet.absolute(0)should not throw an exception, but position
the result set before the first row (JDBC-453)
ResultSetMetaData.getPrecisionof a numeric column when no
transaction is active throws an SQLException (JDBC-464)
As part of this fix, the handling of queries executed by
has been changed. Most metadata queries are now kept prepared for reuse.
Known issues in Jaybird 2.2.12
- Connecting to Firebird 2.5 and earlier with a Firebird 3
be slow with native connections, see CORE-4658.
Workaround is to connect to the IPv4 address instead of the hostname, or to
use a Firebird 2.5 or earlier
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.12</version>
* The artifactId depends on your target Java version: