Dimitry Sibiryakov wrote:

>>If that were true, then this:
>>
>>//with default charset utf8
>>create table X (A char(2), B char(2))
>>insert into X (A, B) values ('A ', 'B ')
>>select A || B from X
>>
>>would produce this string:
>>'A<7_spaces>B<7_spaces>'
>>
>>This is clearly not the case. It produces the correct result:
>>'A<singlespace>B<singlespace>'
>
> Nice trick, yes? And you know why it works this way? Because of INTL
> module, who convert strings between UTF and UCS. During this process it
> applies SUBSTRING(data FROM 1 TO N) to intermediate results.

Yes, very nice, and not something I would like fbclient to do because of
bloat. But I'd like the N, that the server apparently knows and even has
already at hand, would be passed to the client application (the part
that interprets the XSQLVAR struct and itsbuffer.

But I can see that it may just as well be solved with that
isc---somthing call that was mentioned in a different subthread. I'd
just like the XSQLVAR docs to be very clear about all this that has been
discussed in this thread.

Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64