Bug #6568 | UTF-8 Support Missing/Broken in 4.1.9 (was 4.1.7) | ||
---|---|---|---|
Submitted: | 11 Nov 2004 5:42 | Modified: | 26 Apr 2005 5:52 |
Reporter: | James Barwick | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S3 (Non-critical) |
Version: | 4.1.9 | OS: | Linux (SuSE 9.0) |
Assigned to: | CPU Architecture: | Any |
[11 Nov 2004 5:42]
James Barwick
[24 Mar 2005 4:43]
Jorge del Conde
Hi I was unable to reproduce this using FC2 and 4.1.11 from bk.
[24 Mar 2005 4:44]
Jorge del Conde
James, can you please tell me if you can reproduce this behaviour using the latest code from our bk tree ? thanks.
[24 Mar 2005 12:38]
Sergei Golubchik
regex crash that you experience was probably fixed in 4.1.8 (see bug#7111). Incorrect characters - php does not read [mysql] section in my.cnf
[26 Mar 2005 5:52]
James Barwick
Couple of follow-ups...We have moved on to the 4.1.9 source and compiled. We have removed all references to REGEXP in our application (we only had a couple) and are now doing REGEXP in PHP script, not the database. (we are afraid of mysql now). Our 4.1.9 environment with PHP 4.3.8 is now running on 8 servers in UTF-8 mode in "production". We are watching performance carefully...Note: LC_TYPE and LANG are set to "en_US.UTF8", not "C". (SuSE root user configuration has an option to set LC_TYPE to C, we are not doing that..root user is UTF8...and subsiquently the mysql user which the database runs under has LANG/LC_TYPE set to UTF8 as well) my.cnf default charset is utf8 and all table default charsets are UTF8 3 Machines are SuSE 9.0, and 5 Machines are RedHat 9.0 We have 3 more test Machines Running SuSE 9.0, 1 Development machine running SuSE 9.0, another Development Machine running SuSE 9.2, and another Development Machine running SuSE 9.0 (x86_64...soon to be upgraded to SuSE 9.2-x86_64) We do not have any have servers on mySQL 4x release older than 4.1.9. we do have 3 more servers Running RedHat 9.0 with mySQL 3.23 we are scheduling for upgrade. And only upgrading the DB because of UTF8 character problems in the database. (I was dumn 2 years ago and thought that we could deploy enough checks in the application to keep bad UTF8 out of the database...biggest problems is inserting into short fields with truncation errors...my guys keep forgetting to truncate the data in PHP or in Java)...oh, well...live and learn....we will soon see if MySQL4.1.9 handles this nicely...hope so...not enough experience just yet...(very difficult to test in the lab...my QA team say the initial tests looked good)...anyway... I will try to over the next couple of days, follow-up on the 4.1.9 source to determine if REGEXP is dying and causing a server crash. Sorry guys...please be patient.
[26 Apr 2005 23: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".