Bug #34806 | quote() | ||
---|---|---|---|
Submitted: | 25 Feb 2008 13:16 | Modified: | 4 Apr 2008 3:34 |
Reporter: | trip Kano | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Charsets | Severity: | S3 (Non-critical) |
Version: | 4.0.13-nt | OS: | Windows (quote(field_name) not working, if my field has a char Ñ..) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 4.0, Ñ, quote |
[25 Feb 2008 13:16]
trip Kano
[25 Feb 2008 13:27]
Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, 4.0.30 at least (or, better, recent 4.1 or 5.0). In case of the same problem, please, send a complete test case.
[26 Mar 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[26 Mar 2008 9:13]
Susanne Ebrecht
Many thanks for writing a bug report. We need to know: when do you need this character? Do you need it as identifier for table names? Do you need it as user name or password? Do you just have text (or varchar/char) fields with that characters? Which language setting has your system? Also MySQL 4.0 isn't able to handle non-ASCII signs correct. Please let us know if your problem is fixed by using newer versions. The best would be to upgrade to MySQL 5.0.51a.
[2 Apr 2008 11:45]
trip Kano
it is only an entry in my database as a data (ex. a name), i just access it and out it with quote.. language is ENGLISH (Ascii) so far all other characters are o.k. we cant just upgrade a database because of some reason.. 1. The system,program is already deployed to the clients 2. If we upgrade, the possibility for errors is there and its risky
[2 Apr 2008 14:20]
Susanne Ebrecht
Many thanks for writing a bug report. You told your language settings are ASCII. The character Ñ isn't part of the ASCII character set. To get/store characters like "Ñ" or "ñ" in the right way you have to use Latin1 or UTF8. Therefor your column at the table where you want to store these letters has to Latin1 or UTF8 and also when you will get it out you must have a client of Latin1 or UTF8 and also your environment encoding should be ISO-8859-15 (or CP1252) for Latin1 client encoding or UTF8 for UTF8 client encoding.
[4 Apr 2008 3:34]
trip Kano
ok thanks ma'am.. i'll try that..