Hello all,

I added utf8 as character set in odbc connection
string. The odbc driver version is 3.51 and mysql
5.0.x. The problem is that the saved Chinese
characters in the table were displayed as ???? and can
not be read. Here is the connection string.

Driver={MySQL ODBC 3.51
Driver};database=dbname;option=0;port=3306;server=localhost; uid=userid;charset=UTF8

However the Chinese text saved through mysql Query gui
interface can be displayed correctly. The mysql
database was created with character set uft8.

Is there anyone who knows where is the problem?

Thanks.
-Jun C.

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

Hi Chen Jun:

'charset=XXX' is not a valid parameter in connection string, so it will not affect the client encoding.
you can execute a 'SET CHARACTER SET XXX' sql statement to change the client encoding after a database connection is created/established.

Also, you can use ODBC DataSource instead of connection string, i prefer ODBC datas ource because there's an 'Initial Statement' option in MyODBC configuation dialog, you can set it to 'SET CHARACTER SET XXX' so that your application does not need to care about the client encoding.

The client encoding need not be the same as the server encoding. If you web pages are encoded in GB18030/GBK/GB2312, then you need to use GBK as the client encoding.

Wish it can help you.

############
ODBC 链接字符串并没有 charset=XXX 这一项，所以这样不能更改客户端的编码，你可以在数据库连接成功 后先执行一个 SET CHARACTER SET XXX 的 SQL 语句，这样才能更改你的客户端编码。

如果环境允许的话，我推荐你还是通过 ODBC 数据源来访问数据库，因为 MyODBC 里可以配置一个 Initial Statement 的选项，把 SET CHARACTER SET XXX 语句写在这里就行了，你的程序也不用关心编码的事情了

还有就是：客户端编码不一定非得跟数据库服务器的编码一致，假设 你的 web 页面都用 GB 系列编码的话，那你应该用 GBK 作为客户端的编码，而不是 UTF-8。

希望这些能对你有所帮助。


------------------
刘研
2007-11-14

------------------------------------------------------------ -
发件人：Jun Chen
发送日期：2007-11-14 12:23:59
收件人：myodbc [at] lists.mysql.com
抄送：
主题：How to use odbc to save Chinese into mysql in ASP.NET

Hello all,

I added utf8 as character set in odbc connection
string. The odbc driver version is 3.51 and mysql
5.0.x. The problem is that the saved Chinese
characters in the table were displayed as ???? and can
not be read. Here is the connection string.

Driver={MySQL ODBC 3.51
Driver};database=dbname;option=0;port=3306;server=localhost; uid=userid;charset=UTF8

However the Chinese text saved through mysql Query gui
interface can be displayed correctly. The mysql
database was created with character set uft8.

Is there anyone who knows where is the problem?

Thanks.
-Jun C.

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=lovetide [at] 21cn.com


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

3.5x versions of ODBC can not handle Chinese characters. I had to switch to
the 5.x series, and then I was able to work with Chinese characters.

Regards,

Jerry Schwartz
The Infoshop by Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341

www.the-infoshop.com
www.giiexpress.com
www.etudes-marche.com

> -----Original Message-----
> From: Jun Chen [mailto:acgtek [at] yahoo.com]
> Sent: Tuesday, November 13, 2007 5:57 PM
> To: myodbc [at] lists.mysql.com
> Subject: How to use odbc to save Chinese into mysql in ASP.NET
>
> Hello all,
>
> I added utf8 as character set in odbc connection
> string. The odbc driver version is 3.51 and mysql
> 5.0.x. The problem is that the saved Chinese
> characters in the table were displayed as ???? and can
> not be read. Here is the connection string.
>
> Driver={MySQL ODBC 3.51
> Driver};database=dbname;option=0;port=3306;server=localhost; uid=userid;
> charset=UTF8
>
> However the Chinese text saved through mysql Query gui
> interface can be displayed correctly. The mysql
> database was created with character set uft8.
>
> Is there anyone who knows where is the problem?
>
> Thanks.
> -Jun C.
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe: http://lists.mysql.com/myodbc?unsub=jerry [at] gii.co.jp





--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org