diff options
| author | unknown <sanja@askmonty.org> | 2012-12-28 14:41:46 +0200 |
|---|---|---|
| committer | unknown <sanja@askmonty.org> | 2012-12-28 14:41:46 +0200 |
| commit | 6f26aac9409e3456798e58a4ee4306e43c7ebf7b (patch) | |
| tree | df8ad17736247d1493460205865fb75757a00ae1 /sql/item.cc | |
| parent | e99aa91e90adfd54cc1f460dd8cdd19614f30abc (diff) | |
| download | mariadb-git-6f26aac9409e3456798e58a4ee4306e43c7ebf7b.tar.gz | |
MDEV-3873 & MDEV-3876 & MDEV-3912 : Wrong result (extra rows) with ALL subquery
from a MERGE view.
The problem was in the lost ability to be null for the table of a left join if it
is a view/derived table.
It hapenned because setup_table_map(), was called earlier then we merged
the view or derived.
Fixed by propagating new maybe_null flag during Item::update_used_tables().
Change in join_outer.test and join_outer_jcl6.test appeared because
IS NULL reported no used tables (i.e. constant) for argument which could not be
NULL and new maybe_null flag was propagated for IS NULL argument (Item_field)
because table the Item_field belonged to changed its maybe_null status.
Diffstat (limited to 'sql/item.cc')
| -rw-r--r-- | sql/item.cc | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/sql/item.cc b/sql/item.cc index 16dbd011f22..aee35b611e7 100644 --- a/sql/item.cc +++ b/sql/item.cc @@ -9166,11 +9166,18 @@ table_map Item_ref::used_tables() const void Item_ref::update_used_tables() -{ +{ if (!get_depended_from()) - (*ref)->update_used_tables(); + (*ref)->update_used_tables(); + maybe_null= (*ref)->maybe_null; } +void Item_direct_view_ref::update_used_tables() +{ + Item_ref::update_used_tables(); + if (view->table && view->table->maybe_null) + maybe_null= TRUE; +} table_map Item_direct_view_ref::used_tables() const { |