diff options
author | unknown <sanja@montyprogram.com> | 2012-02-14 16:52:56 +0200 |
---|---|---|
committer | unknown <sanja@montyprogram.com> | 2012-02-14 16:52:56 +0200 |
commit | 764eeeee74f999fe2107fc362236563be0025093 (patch) | |
tree | 8af3359111969a90c2670d887c5ef79262aab74f /mysql-test/t/derived_opt.test | |
parent | 7ab53e80627e54c6dece486bf0b059436b7e5777 (diff) | |
download | mariadb-git-764eeeee74f999fe2107fc362236563be0025093.tar.gz |
Fix for LP BUG#910123 MariaDB 5.3.3 causes 1093 error on Drupal
Problem was that now we can merge derived table (subquery in the FROM clause).
Fix: in case of detected conflict and presence of derived table "over" the table which cased the conflict - try materialization strategy.
Diffstat (limited to 'mysql-test/t/derived_opt.test')
-rw-r--r-- | mysql-test/t/derived_opt.test | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/mysql-test/t/derived_opt.test b/mysql-test/t/derived_opt.test index 42f3ce296e1..c2f831036e1 100644 --- a/mysql-test/t/derived_opt.test +++ b/mysql-test/t/derived_opt.test @@ -202,5 +202,15 @@ RIGHT JOIN ( drop table t1,t2,t3,t4; +--echo # +--echo # LP BUG#910123 MariaDB 5.3.3 causes 1093 error on Drupal +--echo # Fix: force materialization in case of conflict +--echo # +SET optimizer_switch='derived_merge=on'; +CREATE TABLE t1 ( i INT ); +INSERT INTO t1 VALUES ( (SELECT 1 FROM ( SELECT * FROM t1 ) as a) ); +drop table t1; +set optimizer_switch=@save_optimizer_switch; + # The following command must be the last one the file set optimizer_switch=@exit_optimizer_switch; |