ADO.NET provider 8.0.0.0 for Firebird is ready (with Entity Framework Core 5.0 support)
More info at this link.
Category: Tools & Products releases
Announcements of new Firebird related products, or new releases.
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:
Database .NET and dbMigration .NET 2021 released
Database .NET 31.6 is an innovative, powerful and intuitive multiple database management tool, With it you can easily edit and manage your Firebird database files.
dbMigration .NET 13.2 is a simple, easy and intuitive multiple database migration and data synchronization tool, With it you can easily migrate schema and data to Firebird and vice versa.
Load testing of IBProvider v5.21.1 and Firebird v3.0.7
Hello All.
We have good news for everyone who uses IBProvider in critical and complex systems.
A «large», multithreaded, load testing of the latest release of IBProvider v5.21.1 and Firebird v3.0.7 (SS, Win, x64) has been carried out.
This is more than 7 million tests that were performed on a 10-core processor.
The main point of this testing was that the global cache of the SQL query parser was used (sql_cache__scope=db).
As usual, the built-in client for Firebird (dbclient_type=fb.direct) was used.
Testing completed with no visible problems.
See additional info at our web site: https://www.ibprovider.com/eng/news/n_201225.html
Best regards, IBProvider Team.
ADO.NET provider 7.10.1.0 for Firebird is ready
More info at this link.
IBProvider v5.21. SQL query parser cache implementation
In this release of IBProvider v5, we have implemented caching the results of our own SQL query parser.
The SQL query parser is needed to define the type of query and its parameter list as well as to divide the script into separate expressions.
The SQL query cache (SQL Cache) supplements the server query cache (Stmt Cache) implemented way back in the earlier versions of IBProvider v3.
Both SQL Cache and Stmt Cache use separate threads to service their own state.
The SQL query cache works for both user queries and service queries of updatable rowset.
Read more at IBProvider Site
Kind Regards, IBProvider Team.
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:
IBProvider v5.19. Advanced load testing
Hello Everyone,
All changes in the current IBProvider release are related to the reorganization of the source code. If you are using v5.18, you can skip this update.
In addition to standard checks, IBProvider v5.19 (vc16, x64) went through advanced load testing. Within 42.5 days, ~7 million tests, applicable in FB3, were run through the debug build of the provider and our connection pool (LCPI OLE DB Services).
Full news text – https://www.ibprovider.com/eng/news/n_200723.html
Kind Regards, IBProvider team.
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: