Jaybird 4.0.3 and 3.0.11 released

Jaybird 4.0.3 and 3.0.11 have been released.

The following has been changed or fixed since Jaybird 4.0.2 and 3.0.10:

  • Changed: Closing a statement will now be sent to the server immediately (JDBC-638)

Jaybird 4.0.3

Jaybird 4 supports Firebird 2.5 and higher, on Java 7, 8, 11 and 15 (support for Java 15 using the Java 11 version of the driver); Java 16 has not been fully tested yet.

See also:

Jaybird 3.0.11

Although Jaybird 3 is still maintained, we recommend upgrading to Jaybird 4.

Jaybird 3 supports Firebird 2.0 and higher, on Java 7, 8, 11 and 15; Java 16 has not been fully tested yet. Basic Java 9 and higher compatibility is provided through the Java 8 version of the driver.

See also:

Jaybird 4.0.2 and 3.0.10 released

Jaybird 4.0.2 and 3.0.10 have been released.

Jaybird 4.0.2

The following has been changed or fixed since Jaybird 4.0.1:

  • Fixed: First letter of JDBC escape was case-sensitive (JDBC-632)
  • Fixed: Some usernames cannot authenticate using SRP (JDBC-635)
  • Fixed: ServiceConfigurationError while loading plugins could prevent Jaybird from loading (JDBC-636)

Jaybird 4 supports Firebird 2.5 and higher, on Java 7, 8, 11 and 15 (support for Java 15 using the Java 11 version of the driver).

See also:

Jaybird 3.0.10

Although Jaybird 3 is still maintained, we recommend upgrading to Jaybird 4.

The following has been changed or fixed since Jaybird 3.0.10:

  • Added: A static utility method FBDriver.normalizeProperties which, given a JDBC url and a Properties object, returns a Map<String, String> containing the merged properties normalized to the common property name. (JDBC-627)
  • Fixed: Use of isc_dpb_no_db_triggers no longer logs a warning (JDBC-628)
  • Fixed: First letter of JDBC escape was case-sensitive (JDBC-632)
  • Fixed: Some usernames cannot authenticate using SRP (JDBC-635)
  • Fixed: ServiceConfigurationError while loading plugins could prevent Jaybird from loading (JDBC-636)

Jaybird 3 supports Firebird 2.0 and higher, on Java 7, 8, 11 and 15. Basic Java 9 and higher compatibility is provided through the Java 8 version of the driver.

See also:

Jaybird 4.0.1 released

Jaybird 4.0.1 has been released. Jaybird 4.0.1 is the first maintenance release of Jaybird 4, and introduces support for INT128 (a new type in Firebird 4), improves support for the Firebird 4 WITH TIME ZONE types by adding support for java.time.ZonedDateTime and making some of the derivation rules more consistent with Firebird. It also provides some bug fixes and other changes.

The following has been changed or fixed since Jaybird 4.0.0

  • Fixed: Changes to the transaction configuration (transaction parameter buffer configuration) of one connection are no longer propagated to other connections with the same connection properties (JDBC-386)
  • Fixed: Search index of Javadoc in Java 11 version used incorrect links (JDBC-619)
  • Fixed: The cleanup of native resources didn’t dispose the native library held by JNA, as a change in implementation no longer allowed directly access to the JNA NativeLibrary (JDBC-620)
  • Fixed: When updating a row through an updatable result set, selected but not updated blob fields were set to NULL (JDBC-623)
  • Added: Support for type INT128 (reported as JDBC type NUMERIC) (JDBC-624)
    See also Firebird 4 INT128 support.
  • Added: A static utility method FBDriver.normalizeProperties which, given a JDBC url and a Properties object, returns a Map<String, String> containing the merged properties normalized to common property name. (JDBC-627)
  • Fixed: Use of isc_dpb_no_db_triggers no longer logs a warning (JDBC-628)
  • Incompatible change: While making changes to time zone support, the API of org.firebirdsql.gds.ng.tz.TimeZoneDatatypeCoder was made almost entirely private. This should not affect normal user code.
    Although we try to avoid these types of incompatible changes in point releases, we explicitly allow them for the org.firebirdsql.gds.ng package and sub-packages.
  • Changed: conversions from TIME WITH TIME ZONE now use 2020-01-01 as base date for named zones (JDBC-629)
  • New feature: Added support for java.time.ZonedDateTime for the WITH TIME ZONE types (JDBC-630)
  • Fixed: Connection.setNetworkTimeout incorrectly used the provided Executor to set the timeout (JDBC-631)

Jaybird 4 supports Firebird 2.5 and higher, on Java 7, 8, 11 and 14 (using the Java 11 version of the driver).

See also:

IBSurgeon Firstaid 7.0 is released

IBSurgeon releases version 7 of FirstAID: recovery for Firebird and InterBase databases. 
This version includes the following new features and bugfixes:

  1. Support of InterBase is extended till the version of 2020
  2. Firebird 4 support was aligned with changes in ODS of Firebird 4.0 Beta 2 version, almost ready for the release
  3. Addressable space for 64-bit machines was increased to 3Gb, which allows to open and recover bigger databases
  4. Several bugfixes for BOOLEAN data type recovery and BLOBs processing

Download FirstAID now: https://ib-aid.com/en/ibsurgeon-firstaid/ 

Clients with available FirstAID activations (from version 3.0+) can download and use version 7.0 with existing licenses.

Those clients who have exhausted all activations, or users of FirstAID before 3.0, can upgrade here https://ib-aid.com/en/upgrades-ibsurgeon/

Jaybird 3.0.9 released

Jaybird 3.0.9 has been released. This release contains the following changes:

  • Fixed: changes to the transaction configuration (transaction parameter buffer configuration) of one connection are no longer propagated to other connections with the same connection properties (JDBC-386)
  • New feature: Firebird 4 data type bind configuration support (JDBC-603)
  • New feature: Jaybird now supports UTF-8 URL encoding for connection properties in the JDBC url. (JDBC-604)
  • Fixed: When updating a row through an updatable result set, selected but not updated blob fields were set to NULL (JDBC-623)

Jaybird 3.0 supports Firebird 2.0 and higher, on Java 7, 8, 11 and 14. Basic Java 9 and higher compatibility is provided through the Java 8 version of the driver.

See also:

Real world experience with FbNetExternalEngine performance and code structure

I’m now going through piece of SQL code that contains a lot of stored procedures from over the years and lately also functions (in last year the migration to Firebird 3 really began) and looking into the code to identify functions and procedures to start the rewriting with using FbNetExternalEngine. I’m at the beginning, but I have some interesting piece I’d like to show.

Read more.

1 2 3 55