Hello Thomas,
13.09.2021 11:43, Thomas Steinmaurer wrote:
Hello,
congratulations to the Firebird 4 release!
How do I best find out what has been changed in the area of MON$ tables and
especially Firebird Trace API.
MON$ tables get a bit of mentioning in the Release Notes, e.g. what fields have been added etc. resp. I could extract the DDL for
all MON$ tables and textually compare it the output for Firebird 3 MON$ tables.
What might have been added in the Firebird 4 Trace API interesting for our FB TraceManager product? Any new trace event types
(aka EXECUTE_STATEMENT_FINISH etc ...). Would thi be covered in the Release Notes?
Sure. There was not mush changes in Trace visible to the end users:
- new system privilege to trace attachments of other users
- session management statements now traced
- trace record for COMMIT/ROLLBACK RETAINING was extended to show old/new
transaction IDs
Some other features that developed before release was backported into v3 so it
is not new in v4.
And, of course, some bugs was fixed.
Many thanks. This helps.
It seems MON$ tables are now using the timestamp with time zone data type.
Yes, look also for changes of CURRENT_TIME[STAMP]
To do a simple "SELECT * ..." query on e.g. MON$DATABASE, I guess either the client library needs to support the new data type or I
need to explicitly CAST to TIMESTAMP each affected column, right?
Another possibility is to set coercion rules for new data type for your
connection, see
https://firebirdsql.org/file/documentation/release_notes/html/en/4_0/rlsnotes40.html#rnfb4-msql-set-bind-native-to-legacy-coercion-rules
and
https://firebirdsql.org/file/documentation/release_notes/html/en/4_0/rlsnotes40.html#rnfb40-compat
Regards,
Vlad
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
