diff options
| author | gkodinov@mysql.com <> | 2006-05-11 15:30:54 +0300 |
|---|---|---|
| committer | gkodinov@mysql.com <> | 2006-05-11 15:30:54 +0300 |
| commit | 0486cfbee29d417cffdb4eba79d6b9c435495987 (patch) | |
| tree | 806e73783799e5eb151e4898a3ed1e6c801f1091 /mysql-test/r/view.result | |
| parent | 1efda1ea54f25165b71389acd81968a01d70905a (diff) | |
| download | mariadb-git-0486cfbee29d417cffdb4eba79d6b9c435495987.tar.gz | |
BUG#7549: Missing error message for invalid view selection with subquery.
When a view statement is compiled on CREATE VIEW time, most of the
optimizations should not be done. Finding the right optimization
for a subquery is one of them.
Unfortunately the optimizer is resolving the column references of
the left expression of IN subqueries in the process of deciding
witch optimization to use (if needed). So there should be a
special case in Item_in_subselect::fix_fields() : check the
validity of the left expression of IN subqueries in CREATE VIEW
mode and then proceed as normal.
Diffstat (limited to 'mysql-test/r/view.result')
| -rw-r--r-- | mysql-test/r/view.result | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mysql-test/r/view.result b/mysql-test/r/view.result index 667d10cd145..a89b6e9b3b1 100644 --- a/mysql-test/r/view.result +++ b/mysql-test/r/view.result @@ -706,7 +706,7 @@ create view v1 as select a from t1; create view v2 as select a from t2 where a in (select a from v1); show create view v2; View Create View -v2 CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `v2` AS select `t2`.`a` AS `a` from `t2` where `a` in (select `v1`.`a` AS `a` from `v1`) +v2 CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `v2` AS select `t2`.`a` AS `a` from `t2` where `t2`.`a` in (select `v1`.`a` AS `a` from `v1`) drop view v2, v1; drop table t1, t2; CREATE VIEW `v 1` AS select 5 AS `5`; |