Kjell Rilbe wrote:

> OK. I now I understand that the client application has to transliterate
> to the connection's character set, regardless what character set is used
> in each DB column. Is this correct?

Yes.

> So, if a DB contains one UTF8 column and one ISO8859_1 column, and the
> client connects with UTF8, then the application has to send the
> ISO8859_1 data in UTF8 format, even if the data actually entered into
> the client application already is ISO8859_1.

Yes.

> Would it be possible to select connection character set on a per column
> or per parameter basis?

It wouldn't make sense. For example, what if your INSERT statement uses
both columns at the same time?

> It seems to me that it would be useful to be able to do so.

I don't see a case. But, I do see a lot of cases where it would not work.

> On the other hand, you could always have such application connect with
> NONE and make sure it's aware of each column's character set. That way
> it would be able to send data in different character sets for different
> columns. Right?

Yes.

--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com