diff options
author | unknown <evgen@moonbone.local> | 2006-11-14 19:50:44 +0300 |
---|---|---|
committer | unknown <evgen@moonbone.local> | 2006-11-14 19:50:44 +0300 |
commit | 1019dd404c273b722daa4039d42b1a920439e6b1 (patch) | |
tree | d10a53e376fd473c3ab10173af53e5dab66d8e5c /include/my_time.h | |
parent | 405dcd2df29e4693a0981c186d0c55b2f9a37b84 (diff) | |
download | mariadb-git-1019dd404c273b722daa4039d42b1a920439e6b1.tar.gz |
Bug#20045: Server crash on INSERT ... SELECT ... FROM non-mergeable view
The regression is caused by the fix for bug 14767. When INSERT ... SELECT
used a view in the SELECT list that was not inlined, and there was an
active transaction, the server could crash in Query_cache::invalidate.
On INSERT ... SELECT only the table being inserted into is invalidated.
Thus views that can't be inlined are skipped from invalidation.
The bug manifests itself in two ways so there is 2 test cases.
One checks that the only the table being inserted into is invalidated.
And the second one checks that there is no crash on INSERT ... SELECT.
mysql-test/t/query_cache.test:
Added a test case for bug#20045: Server crash on INSERT ... SELECT ... FROM non-mergeable view
mysql-test/r/query_cache.result:
Added a test case for bug#20045: Server crash on INSERT ... SELECT ... FROM non-mergeable view
sql/sql_parse.cc:
Bug#20045: Server crash on INSERT ... SELECT ... FROM non-mergeable view
On INSERT ... SELECT only the table being inserted into is invalidated.
Diffstat (limited to 'include/my_time.h')
0 files changed, 0 insertions, 0 deletions