Hello.


When you are using mysql command line client under windows,

all data you see is in cp866 character set (property of all console programs).

And at the server side data is in cp1251 character set. So you should

use sql statements for correct work:

 SET character_set_client = 'cp866';

 SET character_set_results ='cp866';

 SET character_set_connection ='cp1251';

For more information see:

 http://dev.mysql.com/doc/mysql/en/Charset-connection.html









Alex <[EMAIL PROTECTED]> wrote:

> Hi people!

> 

> I have a server and client (C API) ver 4.1.8

> Server side was compiled under FreeBSD 5.2.1 with charset cp1251 as I 

> wanted it to sort russian strings from Windows clients properly.

> Client side (mysqlclient.lib) was downloaded as a compiled Windows binary.

> But when I started to insert data I've found that all russian chars are 

> in database replaced with '?' chars.

> Is that because precompiled Windows client library definately has main 

> charset latin1?

> What do I need to do with this?

> Shall I get sources and compile client library using cp1251? (by the way 

> I can configure it under Unix only :0))

> Or Can I do something else?

> 

> Any help or advise will be helpful

> 

> Alexander

> 



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to