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
Hello,
there is a table with all Material (stock), each one has a number. Now, in a
second table there is listed the material that is a part of the Material.
For example:
Material ABC
Material BCD
Material XXX
Material OMV
Material KOM
Material OMV can be a Part of XXX and XXX
there is a table with all Material (stock), each one has a number. Now, in a
second table there is listed the material that is a part of the Material.
For example:
Material ABC
Material BCD
Material XXX
Material OMV
Material KOM
Material OMV can be a Part of XXX and XXX a Part of
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
There is at least a good alternative, Frank Ingermann showed how to do
something very similar when calculating the amount of ingredients required when
baking a marble cake at a Firebird conference a few years ago. He used a
recursive CTE. Whether a recursive CTE is simpler than a recursive
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
