Reverted Firebird 3 workaround for updatable result sets as bug has been fixed in Firebird (JDBC-330)

Fixed: Processing and closing the ResultSet from callable statement and then using the getters throws NullPointerException (JDBC-350)

Using both the getters and the result set for the same callable statement is incorrect; the ability to do this might be removed in a future version of Jaybird. A ResultSet should be used for selectable procedures, while the getters should be used with executable procedures.

Fixed: FBManagedConnectionFactory.tryCompleteInLimboTransaction doesn't work with recent Firebird 3 builds (JDBC-353)

doesn't work with recent Firebird 3 builds (JDBC-353) Fixed: Jaybird can throw a NullPointerException when a fatal connection error has occurred (JDBC-359)

when a fatal connection error has occurred (JDBC-359) Fixed: Calling close on a JCA connection triggers exception Connection enlisted in distributed transaction (JDBC-362)

Fixed: Potential memory-leak when using a lot of different connection strings and/or properties (JDBC-364)

Fixed: FBRowUpdater.buildInsertStatement doesn't quote column names (JDBC-370)

doesn't quote column names (JDBC-370) Fixed: EncodingFactory doesn't handle UnsupportedCharsetException (JDBC-371)

doesn't handle (JDBC-371) Fixed: Current method of quoting in FBRowUpdater incorrect for dialect 1 (JDBC-372)

<groupId>org.firebirdsql.jdbc</groupId>

<artifactId>jaybird-jdkXX</artifactId>

<version>2.2.6</version>

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.6 This release contains the following fixes:The release is also available on maven(*):* The artifactId depends on your target Java version: jaybird-jdk15, jaybird-jdk16, jaybird-jdk17 or jaybird-jdk18.