Re: utf8 in QB

Hey Mike,

Your posts have clarified a lot, but I'm still unsure about a couple of
things.

The client is the MySQL client library (the DLL on Windows) not the
> application.


So the client is the piece of code that sits on the opposite side of the
TCP/IP connection (opposite to the server) and communicates with the server?
So, if I write mysql_query('select * from blah*') in my PHP program, the PHP
program itself is not the client, but merely is instructing the (PHP
version?) mysql client to tell the server to execute the statement?

eg:

|QB|--->|client (windows dll)|------connection---------------->|server|
or
|PHP|--->|PHP driver (the client)|-------connection-------->|server|

So when I type in statements into the mysql command line client, I myself am
not the client, but I'm telling the client to execute statements for me
(kind of like in the above example the PHP not being the client, but the PHP
telling the client to do work)?

Is the character_set_client the encoding that is coming *out* of the client
and into the connection, and the character_set_connection the encoding that
is coming *out* of the connection and into the server? What would happen if
I inputted a UCS-2 file into the command line client and set
character_set_client to be UTF8, would the client have to translate into
UTF8?

|FILE|----ucs2---->|command line client|----utf8---->|connection|

If this is the case, how does the command line client know the encoding of
the input?

Or is it more to indicate to the connection how the data incoming from the
client is encoded?

|FILE|----ucs2---->|command line client|----ucs2----->|connection|

How does character_set_connection come into play? What is it's role? The
manual isn't very clear..

Is the command line client essentially the same client (Windows DLLs) that
QB uses?

Thanks *a lot* for your help!!

Taras