Details
Major
Description
mysqld.exe!simplify_joins()[sql_select.cc:12827] mysqld.exe!JOIN::optimize()[sql_select.cc:1054] mysqld.exe!st_select_lex::optimize_unflattened_subqueries()[sql_lex.cc:3476] mysqld.exe!mysql_delete()[sql_delete.cc:123] mysqld.exe!mysql_execute_command()[sql_parse.cc:3067] mysqld.exe!Prepared_statement::execute()[sql_prepare.cc:3905] mysqld.exe!Prepared_statement::execute_loop()[sql_prepare.cc:3564] mysqld.exe!mysql_sql_stmt_execute()[sql_prepare.cc:2732] mysqld.exe!mysql_execute_command()[sql_parse.cc:2207] mysqld.exe!mysql_parse()[sql_parse.cc:5765] mysqld.exe!dispatch_command()[sql_parse.cc:1071] mysqld.exe!do_command()[sql_parse.cc:794] mysqld.exe!threadpool_process_request()[threadpool_common.cc:224] mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
drop table if exists `t1`,`t2`,`v1`; create table `t1`(`a` int)engine=innodb; create table `t2`(`a` int)engine=innodb; create or replace view `v1` as select `a` from `t1`; prepare s from "delete from `t2` order by (select 1 from `v1`)"; execute s;
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
merge for insert should be called only for one table (where we delete/insert)
"merge for insert" put view table in place, then re-initialization before execution removes it, and normal merge does not touch it because the table marked as "merged for insert" and is not part of multi-update or multi-delete.
IMHO "merge for insert" should be applicable only for tables which top view belongs to "main" SELECT_LEX
pushed to 5.3
the problem is that derived->merged is not set for v1...