summaryrefslogtreecommitdiff
path: root/mysql-test/r/subselect_nulls.result
Commit message (Collapse)AuthorAgeFilesLines
* Create 'main' test directory and move 't' and 'r' thereMichael Widenius2018-03-291-123/+0
|
* MDEV-7339 Server crashes in Item_func_trig_cond::val_intSergei Golubchik2017-07-121-0/+6
| | | | | | | | | | | | | | | | Item_in_subselect::pushed_cond_guards[] array is allocated only when left_expr->maybe_null. And it is used (for row expressions) when left_expr->element_index(i)->maybe_null. For left_expr being a multi-column subquery, its maybe_null is always false when the subquery doesn't use tables (see Item_singlerow_subselect::fix_length_and_dec() and subselect_single_select_engine::fix_length_and_dec()), otherwise it's always true. But row elements can be NULL regardless, so let's always allocate pushed_cond_guards for multi-column subqueries, no matter whether its maybe_null was forced to true or false.
* Change the default @@optimizer_switch settings:Sergey Petrunya2011-11-021-0/+3
| | | | | | - semijoin=on - firstmatch=on - loosescan=on
* Backport of subquery optimizations to 5.3.Sergey Petrunya2010-01-171-0/+114
There are still test failures because of: - Wrong query results in outer join + semi join - EXPLAIN output differences