Subject | Re: [firebird-support] Bug with character sets |
---|---|
Author | Brad Pepers |
Post date | 2009-05-20T00:55:55Z |
On 19-May-09, at 8:31 AM, Dimitry Sibiryakov wrote:
know is how many characters I got and right now it looks like the
client has to do this and select information on the character sets and
do work that I would really think the server should do. But in the
end I guess as long as I can understand what is going on and ideally
if it was documented somewhere (since it is certainly not something I
think client side developers would expect!) then good enough!
--
Brad
>> I totally fail to see why the client library knows nothing aboutThis is what is unfortunate. On the client side what I really want to
>> this? Isn't
>> it the client library that is the "glue" between the network
>> protocol and
>> the client application? Yes, it is, so it should present properly
>> encoded
>> character strings to the client application.
>
> It is "glue", right, but network protocol does not include actual
> data length in characters, only in bytes.
know is how many characters I got and right now it looks like the
client has to do this and select information on the character sets and
do work that I would really think the server should do. But in the
end I guess as long as I can understand what is going on and ideally
if it was documented somewhere (since it is certainly not something I
think client side developers would expect!) then good enough!
--
Brad