IBProvider v5.5
Hello All,
This IBProvider update provides support for Firebird v3.0.4 authentication methods: Srp224, Srp256, Srp384 and Srp512.
https://www.ibprovider.com/eng/news/n_190531.html
With Best Regards, IBProvider Team.
Hello All,
This IBProvider update provides support for Firebird v3.0.4 authentication methods: Srp224, Srp256, Srp384 and Srp512.
https://www.ibprovider.com/eng/news/n_190531.html
With Best Regards, IBProvider Team.
The new article from IBSurgeon:
A quick estimation of disk speed with verified backup (gbak): https://ib-aid.com/en/articles/disk-speed-measurement-with-backup/
Is your disk subsystem slow or fast? If you are doing regular backups, now you can easily estimate it.
We are happy to announce the release of Jaybird 3.0.6.
This release is largely a bugfix release, but contains additional support for Firebird 4.
Jaybird 3.0.6 contains the following fixes and changes:
Jaybird 3.0 supports Firebird 2.0 and higher, on Java 7, 8 and 9 and higher. Basic Java 9 and higher compatibility is provided through the Java 8 version of the driver.
See also:
Hello All,
We are pleased to annonce update of our components for work with Firebird and InterBase DBMS.
https://www.ibprovider.com/eng/news/n_190520.html
The first beta for Jaybird 4 is available for testing.
We’d really appreciate it if you take the time to test this version of Jaybird with your applications. Bug reports about undocumented changes in behavior are appreciated. Feedback can be sent to the Firebird-java mailing list or reported on the issue tracker http://tracker.firebirdsql.org/browse/JDBC.
Jaybird 4 is – compared to Jaybird 3 – an incremental release that builds on the foundations of Jaybird 3. The focus of this release has been on further improving JDBC support and adding support for the new data types and features of Firebird 4.
The main new features are:
Jaybird 4.0.0-beta-1 is for testing purposes only, and not intended for production use.
See also:
As you probably know, Firebird Conference 2019 will include the practical workshops, and the article “How to track deadlocks in Firebird” is one of the sneaks peeks of the workshop “All About Transactions”, which will be done by Vlad Khorsun, Firebird core developer, and Alexey Kovyazin from IBSurgeon.
To help developers investigate the update conflicts (deadlocks), Firebird puts into error messages the reference to the concurrent transaction – i.e., the transaction where the concurrent update is not yet committed. Together with Trace API, it gives us the ability to track both conflicting operations.
Let’s consider the practical steps on how to do it: read the article “How to track deadlocks in Firebird“.