diff options
| author | Monty <monty@mariadb.org> | 2021-10-07 20:15:34 +0300 |
|---|---|---|
| committer | Monty <monty@mariadb.org> | 2022-01-21 14:30:14 +0200 |
| commit | 699b8a45dee0d50ef6b076c2f3004bcf6d395b70 (patch) | |
| tree | ca1ed86fe8b00d41f480157548369034ad17e93a /mysql-test/main/subselect_mat.result | |
| parent | 5341d8188e06a345d74fac74b771d6a1fa81705c (diff) | |
| download | mariadb-git-699b8a45dee0d50ef6b076c2f3004bcf6d395b70.tar.gz | |
Update matching_candidates_in_table() to treat all conditions similar
Fixed also that the 'with_found_constraint parameter' to
matching_candidates_in_table() is as documented: It is now true only
if there is a reference to a previous table in the WHERE condition for
the current examined table (as it was originally documented)
Changes in test results:
- Filtered was 25% smaller for some queries (expected).
- Some join order changed (probably because the tables had very few rows).
- Some more table scans, probably because there would be fewer returned
rows.
- Some tests exposes a bug that if there is more filtered rows, then the
cost for table scan will be higher. This will be fixed in a later commit.
Diffstat (limited to 'mysql-test/main/subselect_mat.result')
| -rw-r--r-- | mysql-test/main/subselect_mat.result | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/mysql-test/main/subselect_mat.result b/mysql-test/main/subselect_mat.result index 8c659000a99..83213e0750d 100644 --- a/mysql-test/main/subselect_mat.result +++ b/mysql-test/main/subselect_mat.result @@ -1889,8 +1889,8 @@ WHERE alias4.c = alias3.b ); id select_type table type possible_keys key key_len ref rows Extra 1 PRIMARY NULL NULL NULL NULL NULL NULL NULL Impossible WHERE noticed after reading const tables -3 MATERIALIZED alias3 ALL NULL NULL NULL NULL 2 Using where -3 MATERIALIZED alias4 ref c c 11 test.alias3.b 2 Using where; Using index +3 MATERIALIZED alias3 ALL NULL NULL NULL NULL 2 +3 MATERIALIZED alias4 index c c 11 NULL 2 Using where; Using index; Using join buffer (flat, BNL join) DROP TABLE t1,t2; # # BUG#928048: Query containing IN subquery with OR in the where clause returns a wrong result |