Announcements of new Firebird related products, or new releases.
Hello everyone!
We are glad to announce the new update of IBProvider — v3.50.
http://www.ibprovider.com/eng/news/n_180508.html
Main feature of this release — elimination of very old restrictions of our OLE DB provider.
Common list of changes:
Database .NET 24.8 is an innovative, powerful and intuitive multiple database management tool, With it you can easily edit and manage your Firebird database files.
dbMigration .NET 8.4 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.
The Firebird JDBC team is happy to announce the release of Jaybird 3.0.4.
This release of Jaybird introduces two new features: wire protocol encryption and database encryption callback support.
Jaybird 3.0.4 contains the following fixes and changes:
– New feature: Back-ported wire encryption support from Jaybird 4 (JDBC-415)
– Fixed: Native/embedded (JNA) connections truncate varchars to length 255 on read (JDBC-518)
– New feature: Database encryption callback support in pure Java protocol (JDBC-527)
See the Jaybird 3.0.4 release notes for more information. Jaybird 3.0.4 can be downloaded from the JDBC Driver page.
The release is also available on maven:
groupId: org.firebirdsql.jdbc
artifactid: jaybird-jdkXX*
version: 3.0.4
* The artifactId depends on your target Java version: jaybird-jdk18, or jaybird-jdk17
After a long hiatus, I’ve finally found time to update firebird_fdw, which is now available as version 0.3.0.
This update, together with an update of the underlying Firebird API wrapper libfq to version 0.2.0, is a general cleanup/bugfix release, with improvements including:
- support for PostgreSQL 9.6 and 10
- support for
IMPORT FOREIGN SCHEMA(PostgreSQL 9.5 and later)- automatic reconnection to Firebird
- improved error message handling and display
- improved memory handling and prevention of various unhandled situations which caused the PostgreSQL server to crash
Additionally, CentOS rpm packages are now available via the Fedora Copr build system.
This release has been developed and tested with Firebird 2.5. It will work with Firebird 3.0, but does not yet take advantage of any new features; future releases will hopefully address this.
Yii2-Firebird 0.10.0 is released with the following ChangeLog:
Yii2-Firebird updated in git master with Yii2 2.0.15 compatibility : dev-master on packagist.org
You can use the following docker images based on Debian Jessie
Firebird high-level native client for Node.js / TypeScript updated to v0.0.1-beta.1 with a few changes:
-Add fetchSize option to FetchOptions and group options in a single parameter in Attachment::execute* methods #4
-Performance improvement in fetch
-Add properties to TransactionOptions – #5.
-Finish #1 – Support for BLOB datatype: Adding support for read/write BLOB with the Blob and BlobStream classes.
XPO (an object-relational mapping library – ORM) supports more than a dozen database engines (including SQL Server, Oracle and various Open Source products) and recently got updated to support Firebird 3 too.
Firebird
In addition to SQL Server, MySql, PostgreSQL and SQLite, XPO for .NET Core / .NET Standard 2.0 supports ADO.NET provider 5.11+ for Firebird starting with v17.2.5. As we noted in our introductory post, the lack of support for other providers is not an XPO limitation – as soon as RDBMS vendors begin supporting .NET Standard 2.0, we will test XPO with these RDBMS providers and add them to our supported list.
Support for Firebird 3.0 server and the client ADO.NET data provider (FirebirdSql.Data.FirebirdClient 5.8.0) will be available in v18.1. We will also support the Substring criteria function that was missing before.
Hello everyone!
We have two news for you:
1. IBProvider v3.49 was released. We ensured a stricter compliance with the OLE DB specification and revised the existing code.
2. Microsoft changed its decision to go back to ODBC and promises to release an updated OLE DB provider for MS SQL. Let’s hope that they not only will rewrite the provider but also update the OLE DB specification.
