Hello,

Helen, you wrote:

> You don't have to tell the client what it is getting from the UI. It
> knows
> that. You only have to tell it what to store or search for, and only
> if it
> is storing or searching columns that are not in the default character
> set.

How could the client know what it is getting from the UI?
On Win32 for instance, what does this means?
Does it mean that the client assume that strings passed to the API are
encoded in the system default codepage ? Or in the process codepage ?
Or in the thread codepage ?

What if this coding is 'Wide' strings (UTF-16) ? Will the conversion
from UTF-16 to UNICODE_FSS work ?

What's the purpose of the lc_ctype if it should always be set to match
the character set of the database (which you wrote in another sentence)
?

Now, you're getting me confused.

From a previous post in this topic, I was seeing things as this:

The DB is set for instance for UNICODE_FSS.
I attach with ISO_8859_1 and all strings I give or get to/from the
engine are encoded in ISO_8859_1, while stored in UNICODE_FSS. The
required translation (which might fail for some characters) happens
somewhere in the client or in the engine.

What's wrong, what's right ? Getting lost a bit here.

--
Olivier Mascia