System.Data.SQLite
Check-in [006a35fb5e]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Pickup the 'vtab.html' doc fix from upstream.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 006a35fb5e2a258451c0df653aa2795b64d38588
User & Date: mistachkin 2016-08-09 00:20:07
Context
2016-08-25
01:14
Add a couple more 'successful' exit codes for the Microsoft Visual C++ Redistributable for Visual Studio. Pursuant to [86d8e9b4d0]. check-in: 33a2920cbe user: mistachkin tags: trunk
2016-08-09
00:20
Pickup the 'vtab.html' doc fix from upstream. check-in: 006a35fb5e user: mistachkin tags: trunk
00:02
Pickup the SQLite core library 3.14 doc changes from upstream. check-in: 70455e449b user: mistachkin tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to Doc/Special/Core/vtab.html.

   871    871   or in a USING or ON clause that is of the form
   872    872   
   873    873   <blockquote>
   874    874        column  OP  EXPR
   875    875   </blockquote>
   876    876   
   877    877   <p>Where "column" is a column in the virtual table, OP is an operator 
   878         -like "=" or "<", and EXPR is an arbitrary expression. So, for example,
          878  +like "=" or "&lt;", and EXPR is an arbitrary expression. So, for example,
   879    879   if the WHERE clause contained a term like this:
   880    880   
   881    881   <blockquote><pre>
   882    882        a = 5
   883    883   </pre></blockquote>
   884    884   
   885    885   <p>Then one of the constraints would be on the "a" column with 
................................................................................
   887    887   literal representation of the WHERE clause. The query optimizer might
   888    888   make transformations to the 
   889    889   WHERE clause in order to extract as many constraints 
   890    890   as it can. So, for example, if the WHERE clause contained something 
   891    891   like this:
   892    892   
   893    893   <blockquote><pre>
   894         -     x BETWEEN 10 AND 100 AND 999>y
          894  +     x BETWEEN 10 AND 100 AND 999&gt;y
   895    895   </pre></blockquote>
   896    896   
   897    897   <p>The query optimizer might translate this into three separate constraints:
   898    898   
   899    899   <blockquote><pre>
   900         -     x >= 10
   901         -     x <= 100
   902         -     y < 999
          900  +     x &gt;= 10
          901  +     x &lt;= 100
          902  +     y &lt; 999
   903    903   </pre></blockquote>
   904    904   
   905    905   <p>For each constraint, the aConstraint[].iColumn field indicates which 
   906    906   column appears on the left-hand side of the constraint.
   907    907   The first column of the virtual table is column 0. 
   908    908   The rowid of the virtual table is column -1. 
   909    909   The aConstraint[].op field indicates which operator is used.