>btw, in Firebird 3, the RDB$EXCEPTIONS.RDB$MESSAGE is still NONE. Would it make sense to encode the message according to the given connection character set?
>> Now, I tried the following in the procedure to work around the above: >> >> exception test _utf8 'unicode string here'; Any idea why this won't work either? Or at least, not in my test? With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird!
