You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When tracing, parameters are logged, very nice.
Currently we use CHAR(16) CHARACTER SET OCTETS to store ID-values.
Tracing log them like this.
param0 = varchar(16), " ßFÃ/¿J¹Z3¡õñ]["
I can manually convert this to hex by Win1252 decoding, (DF46C32FBF4AB95A33A1F5F15D5B) but it would be much easier to have a Hex presentation when parameter is of Octets charset.
Please implement encoding with hex-values when parameter is of type CHAR(16) CHARACTER SET OCTETS.
The text was updated successfully, but these errors were encountered:
pbhofstede2
changed the title
Firebird 5.0 Trace, parameter logging
[improvement] Firebird 5.0 Trace, parameter logging
Dec 20, 2024
From firebird support list: https://groups.google.com/u/2/g/firebird-support/c/kPgAW-BtpQo
When tracing, parameters are logged, very nice.
Currently we use CHAR(16) CHARACTER SET OCTETS to store ID-values.
Tracing log them like this.
param0 = varchar(16), " ßFÃ/¿J¹Z3¡õñ]["
I can manually convert this to hex by Win1252 decoding, (DF46C32FBF4AB95A33A1F5F15D5B) but it would be much easier to have a Hex presentation when parameter is of Octets charset.
Please implement encoding with hex-values when parameter is of type CHAR(16) CHARACTER SET OCTETS.
The text was updated successfully, but these errors were encountered: