maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #02295
Updated (by Psergey): MariaDB 5.3 (91)
-----------------------------------------------------------------------
WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...........: MariaDB 5.3
CREATION DATE..: Sun, 28 Feb 2010, 14:01
SUPERVISOR.....: Monty
IMPLEMENTOR....:
COPIES TO......:
CATEGORY.......: Server-RawIdeaBin
TASK ID........: 91 (http://askmonty.org/worklog/?tid=91)
VERSION........: WorkLog-3.4
STATUS.........: Un-Assigned
PRIORITY.......: 60
WORKED HOURS...: 0
ESTIMATE.......: (hours remain)
ORIG. ESTIMATE.: 0
PROGRESS NOTES:
-=-=(Psergey - Sun, 28 Feb 2010, 14:48)=-=-
Title modified.
--- /tmp/wklog.91.old.21924 2010-02-28 14:48:29.000000000 +0000
+++ /tmp/wklog.91.new.21924 2010-02-28 14:48:29.000000000 +0000
@@ -1 +1 @@
-Subqueries: Inside-out execution for non-semijoin materialized subqueries that are AND-parts of the WHERE
+MariaDB 5.3
-=-=(Psergey - Sun, 28 Feb 2010, 14:09)=-=-
Dependency created: 94 now depends on 91
DESCRIPTION:
Consider the following case:
SELECT * FROM big_table
WHERE oe IN (SELECT ie FROM table_with_few_groups
WHERE ...
GROUP BY group_col) AND ...
Here the best way to execute the query is:
Materialize the subquery;
# now run the join:
for each record R1 in materialized table
for each record R2 in big_table such that oe=R1
pass R2 to output
Semi-join materialization supports such strategy with SJM-Scan strategy. This WL
entry is about adding support for such strategies for non-semijoin subqueries.
ESTIMATED WORK TIME
ESTIMATED COMPLETION DATE
-----------------------------------------------------------------------
WorkLog (v3.5.9)