|
What's New in V3.7? |
|
|
|
|
What's New in V3.7? |
|
|
What's New in V3.7?
|
What's New in V3.7? |
|
|
|
|
What's New in V3.7? |
|
|
This section discusses the incremental changes in V3.7 compared to V3.6.
High-Level Overview
The following changes/enhancements have been made/added in V3.7:
| • | Experimental support for Firebird 4 Beta 2 |
| • | Improved Firebird client library handling |
| • | Extended trace configuration and trace data support |
| • | Bugfixes, improved stability, misc |
They are discussed in more detail in the following sections.
Experimental support for Firebird 4 Beta 2
This release adds experimental support for Firebird 4 Beta 2.
Pre-requisites
To use FB TraceManager with Firebird 4 Beta 2, you have to disable over-the-wire encryption on the Firebird side in firebird.conf with:
WireCrypt = Disabled
Supported Features
All areas in the product, except Database Monitoring - Monitoring (MON$) Tables, should work fine with Firebird 4 Beta 2.
Improved Firebird client library handling
The logic behind which Firebird client library is used for per-database Database Monitoring has been reworked. When registering a database with Register Database, if the client library entry is kept empty, upon connect, the Firebird client library defined for the server attachment in Register Server will be used then.
Extended trace configuration and trace data support
A few additional trace configuration parameters have been added in newer Firebird sub-releases. E.g.:
| • | log_warnings |
| • | log_initfini |
both are supported now in the Register Project dialog.
Additionally, http://tracker.firebirdsql.org/browse/CORE-6095 added additional trace data in context of RETAINed transactions. FB TraceManager now properly supports the change trace data layout across the entire product.
Bugfixes, improved stability, misc
FB TraceManager ships with Firebird embedded. We have updated to version 2.5.9. Additionally, a few minor bugs have been fixed as well.
See also