Martijn Tonies wrote:

>
> This has nothing to do with fetching data. Having to query the
> system tables in order to properly process the data as provided
> by the client side API, does that sound "OK" to you?

I have some doubts about a "proper processing". For a CHAR value, does
it mean returning (to the caller application) the string with trailing
spaces of without? I'd expect a clever intermediate layer to trim them.
But I suspect this makes this issue independent from the multi-byte
character sets then, because your N (length in characters) is always 10
for CHAR(10) regardless of the string stored inside (e.g. 'a') and its
charset. I mean that XSQLVAR may contain either N = 40 or N = 10, and it
doesn't change anything for you, as you have to decode the partial
string anyway. Do I miss anything?


Dmitry