diff options
| author | Karthik Kamath <karthik.kamath@oracle.com> | 2015-08-18 10:38:06 +0530 |
|---|---|---|
| committer | Karthik Kamath <karthik.kamath@oracle.com> | 2015-08-18 10:38:06 +0530 |
| commit | 93ac0eb1c46a708529b290fd072c9d1e3e3526e8 (patch) | |
| tree | f2d01076e5db8d4bec8bb191b737af1ea650793c | |
| parent | 8fe0708808ddba0d85798d0cd9100b3173064081 (diff) | |
| download | mariadb-git-93ac0eb1c46a708529b290fd072c9d1e3e3526e8.tar.gz | |
BUG#11754258: INCORRECT ERROR MESSAGE WHEN CREATING UNSAFE
VIEW
It appears that the code refactoring done as part of the
patch for the MySQL BUG#11749859 fixed this issue. This
issue is not reproducible on MySQL 5.5+ versions now.
As part of this patch, the test file "mysqldump.test" has
been updated to remove the comment which was referring to
the bug and also the line which suppresses the warning.
| -rw-r--r-- | mysql-test/t/mysqldump.test | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/mysql-test/t/mysqldump.test b/mysql-test/t/mysqldump.test index 54780b95627..11d766c3293 100644 --- a/mysql-test/t/mysqldump.test +++ b/mysql-test/t/mysqldump.test @@ -875,13 +875,8 @@ select * from t1; create view v1 as select * from v3 where b in (1, 2, 3, 4, 5, 6, 7); -# Disable warnings since LIMIT warning for unsafe statement if -# binlog_format = STATEMENT. Note: after BUG#45832, the warning should -# not be issued. ---disable_warnings create view v2 as select v3.a from v3, v1 where v1.a=v3.a and v3.b=3 limit 1; ---enable_warnings --exec $MYSQL_DUMP --skip-comments test |