diff options
author | Sergey Glukhov <Sergey.Glukhov@sun.com> | 2010-10-18 16:12:27 +0400 |
---|---|---|
committer | Sergey Glukhov <Sergey.Glukhov@sun.com> | 2010-10-18 16:12:27 +0400 |
commit | d0ac4e2c5ade16d6d0833137aa67071b34e66964 (patch) | |
tree | 5b477ae757b3fb5b170a6d815c5b1981d39c037a /mysql-test/t/cache_innodb-master.opt | |
parent | 127c721cef2c1b248af79a386c174a5e7addd556 (diff) | |
download | mariadb-git-d0ac4e2c5ade16d6d0833137aa67071b34e66964.tar.gz |
Bug#56814 Explain + subselect + fulltext crashes server
create_sort_index() function overwrites original JOIN_TAB::type field.
At re-execution of subquery overwritten JOIN_TAB::type(JT_ALL) is
used instead of JT_FT. It misleads test_if_skip_sort_order() and
the function tries to find suitable key for the order that should
not be allowed for FULLTEXT(JT_FT) table.
The fix is to restore JOIN_TAB strucures for subselect on re-execution
for EXPLAIN.
Additional fix:
Update TABLE::maybe_null field which
affects list_contains_unique_index() behaviour as it
could have the value(maybe_null==TRUE) based on the
assumption that this join is outer
(see setup_table_map() func).
mysql-test/r/explain.result:
test case
mysql-test/t/explain.test:
test case
sql/item_subselect.cc:
Make subquery uncacheable in case of EXPLAIN. It allows to keep
original JOIN_TAB::type(see JOIN::save_join_tab) and restore it
on re-execution.
sql/sql_select.cc:
-restore JOIN_TAB strucures for subselect on re-execution for EXPLAIN
-Update TABLE::maybe_null field as it could have
the value(maybe_null==TRUE) based on the assumption
that this join is outer(see setup_table_map() func).
This change is not related to the crash problem but
affects EXPLAIN results in the test case.
Diffstat (limited to 'mysql-test/t/cache_innodb-master.opt')
0 files changed, 0 insertions, 0 deletions