Bug #16331 Variable 'sql_mode' can't be set to the value of '501219328'
Submitted: 10 Jan 2006 10:27 Modified: 17 Jan 2006 12:50
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.18, 5.0-bk OS:Linux (linux, windows)
Assigned to: CPU Architecture:Any

[10 Jan 2006 10:27] Shane Bester 
Description:
After executing update SQL statements with sql_mode, roll-forward recovery results in syntax error. It seems binary log does not contain correct info
about sql_mode variable.

How to repeat:
start mysqld with --log-bin option and execute:

SET sql_mode=TRADITIONAL;
CREATE TABLE tbl1 (col1 INTEGER);

Run mysqlbinlog on the binlog.  It contains a line:

SET @@session.sql_mode=501219328;

which is invalid.

>mysql -uroot -p12345 -h 192.168.250.13 db <sql.txt
ERROR 1231 (42000) at line 11: Variable 'sql_mode' can't be set to the value of '501219328'

Suggested fix:
not sure
[10 Jan 2006 10:29] MySQL Verification Team 
Generated binlog which contains invalid sql_mode value

Attachment: binlog_sql_bug16331.txt (text/plain), 853 bytes.
[17 Jan 2006 12:50] Sergei Golubchik 
Please do not submit the same bug more than once. An existing
bug report already describes this very problem. Even if you feel
that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments
to the original bug instead.

Thank you for your interest in MySQL.

Additional info:

a duplicate of BUG#13897