Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Properly escape "<" and ">" characters in the vtab.html document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
03ec352945a78731564c00481a614ad3 |
| User & Date: | drh 2016-08-09 00:13:32 |
Context
|
2016-08-09
| ||
| 17:38 | Improvements to the PRAGMA secure_delete documentation. check-in: ec87587f77 user: drh tags: trunk | |
| 00:13 | Properly escape "<" and ">" characters in the vtab.html document. check-in: 03ec352945 user: drh tags: trunk | |
|
2016-08-08
| ||
| 22:40 | Increase the fontsize on the "pi". check-in: 5933ebb467 user: drh tags: trunk | |
Changes
Changes to pages/vtab.in.
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
...
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
|
or in a USING or ON clause that is of the form
<blockquote>
column OP EXPR
</blockquote>
<p>Where "column" is a column in the virtual table, OP is an operator
like "=" or "<", and EXPR is an arbitrary expression. So, for example,
if the WHERE clause contained a term like this:
<blockquote><pre>
a = 5
</pre></blockquote>
<p>Then one of the constraints would be on the "a" column with
................................................................................
literal representation of the WHERE clause. The query optimizer might
make transformations to the
WHERE clause in order to extract as many constraints
as it can. So, for example, if the WHERE clause contained something
like this:
<blockquote><pre>
x BETWEEN 10 AND 100 AND 999>y
</pre></blockquote>
<p>The query optimizer might translate this into three separate constraints:
<blockquote><pre>
x >= 10
x <= 100
y < 999
</pre></blockquote>
<p>For each constraint, the aConstraint[].iColumn field indicates which
column appears on the left-hand side of the constraint.
The first column of the virtual table is column 0.
The rowid of the virtual table is column -1.
The aConstraint[].op field indicates which operator is used.
|
|
|
|
|
|
|
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
...
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
|
or in a USING or ON clause that is of the form
<blockquote>
column OP EXPR
</blockquote>
<p>Where "column" is a column in the virtual table, OP is an operator
like "=" or "<", and EXPR is an arbitrary expression. So, for example,
if the WHERE clause contained a term like this:
<blockquote><pre>
a = 5
</pre></blockquote>
<p>Then one of the constraints would be on the "a" column with
................................................................................
literal representation of the WHERE clause. The query optimizer might
make transformations to the
WHERE clause in order to extract as many constraints
as it can. So, for example, if the WHERE clause contained something
like this:
<blockquote><pre>
x BETWEEN 10 AND 100 AND 999>y
</pre></blockquote>
<p>The query optimizer might translate this into three separate constraints:
<blockquote><pre>
x >= 10
x <= 100
y < 999
</pre></blockquote>
<p>For each constraint, the aConstraint[].iColumn field indicates which
column appears on the left-hand side of the constraint.
The first column of the virtual table is column 0.
The rowid of the virtual table is column -1.
The aConstraint[].op field indicates which operator is used.
|