mirror of
https://github.com/sqlite/sqlite.git
synced 2025-12-24 14:17:58 +03:00
Comment changes only (CVS 165)
FossilOrigin-Name: 97339efdf3f3b02a6a4fe57d2cb01d19cec3c749
This commit is contained in:
14
manifest
14
manifest
@@ -1,5 +1,5 @@
|
||||
C Version\s1.0.15\s(CVS\s488)
|
||||
D 2000-10-23T13:20:00
|
||||
C Comment\schanges\sonly\s(CVS\s165)
|
||||
D 2000-11-28T20:46:39
|
||||
F COPYRIGHT 74a8a6531a42e124df07ab5599aad63870fa0bd4
|
||||
F Makefile.in 0b1fdafa55e1bf4d3a4f5213544130e66ef32052
|
||||
F README 51f6a4e7408b34afa5bc1c0485f61b6a4efb6958
|
||||
@@ -65,7 +65,7 @@ F tool/renumberOps.awk 6d067177ad5f8d711b79577b462da9b3634bd0a9
|
||||
F www/arch.fig 4f246003b7da23bd63b8b0af0618afb4ee3055c8
|
||||
F www/arch.png 8dae0766d42ed3de9ed013c1341a5792bcf633e6
|
||||
F www/arch.tcl a40380c1fe0080c43e6cc5c20ed70731511b06be
|
||||
F www/c_interface.tcl 5e15e610397b50a9c2a9b2d1d96ec9c846638c07
|
||||
F www/c_interface.tcl 11be2d5826eb7d6efd629751d3b483c1ed78ba14
|
||||
F www/changes.tcl c31acb39bd4e961e966ac05347a3bbffa56c576d
|
||||
F www/crosscompile.tcl bee79c34f6c3f162ec1c6f5294e79f73651d27ee
|
||||
F www/fileformat.tcl cfb7fba80b7275555281ba2f256c00734bcdd1c9
|
||||
@@ -75,8 +75,8 @@ F www/mingw.tcl fc5f4ba9d336b6e8c97347cc6496d6162461ef60
|
||||
F www/opcode.tcl cb3a1abf8b7b9be9f3a228d097d6bf8b742c2b6f
|
||||
F www/sqlite.tcl cb0d23d8f061a80543928755ec7775da6e4f362f
|
||||
F www/tclsqlite.tcl 06f81c401f79a04f2c5ebfb97e7c176225c0aef2
|
||||
F www/vdbe.tcl bcbfc33bcdd0ebad95eab31286adb9e1bc289520
|
||||
P 356cdd64860b714f52529159fada799dca7bb1c0
|
||||
R 74743bda8c8d42a04097be9627f279df
|
||||
F www/vdbe.tcl 0c8aaa529dd216ccbf7daaabd80985e413d5f9ad
|
||||
P d2ad3d2b4ee868621fb1155c64216536d576e456
|
||||
R 83fb4b0a2d996778108e66a5fdc62b84
|
||||
U drh
|
||||
Z dc6feacf6ee70c341a007315b3df6654
|
||||
Z ab74421a3e62e0f3d766c4c0780c1caf
|
||||
|
||||
@@ -1 +1 @@
|
||||
d2ad3d2b4ee868621fb1155c64216536d576e456
|
||||
97339efdf3f3b02a6a4fe57d2cb01d19cec3c749
|
||||
@@ -1,7 +1,7 @@
|
||||
#
|
||||
# Run this Tcl script to generate the sqlite.html file.
|
||||
#
|
||||
set rcsid {$Id: c_interface.tcl,v 1.12 2000/10/23 13:16:33 drh Exp $}
|
||||
set rcsid {$Id: c_interface.tcl,v 1.13 2000/11/28 20:46:39 drh Exp $}
|
||||
|
||||
puts {<html>
|
||||
<head>
|
||||
@@ -458,7 +458,7 @@ meaning of single-quote within a string literal.
|
||||
</p>
|
||||
|
||||
<p>Consider an example. Suppose you are trying to insert a string
|
||||
values into a database table where the string value was obtained from
|
||||
value into a database table where the string value was obtained from
|
||||
user input. Suppose the string to be inserted is stored in a variable
|
||||
named zString. The code to do the insertion might look like this:</p>
|
||||
|
||||
|
||||
12
www/vdbe.tcl
12
www/vdbe.tcl
@@ -1,7 +1,7 @@
|
||||
#
|
||||
# Run this Tcl script to generate the vdbe.html file.
|
||||
#
|
||||
set rcsid {$Id: vdbe.tcl,v 1.5 2000/07/30 20:04:43 drh Exp $}
|
||||
set rcsid {$Id: vdbe.tcl,v 1.6 2000/11/28 20:46:41 drh Exp $}
|
||||
|
||||
puts {<html>
|
||||
<head>
|
||||
@@ -220,7 +220,7 @@ cursor to the "examp" file.</p>
|
||||
preprocessor macro, then
|
||||
there is a special SQL comment that will cause the
|
||||
the VDBE to traces the execution of programs.
|
||||
Though this features was originally intended for testing
|
||||
Though this feature was originally intended for testing
|
||||
and debugging, it might also be useful in learning about
|
||||
how the VDBE operates.
|
||||
Use the "<tt>--vdbe-trace-on--</tt>" comment to
|
||||
@@ -306,7 +306,7 @@ int Callback(void *pUserData, int nColumn, char *azData[], char *azColumnName[])
|
||||
|
||||
<p>The SQLite library supplies the VDBE with a pointer to the callback function
|
||||
and the <b>pUserData</b> pointer. (Both the callback and the user data were
|
||||
originally passed in as argument to the <b>sqlite_exec()</b> API function.)
|
||||
originally passed in as arguments to the <b>sqlite_exec()</b> API function.)
|
||||
The job of the VDBE is to
|
||||
come up with values for <b>nColumn</b>, <b>azData[]</b>,
|
||||
and <b>azColumnName[]</b>.
|
||||
@@ -769,7 +769,7 @@ a small percentage of the rows end up in the result. This can
|
||||
take a long time on a big table. To speed things up, SQLite
|
||||
can use an index.</p>
|
||||
|
||||
<p>An GDBM file associates a key with some data. For a SQLite
|
||||
<p>A GDBM file associates a key with some data. For a SQLite
|
||||
table, the GDBM file is set up so that the key is a integer
|
||||
and the data is the information for one row of the table.
|
||||
Indices in SQLite reverse this arrangement. The GDBM key
|
||||
@@ -1172,7 +1172,7 @@ with that key is brought into focus. A new bucket is created with
|
||||
the key if one did not previously exist. Once the bucket is in
|
||||
focus, the memory locations of the bucket are used to accumulate
|
||||
the values of the various aggregate functions. After the query
|
||||
loop terminates, the each bucket is visited once to generate a
|
||||
loop terminates, each bucket is visited once to generate a
|
||||
single row of the results.</p>
|
||||
|
||||
<p>An example will help to clarify this concept. Consider the
|
||||
@@ -1476,7 +1476,7 @@ VDBE halts.</p>
|
||||
All this code does is make an entry in the temporary table for each
|
||||
row of the examp2 table. The key for each temporary table entry
|
||||
is the "three" column of examp2 and the data
|
||||
entries is an empty string since it is never used.</p>
|
||||
is an empty string since it is never used.</p>
|
||||
|
||||
<p>The outer SELECT is implemented by instructions 8 through 19. In
|
||||
particular, the WHERE clause containing the IN operator is implemented
|
||||
|
||||
Reference in New Issue
Block a user