29.01.2015 19:15, Martijn Tonies wrote:
2) Create SP with EXCEPTION ERROR 'some Cyrillic string';
Done. In the source, I see the following:
begin
exception test _utf8
X'31D0A2D095D0A1D0A220D09DD09020D091D0AAD09BD093D090D0A0D0A1D09AD098';
end
You don't need the _utf8 prefix with HEX
27.01.2015 14:48, Martijn Tonies wrote:
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?
Do you mean changing RDB$EXCEPTIONS.RDB$MESSAGE to UTF8? It was
discussed but ended nowhere.
Hello Dmitry,
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?
Do you mean changing RDB$EXCEPTIONS.RDB$MESSAGE to UTF8? It was
discussed but ended nowhere.
No, I meant a runtime
Hello Dmitry,
I'm still puzzled.
29.01.2015 19:15, Martijn Tonies wrote:
2) Create SP with EXCEPTION ERROR 'some Cyrillic string';
Done. In the source, I see the following:
begin
exception test _utf8
X'31D0A2D095D0A1D0A220D09DD09020D091D0AAD09BD093D090D0A0D0A1D09AD098';
end
You
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
btw, in Firebird 3, the RDB$EXCEPTIONS.RDB$MESSAGE is still NONE.
Oh bugger.
Now, I tried the following in the procedure to work around the above:
exception test _utf8 'unicode string here';
When I look at RDB$PROCEDURES.RDB$PROCEDURE_SOURCE I can see
the text is inserted as a hex
Oh bugger.
Now, I tried the following in the procedure to work around the above:
exception test _utf8 'unicode string here';
When I look at RDB$PROCEDURES.RDB$PROCEDURE_SOURCE I can see
the text is inserted as a hex string.
But this doesn't seem to work either?
Does this work at all
21.01.2015 20:11, Martijn Tonies wrote:
Oh bugger.
Now, I tried the following in the procedure to work around the above:
exception test _utf8 'unicode string here';
When I look at RDB$PROCEDURES.RDB$PROCEDURE_SOURCE I can see
the text is inserted as a hex string.
But this doesn't seem
21.01.2015 19:45, 'Martijn Tonies wrote:
I have an EXCEPTION object with a Unicode text in it, a stored procedure
raises this exception.
The client application can view the Unicode text just fine when it
retrieves the Exception meta data, but when the exception is raised,
Firebird doesn’t
I have an EXCEPTION object with a Unicode text in it, a stored procedure
raises this exception.
The client application can view the Unicode text just fine when it
retrieves the Exception meta data, but when the exception is raised,
Firebird doesn’t seem to translate the text.
Any idea how to
10 matches
Mail list logo
