Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Turn on "fancy-format" for the optoverview.html document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
98e66068fe499095018ede2452a691ad |
| User & Date: | drh 2018-01-26 15:50:32 |
Context
|
2018-01-31
| ||
| 02:52 | Typo in the how-to-corrupt document. check-in: 6ad1abb448 user: drh tags: branch-3.22 | |
|
2018-01-26
| ||
| 18:38 | Update documentation for CAST to integer to describe what happens when the integer is too large. This behavior is only supported on the latest trunk, so with this check-in the documentation is no longer suitable for use with 3.22.0. check-in: 6b1b360098 user: drh tags: trunk | |
| 15:50 | Turn on "fancy-format" for the optoverview.html document. check-in: 98e66068fe user: drh tags: trunk | |
| 15:44 | Bring the query flattening section of the optoverview.html document up to date with version 3.22.0. check-in: a599e76d95 user: drh tags: trunk | |
Changes
Changes to pages/optoverview.in.
1
2
3
4
5
6
7
8
9
10
..
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
<title>The SQLite Query Optimizer Overview</title>
<tcl>hd_keywords {optimizer} {query planner} {SQLite query planner}</tcl>
<tcl>
proc SYNTAX {text} {
hd_puts "<blockquote><pre>"
set t2 [string map {& & < < > >} $text]
regsub -all "/(\[^\n/\]+)/" $t2 {</b><i>\1</i><b>} t3
hd_puts "<b>$t3</b>"
hd_puts "</pre></blockquote>"
................................................................................
if {$n==1} {
hd_puts "<h$n align='center'>$num $name</h$n>"
} else {
hd_puts "<h$n>$num $name</h$n>"
}
}
HEADING 0 {The SQLite Query Planner}
PARAGRAPH {
This document provides overview of how the query planner and optimizer
for SQLite works.
}
PARAGRAPH {
Given a single SQL statement, there might be dozens, hundreds, or even
|
>
>
<
<
|
1
2
3
4
5
6
7
8
9
10
11
12
..
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
<title>The SQLite Query Optimizer Overview</title>
<tcl>hd_keywords {optimizer} {query planner} {SQLite query planner}</tcl>
<fancy_format>
<tcl>
proc SYNTAX {text} {
hd_puts "<blockquote><pre>"
set t2 [string map {& & < < > >} $text]
regsub -all "/(\[^\n/\]+)/" $t2 {</b><i>\1</i><b>} t3
hd_puts "<b>$t3</b>"
hd_puts "</pre></blockquote>"
................................................................................
if {$n==1} {
hd_puts "<h$n align='center'>$num $name</h$n>"
} else {
hd_puts "<h$n>$num $name</h$n>"
}
}
PARAGRAPH {
This document provides overview of how the query planner and optimizer
for SQLite works.
}
PARAGRAPH {
Given a single SQL statement, there might be dozens, hundreds, or even
|