mirror of
https://github.com/sqlite/sqlite.git
synced 2025-08-01 06:27:03 +03:00
More documentation updates (CVS 295)
FossilOrigin-Name: f65df59e554c281ad1efa830f13f87488eb16845
This commit is contained in:
drh
18
manifest
18
manifest
@ -1,5 +1,5 @@
|
||||
C Make\slemon\s64-bit\sclean\s(CVS\s294)
|
||||
D 2001-10-25T20:37:17
|
||||
C More\sdocumentation\supdates\s(CVS\s295)
|
||||
D 2001-10-31T15:44:47
|
||||
F Makefile.in 6801df952cb1df64aa32e4de85fed24511d28efd
|
||||
F Makefile.template 1fdb891f14083ee0b63cf7282f91529634438e7a
|
||||
F README 93d2977cc5c6595c448de16bdefc312b9d401533
|
||||
@ -101,20 +101,20 @@ F tool/report1.txt 9eae07f26a8fc53889b45fc833a66a33daa22816
|
||||
F www/arch.fig d5f9752a4dbf242e9cfffffd3f5762b6c63b3bcf
|
||||
F www/arch.png 82ef36db1143828a7abc88b1e308a5f55d4336f4
|
||||
F www/arch.tcl 03b521d252575f93b9c52f7c8b0007011512fcfb
|
||||
F www/c_interface.tcl 6c5989670e014de44dce6580cbde0eea965dadbb
|
||||
F www/changes.tcl fdd4f8b474bce2463b876c1bedb68c20bc3f5b34
|
||||
F www/c_interface.tcl d446234c1d3ed747fcefd30e972a19f2b2fc0e05
|
||||
F www/changes.tcl 995d934eb54762d766923241a5a2e6023a0f3c6e
|
||||
F www/crosscompile.tcl c99efacb3aefaa550c6e80d91b240f55eb9fd33e
|
||||
F www/download.tcl 3e51c9ff1326b0a182846134987301310dff7d60
|
||||
F www/dynload.tcl 02eb8273aa78cfa9070dd4501dca937fb22b466c
|
||||
F www/index.tcl 68c815d64b35b2dcc4d4f6845827df71c6869f9f
|
||||
F www/index.tcl 7c7df8d73c751897b643018fd21317269f10e023
|
||||
F www/lang.tcl 1899ec4fb77cd69de335ebd998253de869f34d8e
|
||||
F www/mingw.tcl fc5f4ba9d336b6e8c97347cc6496d6162461ef60
|
||||
F www/opcode.tcl 4365ad9798872491dbd7d3071510ebe461785ac3
|
||||
F www/speed.tcl ab7d6d3bc898472bd94320a5d3c63de928d4804b
|
||||
F www/speed.tcl 212a91d555384e01873160d6a189f1490c791bc2
|
||||
F www/sqlite.tcl 6a21242a272e9c0939a04419a51c3d50cae33e3e
|
||||
F www/tclsqlite.tcl 13d50723f583888fc80ae1a38247c0ab415066fa
|
||||
F www/vdbe.tcl bb7d620995f0a987293e9d4fb6185a3b077e9b44
|
||||
P b0442cb9c64682b6f98bf8f26f50bb54bdfd9013
|
||||
R 32105803ca01e82d865a4315992e9dcb
|
||||
P 475e2fedda2256cc1cfdffa1b12745bc401e552d
|
||||
R b2fc4ff3650cbe526a68ea1cf8e3178b
|
||||
U drh
|
||||
Z 410df64d0289bddfbc85d5b3184781c8
|
||||
Z a9512049e53d528acde7056d6370a7e0
|
||||
|
||||
@ -1 +1 @@
|
||||
475e2fedda2256cc1cfdffa1b12745bc401e552d
|
||||
f65df59e554c281ad1efa830f13f87488eb16845
|
||||
@ -1,7 +1,7 @@
|
||||
#
|
||||
# Run this Tcl script to generate the sqlite.html file.
|
||||
#
|
||||
set rcsid {$Id: c_interface.tcl,v 1.18 2001/10/19 16:44:58 drh Exp $}
|
||||
set rcsid {$Id: c_interface.tcl,v 1.19 2001/10/31 15:44:47 drh Exp $}
|
||||
|
||||
puts {<html>
|
||||
<head>
|
||||
@ -227,7 +227,7 @@ that the database is locked. But the source of the lock is a recursive
|
||||
call to <b>sqlite_exec()</b>. This return can only occur if you attempt
|
||||
to invoke sqlite_exec() from within a callback routine of a query
|
||||
from a prior invocation of sqlite_exec(). Recursive calls to
|
||||
sqlite_exec() are allowed as long as no more they all read-only or do
|
||||
sqlite_exec() are allowed as long as they do
|
||||
not attempt to write the same table.
|
||||
</p></dd>
|
||||
<dt>SQLITE_NOMEM</dt>
|
||||
@ -445,7 +445,7 @@ result[2] = "host"<br>
|
||||
is obtained from malloc(). But the calling function should not try
|
||||
to free this information directly. Instead, pass the complete table
|
||||
to <b>sqlite_free_table()</b> when the table is no longer needed.
|
||||
It is safe to call <b>sqlite_free_table()</b> will a NULL pointer such
|
||||
It is safe to call <b>sqlite_free_table()</b> with a NULL pointer such
|
||||
as would be returned if the result set is empty.</p>
|
||||
|
||||
<p>The <b>sqlite_get_table()</b> routine returns the same integer
|
||||
@ -454,7 +454,7 @@ result code as <b>sqlite_exec()</b>.</p>
|
||||
<h2>Interrupting an SQLite operation</h2>
|
||||
|
||||
<p>The <b>sqlite_interrupt()</b> function can be called from a
|
||||
different thread or from a signal handler to the current database
|
||||
different thread or from a signal handler to cause the current database
|
||||
operation to exit at its first opportunity. When this happens,
|
||||
the <b>sqlite_exec()</b> routine (or the equivalent) that started
|
||||
the database operation will return SQLITE_INTERRUPT.</p>
|
||||
@ -512,7 +512,7 @@ was compiled.</p>
|
||||
|
||||
<p>The <b>sqlite_busy_handler()</b> procedure can be used to register
|
||||
a busy callback with an open SQLite database. The busy callback will
|
||||
be invoked whenever SQLite tries to open a locked that is locked.
|
||||
be invoked whenever SQLite tries to open a file that is locked.
|
||||
The callback will typically do some other useful work, or perhaps sleep,
|
||||
in order to give the lock a chance to clear. If the callback returns
|
||||
non-zero, then SQLite tries again to open the database and the cycle
|
||||
|
||||
@ -17,6 +17,10 @@ proc chng {date desc} {
|
||||
puts "<DD><P><UL>$desc</UL></P></DD>"
|
||||
}
|
||||
|
||||
chng {2001 Oct ?? (2.0.8)} {
|
||||
<li>Documentation updates</li>
|
||||
}
|
||||
|
||||
chng {2001 Oct 21 (2.0.7)} {
|
||||
<li>Any UTF-8 character or ISO8859 character can be used as part of
|
||||
an identifier.</li>
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
#
|
||||
# Run this TCL script to generate HTML for the index.html file.
|
||||
#
|
||||
set rcsid {$Id: index.tcl,v 1.44 2001/10/06 16:33:04 drh Exp $}
|
||||
set rcsid {$Id: index.tcl,v 1.45 2001/10/31 15:44:47 drh Exp $}
|
||||
|
||||
puts {<html>
|
||||
<head><title>SQLite: An SQL Database Engine In A C Library</title></head>
|
||||
@ -107,6 +107,7 @@ the file <b>new.db</b>.
|
||||
|
||||
<p>The SQLite source code is 35% comment. These comments are
|
||||
another important source of information. </p>
|
||||
|
||||
}
|
||||
|
||||
puts {
|
||||
@ -123,6 +124,23 @@ Click to subscribe to sqlite</a>
|
||||
SQLite design issues or for asking questions about SQLite.</p>
|
||||
}
|
||||
|
||||
puts {<h2>Professional Support and Custom Modifications</h2>}
|
||||
|
||||
puts {
|
||||
<p>
|
||||
If you would like professional support for SQLite
|
||||
or if you want custom modifications to SQLite preformed by the
|
||||
original author, these services are available for a modest fee.
|
||||
For additional information contact:</p>
|
||||
|
||||
<blockquote>
|
||||
D. Richard Hipp <br />
|
||||
Hwaci - Applied Software Research <br />
|
||||
704.948.4565 <br />
|
||||
<a href="mailto:drh@hwaci.com">drh@hwaci.com</a>
|
||||
</blockquote>
|
||||
}
|
||||
|
||||
puts {<h2>Building From Source</h2>}
|
||||
|
||||
puts {
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
#
|
||||
# Run this Tcl script to generate the speed.html file.
|
||||
#
|
||||
set rcsid {$Id: speed.tcl,v 1.3 2001/09/28 23:11:24 drh Exp $ }
|
||||
set rcsid {$Id: speed.tcl,v 1.4 2001/10/31 15:44:48 drh Exp $ }
|
||||
|
||||
puts {<html>
|
||||
<head>
|
||||
@ -290,7 +290,7 @@ SQLite 2.0: real 3.12 user 0.02 sys 0.31
|
||||
<p>
|
||||
SQLite 2.0 is much slower at dropping tables. This may be because
|
||||
both SQLite 1.0 and PostgreSQL can drop a table simply by unlinking
|
||||
or renaming a file, since that both use one or more files per table.
|
||||
or renaming a file, since both store database tables in separate files.
|
||||
SQLite 2.0, on the other hand, uses a single file for the entire
|
||||
database, so dropping a table involves moving lots of page of that
|
||||
file to the free-list, which takes time.
|
||||
|
||||
Reference in New Issue
Block a user