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/r/derived_opt.result | |
| 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/r/derived_opt.result')
| -rw-r--r-- | mysql-test/r/derived_opt.result | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/mysql-test/r/derived_opt.result b/mysql-test/r/derived_opt.result index 721d4277775..c5376bee756 100644 --- a/mysql-test/r/derived_opt.result +++ b/mysql-test/r/derived_opt.result @@ -273,4 +273,13 @@ ON alias3.f4 != 0 ) ON alias3.f4 != 0; f4 f4 f2 f4 drop table t1,t2,t3,t4; +# +# LP BUG#910123 MariaDB 5.3.3 causes 1093 error on Drupal +# Fix: force materialization in case of conflict +# +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; set optimizer_switch=@exit_optimizer_switch; |