Bug #50429 | ASCII function in WHERE clause is causing incorrect updates/deletes on slave | ||
---|---|---|---|
Submitted: | 18 Jan 2010 23:08 | Modified: | 19 Feb 2010 6:19 |
Reporter: | Victor Kirkebo | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.1.43 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | ascii function, delete, UPDATE |
[18 Jan 2010 23:08]
Victor Kirkebo
[19 Jan 2010 6:19]
Sveta Smirnova
Thank you for the report. I can not reepat described behavior. Please provide output of SHOW VARIABLES LIKE 'char%' on both master and slave.
[19 Jan 2010 9:22]
Victor Kirkebo
On both master and slave: mysql> SHOW VARIABLES LIKE 'char%'; +--------------------------+---------------------------------------------------------------------------------+ | Variable_name | Value | +--------------------------+---------------------------------------------------------------------------------+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results | latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /export/home/lroot/vk136562/mysql-5.1.43-solaris10-x86_64/share/mysql/charsets/ | +--------------------------+---------------------------------------------------------------------------------+ 8 rows in set (0.00 sec) mysql> SHOW VARIABLES LIKE 'version%'; +-------------------------+---------------------+ | Variable_name | Value | +-------------------------+---------------------+ | version | 5.1.43-log | | version_comment | Source distribution | | version_compile_machine | x86_64 | | version_compile_os | pc-solaris2.10 | +-------------------------+---------------------+ 4 rows in set (0.00 sec)
[20 Jan 2010 9:13]
Victor Kirkebo
I just tried again with the latest 5.1.43 build but now I cannot recreate the problem.
[20 Feb 2010 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".