Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in the queryplanner.html document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | branch-3.8.8 |
| Files: | files | file ages | folders |
| SHA1: |
94ffc3e5cbf8c86730287b41bea3dfa3 |
| User & Date: | drh 2015-03-16 20:37:17 |
Context
|
2015-03-16
| ||
| 22:22 | Fix typos in the FAQ. Leaf check-in: 973dd7c44b user: drh tags: branch-3.8.8 | |
| 20:37 | Fix a typo in the queryplanner.html document. check-in: 94ffc3e5cb user: drh tags: branch-3.8.8 | |
| 18:07 | Fix a typo in the isolation.html document. check-in: 0b012929c4 user: drh tags: branch-3.8.8 | |
Changes
Changes to pages/queryplanner.in.
193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 |
</p>
<h3>1.4 Multiple Result Rows</h3>
<p>
In the previous query the fruit='Peach' constraint narrowed the result
down to a single row. But the same technique works even if multiple
rows are obtained. Suppose we looked up the price of Oranges instead
Peaches:
</p>
<tcl>
code {SELECT price FROM fruitsforsale WHERE fruit='Orange'}
figure 6 #fig6 idx1lu2.gif {Indexed Lookup For The Price Of Oranges}
</tcl>
|
| |
193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 |
</p>
<h3>1.4 Multiple Result Rows</h3>
<p>
In the previous query the fruit='Peach' constraint narrowed the result
down to a single row. But the same technique works even if multiple
rows are obtained. Suppose we looked up the price of Oranges instead of
Peaches:
</p>
<tcl>
code {SELECT price FROM fruitsforsale WHERE fruit='Orange'}
figure 6 #fig6 idx1lu2.gif {Indexed Lookup For The Price Of Oranges}
</tcl>
|