diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-06-03 05:16:44 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-06-03 05:16:44 +0000 |
| commit | 62a67b10ff9f9eea6a4695649fb8252d2a4bc74d (patch) | |
| tree | 7b54cadc082d323cda5fd24248e85b7d2ea664a3 /www/eqp.html | |
| parent | Adding debian version 3.45.3-1. (diff) | |
| download | sqlite3-62a67b10ff9f9eea6a4695649fb8252d2a4bc74d.tar.xz sqlite3-62a67b10ff9f9eea6a4695649fb8252d2a4bc74d.zip | |
Merging upstream version 3.46.0.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'www/eqp.html')
| -rw-r--r-- | www/eqp.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/www/eqp.html b/www/eqp.html index b4e68fa..fff35c6 100644 --- a/www/eqp.html +++ b/www/eqp.html @@ -271,7 +271,7 @@ QUERY PLAN </pre></div> <p> - All joins in SQLite are <a href="optoverview.html#table_order">implemented using nested scans</a>. When a + All joins in SQLite are <a href="optoverview.html#joins">implemented using nested scans</a>. When a SELECT query that features a join is analyzed using EXPLAIN QUERY PLAN, one SCAN or SEARCH record is output for each nested loop. For example: </p><div class="codeblock"><pre>sqlite> EXPLAIN QUERY PLAN SELECT t1.*, t2.* FROM t1, t2 WHERE t1.a=1 AND t1.b>2; |