diff options
| author | guilhem@mysql.com <> | 2006-02-18 17:32:15 +0100 |
|---|---|---|
| committer | guilhem@mysql.com <> | 2006-02-18 17:32:15 +0100 |
| commit | 37c1744a036c27692df20476351ec31031fce086 (patch) | |
| tree | 511d7e8f8e3f949e041ae1f5a254d0aeb39ed4f9 /mysql-test/t/sql_mode.test | |
| parent | 56bed24c926e7427002c342eef9cb3d0839aa780 (diff) | |
| download | mariadb-git-37c1744a036c27692df20476351ec31031fce086.tar.gz | |
Fix for BUG#13897 "failure to do SET SQL_MODE=N where N is a number > 31" (the original bug's title isn't the simplest
symptom). sys_var::check_set() was wrong. mysqlbinlog makes use of such SET SQL_MODE=N
(where N is interpreted like if SQL_MODE was a field of type SET), so
this bug affected recovery from binlogs if the server was running with certain SQL_MODE values,
for example the default values on Windows (STRICT_TRANS_TABLES); to work around this bug people
had to edit mysqlbinlog's output.
Diffstat (limited to 'mysql-test/t/sql_mode.test')
| -rw-r--r-- | mysql-test/t/sql_mode.test | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/mysql-test/t/sql_mode.test b/mysql-test/t/sql_mode.test index 8ae9ced6c68..b67f1a73db6 100644 --- a/mysql-test/t/sql_mode.test +++ b/mysql-test/t/sql_mode.test @@ -255,4 +255,13 @@ create view v2 as select a from t2 where a in (select a from v1); drop view v2, v1; drop table t1, t2; +select @@sql_mode; +set sql_mode=2097152; +select @@sql_mode; +set sql_mode=16384+(65536*4); +select @@sql_mode; +--error 1231 +set sql_mode=2147483648; # that mode does not exist +select @@sql_mode; + SET @@SQL_MODE=@OLD_SQL_MODE; |