Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• Subject: mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Subject: Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• Subject: MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Subject: Re: Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
charset=XXX is not a valid parameter in connection string > >Re: How to use odbc

charset=XXX is not a valid parameter in connection string > >Re: How to use odbc

2007-11-14       - By ??

 Back
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 (See http://UTF-8.ora-code.com)??

????????????????????????


-- ---- ---- -----        
????
2007-11-14

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---
????????Jun Chen
??????????2007-11-14 12:23:59
????????myodbc@(protected)
??????
??????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@(protected)


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=mysql@(protected)