>> I totally fail to see why the client library knows nothing about 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.

Then what does it transfer? The server know how many characters
there are, doesn't it?

How does this work for VARCHAR?

Why is the CHAR buffer padded, but it seems VARCHAR isn't?

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com