Bug #13465 | ASP shows question marks instead of Hebrew Chars when conn to MySQL 4.1 | ||
---|---|---|---|
Submitted: | 25 Sep 2005 8:36 | Modified: | 10 Jan 2008 18:46 |
Reporter: | Alon Solell | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51.11, 3.51.19 | OS: | Windows (Windows 2003 Server Standard) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ADO |
[25 Sep 2005 8:36]
Alon Solell
[25 Sep 2005 9:54]
Vasily Kishkin
Could you please create and attach some ASP test case ? Do you use IIS?
[26 Sep 2005 23:34]
Alon Solell
My ASP sample code to extract data from MySQL
Attachment: alon.asp (application/octet-stream, text), 1.50 KiB.
[26 Sep 2005 23:35]
Alon Solell
Sample data to be used. The purpose is to see Hebrew and not question marks
Attachment: alon-TableSample-1.txt (text/plain), 20.43 KiB.
[26 Sep 2005 23:36]
Alon Solell
Yes. I use IIS6
[28 Sep 2005 8:38]
Vasily Kishkin
Could you please insert the follow commands after your opened connection: SET character_set_client=hebrew SET character_set_results=hebrew and test you asp file ?
[28 Sep 2005 12:56]
Alon Solell
Hi Vasily, Where should I enter those entries? In what file? the ASP file? in the Database Creation? In the my.ini file? If I understand you correctly you want me to enter that after the DSN connnection? or as part of the DSN connection? This is my ASP connect strings. I have the choice of doing it via DSN, or as a connect string. Both work (I just need to comment one out). 'MySQL ODBC Connection String datasourcename = "DRIVER={MySQL ODBC 3.51 Driver}; SERVER=localhost;DATABASE=databasename; USER=username; PASSWORD=password; port=3309 OPTION=3;" datasourcename = "samba1" OR,. did you mean somewhere else? Thanks, -Alon.
[30 Sep 2005 0:51]
Alon Solell
datasourcename = "DRIVER={MySQL ODBC 3.51 Driver}; SERVER=localhost;DATABASE=databasename; USER=username; PASSWORD=password; port=3309 OPTION=3;SET character_set_client=hebrew; SET character_set_results=hebrew" This just brings the same results with the question marks. Any other suggetionts? -Alon
[10 Jan 2006 7:03]
Eliyahu Peter Kornfeld
I have the same problem with MySQL 5.0.18 usin MSVC and ODBC to get the data. In fact I tried every possible character set for the connection without results. To be honest with this problem I forced to remove MySQL, it is useless to me.
[12 Jul 2006 19:29]
Bogdan Degtyariov
I was able to reproduce this bug in Win2003 server SP1
[12 Jul 2006 20:12]
Alon Solell
Hello Bogdan Degtyariov, I am happy you were able to replicate the problem. Till now, I've dropped the support for 4.1 and 5.x and left users who I wanted to port from MS-ACCESS on MS-ACCESS as it was a not a viable option to have question marks instead of chars. Now that you finally got to replicate the problem, do you think this can be escallated and be resolved? Thanks, -Alon.
[28 Sep 2007 5:52]
Tonci Grgin
Bogdan, what is the status of this problem?
[28 Sep 2007 12:08]
Tonci Grgin
Bug#29367 has been marked as duplicate of this one.
[31 Dec 2007 14:31]
Bogdan Degtyariov
MyODBC 5.1.1-beta displays Hebrew characters correctly.
[31 Dec 2007 17:28]
Bogdan Degtyariov
Strange test case. Run it and see hebrew characters not displayed correctly through Response.Write
Attachment: alon2.asp (application/octet-stream, text), 259 bytes.
[10 Jan 2008 18:46]
Jess Balint
Unicode is not supported in ADO applications (including ASP) with the Connector/ODBC 3.51 driver. Please consider testing MySQL Connector/ODBC 5.1 which includes Unicode support for ASP.