New snapshot of Jaybird 2.2.4 with support for: Firebird 3.0 Boolean and Java 8

Mark Rottevee announced new snapshot of Jaybird driver :
I have just uploaded a new snapshot version for Jaybird 2.2.4 to
sourceforge and the sonatype snapshots repository for Maven.

Most notable changes are support for the Firebird 3.0 alpha 1 BOOLEAN
type and support for Java 8. For other changes see
http://tracker.firebirdsql.org/browse/JDBC/fixforversion/10531

This snapshot is intended only for testing purposes and has not been
tested with the native or embedded subprotocols.

Download area (Java 5, 6, 7 and 8):
https://sourceforge.net/projects/firebird/files/firebird-jca-jdbc-driver/2.2.4-SNAPSHOT/

Maven snapshot repository:
https://oss.sonatype.org/content/repositories/snapshots/

groupId: org.firebirdsql.jdbc
artifactId: jaybird-jdk1x (where x = 5, 6, 7 or 8)
version: 2.2.4-SNAPSHOT

If you have any problems, let me know in the Firebird-Java list. Bugs
can be reported in the tracker http://tracker.firebirdsql.org/browse/JDBC

1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading...

Jaybird 2.2.4 snapshot with basic Java 8 / JDBC 4.2 support

Mark Rotteveel wrote about new Firebird JDBC driver snapshot:

I just created a snapshot version of Jaybird 2.2.4 with basic Java 8 /
JDBC 4.2 support. It is available for download from:
https://sourceforge.net/projects/firebird/files/firebird-jca-jdbc-driver/2.2.4-snapshot-jdk18/

This snapshot provides basic support for Java 8 by overriding the new
default interface methods added with a slightly more sane default. Most
of the changes in Java 8 are about supporting large update counts (>
Integer.MAX_VALUE) and the new SQLType interface.

For the large update counts Jaybird simply delegates to the methods
returning int values.

The Statement.setLargeMaxRows(long) method will set the max to 0 (no
maximum) if a value larger than Integer.MAX_VALUE is supplied.

The SQLType methods will delegate to the methods accepting an int
sqlType parameter with the value obtained from getVendorTypeNumber()
without further validation or checking. The exception to this are the
ResultSet.updateObject(…) methods which don’t have an equivalent
accepting an integer type parameter. In that case it is delegated to the
equivalent method without type support.

The snapshot is also available on maven in the Sonatype OSS snapshot
repository: https://oss.sonatype.org/content/repositories/snapshots

1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading...

Jaybird 2.2.3 (Firebird JDBC) released

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.3.

See http://www.firebirdsql.org/en/jdbc-driver/ for the downloadlinks.

The release is also available on maven:
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.3</version>

The artifactId depends on your target Java version: jaybird-jdk15, jaybird-jdk16 or jaybird-jdk17.

The following has been changed or fixed in Jaybird 2.2.3:

  • Fixed incorrect synchronization in native and embedded protocol (JNI) implementation for iscBlobInfo and iscSeekBlob (JDBC-300)
  • Fixed holdable ResultSet is closed on auto-commit (JDBC-304, JDBC-305)
  • Fixed table names missing or padded with spaces in Database view of IntelliJ IDEA (JDBC-308, IDEA-100786)
  • Fixed incorrect JDBC minor version reported under Java 7; this resulted in an incorrect column name (for Java 7) in the metadata of DatabaseMetaData.getColumns(…) (JDBC-309)
  • Added IOException to cause of GDSException with error 335544721; “Unable to complete network request to host “”” for further investigation (JDBC-306)

More details are available in the Jaybird 2.2.3 releasenotes.

1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading...

Jaybird 2.2.2 Released

The Firebird JDBC team is happy to announce the release of Jaybird 2.2.2.

See http://www.firebirdsql.org/en/jdbc-driver/ for the downloadlinks.

The release is also available on maven:
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>2.2.2</version>

The artifactId depends on your target Java version: jaybird-jdk15,
jaybird-jdk16 or jaybird-jdk17

The following has been changed or fixed in Jaybird 2.2.2:

  • Fixed: FBMaintenanceManager.listLimboTransactions() reports incorrect transaction id when the result contains multi-site transactions in limbo (JDBC-266)
  • Fixed: Calling PreparedStatement.setClob(int, Clob) with a non-Firebird Clob (eg like Hibernate does) or calling PreparedStatement.setClob(int, Reader) throws FBSQLException: “You can’t start before the beginning of the blob” (JDBC-281)
  • Fixed: Connection property types not properly processed from isc_dpb_types.properties (JDBC-284)
  • Fixed: JNI implementation of parameter buffer writes incorrect integers (JDBC-285, JDBC-286)
  • Changed: Throw SQLException when calling execute, executeQuery, executeUpdate and addBatch methods accepting a query string on a PreparedStatement or CallableStatement as required by JDBC 4.0 (JDBC-288)
    NOTE: Be aware that this change can break existing code if you depended on the old, non-standard behavior! With addBatch(String) the old behavior lead to a memory leak and unexpected results.
  • Fixed: LIKE escape character JDBC escape ({escape ‘<char>’}) doesn’t work (JDBC-290)
  • Added: Support for a connect timeout using connection property connectTimeout. This property can be specified in the JDBC URL or Properties object or on the DataSource. If the connectTimeout property is not specified, the general DriverManager property loginTimeout is used. The value is the timeout in seconds. (JDBC-295)
    For the Java wire protocol the connect timeout will detect unreachable hosts. In the JNI implementation (native protocol) the connect timeout works as the DPB item isc_dpb_connect_timeout which only works after connecting to the server for the op_accept phase of the protocol. This means that – for the native protocol – the connect timeout will not detect unreachable hosts within the timeout. As that might be unexpected, an SQLWarning is added to the connection if the property is specified with the native protocol.
  • As part of the connect timeout change, hostname handling (if the hostname is an IP-address) in the Java wire protocol was changed. This should not have an impact in recent Java versions, but on older Java versions (Java 5 up to update 5) this might result in a delay in connecting using an IP-address, if that address can’t be reverse-resolved to a hostname. Workaround is to add an entry for that IP-address to the /etc/hosts or %WINDIR%\System32\Drivers\etc\hosts file.
1 Star2 Stars3 Stars4 Stars5 Stars (3 votes, average: 5.00 out of 5)
Loading...
1 2 3 4