Subject Trace API dealing with special characters? (e.g. umlauts etc.)
Author Thomas Steinmaurer
Hello,

in a Firebird 2.5 database created with ISO8859_1 and also using
ISO8859_1 at connect time, I get the following in fsql:

SQL> select 'ä' from rdb$database;

CONSTANT
========
ä


But the raw output of a trace session gives me:

2010-11-19T11:02:11.6010 (4588:00000000011ABAE0) START_TRANSACTION
tourism.fdb (ATT_1437, TOURISM:NONE, ISO88591, TCPv4:127.0.0.1)
C:\Program Files\Firebird\Firebird_250_3051\bin\fsql.exe:5280
(TRA_24528, CONCURRENCY | WAIT | READ_WRITE)

2010-11-19T11:02:11.6020 (4588:00000000011ABAE0) EXECUTE_STATEMENT_START
tourism.fdb (ATT_1437, TOURISM:NONE, ISO88591, TCPv4:127.0.0.1)
C:\Program Files\Firebird\Firebird_250_3051\bin\fsql.exe:5280
(TRA_24528, CONCURRENCY | WAIT | READ_WRITE)

Statement 1906:
-------------------------------------------------------------------------------
select '„' from rdb$database
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PLAN (RDB$DATABASE NATURAL)


I don't see the 'ä' correctly. So, are there any problems dealing with
special (Non-Ansi?) characters in the raw trace data output?

Thanks!


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/