Fix typos in comments in test code.
(Oops. This check-in also picked up some unrelated changes to documentation.) (CVS 2175) FossilOrigin-Name: 586acc85b170f84d6e0dbd2e293da19551242f5a
This commit is contained in:
drh
parent
7465a80899
commit
c89b91beee
24
manifest
24
manifest
@ -1,5 +1,5 @@
|
||||
C Fix\sa\stypo\sin\sa\scomment.\s\sNo\scode\schanges.\s\sTicket\s#1052.\s(CVS\s2174)
|
||||
D 2005-01-03T01:28:51
|
||||
C Fix\stypos\sin\scomments\sin\stest\scode.\r\n(Oops.\s\sThis\scheck-in\salso\spicked\sup\ssome\sunrelated\r\nchanges\sto\sdocumentation.)\s(CVS\s2175)
|
||||
D 2005-01-03T01:33:00
|
||||
F Makefile.in 02a184d734a2b4bbbc1ecc2e3ef504fcb13de069
|
||||
F Makefile.linux-gcc a9e5a0d309fa7c38e7c14d3ecf7690879d3a5457
|
||||
F README a01693e454a00cc117967e3f9fdab2d4d52e9bc1
|
||||
@ -84,7 +84,7 @@ F src/vdbeaux.c a7c4c90786e2633b38f2d89f3dc49aed747454e4
|
||||
F src/vdbemem.c 5876c8abf4374fef671f4fd8dc333ef3fc95a2f0
|
||||
F src/where.c 4eb44da11a733b8cb5fe251827fbdf3f1f3efb1c
|
||||
F tclinstaller.tcl 36478c3bbfc5b93ceac42d94e3c736937b808432
|
||||
F test/all.test 929bfa932b55e75c96fe2203f7650ba451c1862c
|
||||
F test/all.test 853e7030ab20a602eeb7a155124ae37f24ff9ffd
|
||||
F test/alter.test 95c57a4f461fa81293e0dccef7f83889aadb169a
|
||||
F test/attach.test f39069efd4394422798f249df9a31489aa941ee1
|
||||
F test/attach2.test eeb987770f4dbe68bd29afdbc2e8cff0142e6eb5
|
||||
@ -146,7 +146,7 @@ F test/lock.test 32fe28e5030f25f23bcf6beef440675b0d848413
|
||||
F test/lock2.test 59c3dd7d9b24d1bf7ec91b2d1541c37e97939d5f
|
||||
F test/lock3.test 615111293cf32aa2ed16d01c6611737651c96fb9
|
||||
F test/main.test 5f9deae11b93336da1ccc5f91cf8be075c91ddf1
|
||||
F test/malloc.test b4674cbb5a72b113eedaaf64fcd5c062e9957ded
|
||||
F test/malloc.test c20b7208d8d123e1185b3cbe54c6fdde3c060c55
|
||||
F test/memdb.test 532aac7128a3da494cddc4461d76c6e3988f771b
|
||||
F test/memleak.test f1fa233f8295dd1d955a00d5e5ee857850f27f29
|
||||
F test/minmax.test e7048476940df0af11d0f2cf687572f557cd0b29
|
||||
@ -182,7 +182,7 @@ F test/table.test b8b0bee2ac2f3d36a674bc68344c1bdd80e99a18
|
||||
F test/tableapi.test b21ab097e87a5484bb61029e69e1a4e5c5e65ede
|
||||
F test/tclsqlite.test 8b9dae3b68a899e5cbaebe6bb51cfc27f2503c6d
|
||||
F test/temptable.test 63a16e3ad19adf073cfbcdf7624c92ac5236522c
|
||||
F test/tester.tcl e7ebedf60c8ebbb0a9af4950981babfbb80cc9a7
|
||||
F test/tester.tcl 071ad70ee2c1d3393e20baabaac03f07e7925cfe
|
||||
F test/thread1.test 776c9e459b75ba905193b351926ac4019b049f35
|
||||
F test/threadtest1.c 6029d9c5567db28e6dc908a0c63099c3ba6c383b
|
||||
F test/threadtest2.c 97a830d53c24c42290501fdfba4a6e5bdd34748b
|
||||
@ -206,7 +206,7 @@ F test/where.test cbe22fb2e241a896fa5dcc732fda512be011ba52
|
||||
F tool/diffdb.c 7524b1b5df217c20cd0431f6789851a4e0cb191b
|
||||
F tool/lemon.c 250b30bcf3f1f422a2cad24b1597314777058a4b
|
||||
F tool/lempar.c 1e61d2b6cb9d8affa264a13336bc0c088498caa4
|
||||
F tool/memleak.awk b744b6109566206c746d826f6ecdba34662216bc
|
||||
F tool/memleak.awk 4e7690a51bf3ed757e611273d43fe3f65b510133
|
||||
F tool/memleak2.awk 9cc20c8e8f3c675efac71ea0721ee6874a1566e8
|
||||
F tool/memleak3.tcl 336eb50b0849dbf99b1d5462d9c37291b01b2b43
|
||||
F tool/mkkeywordhash.c 408dccad57ed50dc67a9a1ee7fd258e0f0a07bd2
|
||||
@ -229,7 +229,7 @@ F www/arch2b.fig d22a2c9642d584b89d4088b1e51e2bb0f7c04bed
|
||||
F www/audit.tcl 90e09d580f79c7efec0c7d6f447b7ec5c2dce5c0
|
||||
F www/autoinc.tcl b357f5ba954b046ee35392ce0f884a2fcfcdea06
|
||||
F www/c_interface.tcl b51b08591554c16a0c3ef718364a508ac25abc7e
|
||||
F www/capi3.tcl 5c1cb163f4d2a54e2d0e22dcc399dd71245c8b89
|
||||
F www/capi3.tcl 9676103393dbf1c313b5618c9da59033f82cd924
|
||||
F www/capi3ref.tcl c5a3ae75fc3505c034f3c4bbb62ab94cf359ac39
|
||||
F www/changes.tcl f2b34859843d9f06a0611eb6d44af767891b09ef
|
||||
F www/common.tcl de758130d54d95d151ea0d17a2ae5b92e1bb01de
|
||||
@ -240,7 +240,7 @@ F www/copyright-release.pdf cfca3558fc97095e57c6117d08f1f5b80d95125a
|
||||
F www/copyright.tcl 82c9670c7ddb0311912ab7fe24703f33c531066c
|
||||
F www/datatype3.tcl 1d14f70ab73075556b95e76a5c13e5b03f7f6c47
|
||||
F www/datatypes.tcl 7c786d2e8ff434346764534ec015966d17efce60
|
||||
F www/docs.tcl 95ec3aac01fe0ff514509a6478b239973eb10c8e
|
||||
F www/docs.tcl 09e5eccffad783fe65fac87772f5265e9bb64abe
|
||||
F www/download.tcl 4d8ff8c882063b864d004c524e4e7456858f09a5
|
||||
F www/dynload.tcl 02eb8273aa78cfa9070dd4501dca937fb22b466c
|
||||
F www/faq.tcl abe360e630d8134bc6242c5e3664969c397eac6e
|
||||
@ -262,8 +262,8 @@ F www/support.tcl 3955da0fd82be68cc5c83d347c05095e80967051
|
||||
F www/tclsqlite.tcl e73f8f8e5f20e8277619433f7970060ab01088fc
|
||||
F www/vdbe.tcl 095f106d93875c94b47367384ebc870517431618
|
||||
F www/version3.tcl 092a01f5ef430d2c4acc0ae558d74c4bb89638a0
|
||||
F www/whentouse.tcl fdacb0ba2d39831e8a6240d05a490026ad4c4e4c
|
||||
P 4165217e5114f5377f0823c63ff2aba879927ce7
|
||||
R 4256e9938158c4257c938a7c19c2fe04
|
||||
F www/whentouse.tcl c3b50d3ac31c54be2a1af9b488a89d22f1e6e746
|
||||
P 9fb1402f0835b214c9174866653e95416b32f860
|
||||
R 1b8ce1bf62029a52efe7aa66908b9708
|
||||
U drh
|
||||
Z 8379ed370e2d153591bc88062fba4b49
|
||||
Z d8b73f30bf9c57bb9c0d09a4ed6f32df
|
||||
|
||||
@ -1 +1 @@
|
||||
9fb1402f0835b214c9174866653e95416b32f860
|
||||
586acc85b170f84d6e0dbd2e293da19551242f5a
|
||||
@ -10,7 +10,7 @@
|
||||
#***********************************************************************
|
||||
# This file runs all tests.
|
||||
#
|
||||
# $Id: all.test,v 1.22 2004/08/31 13:45:12 drh Exp $
|
||||
# $Id: all.test,v 1.23 2005/01/03 01:33:00 drh Exp $
|
||||
|
||||
set testdir [file dirname $argv0]
|
||||
source $testdir/tester.tcl
|
||||
@ -81,7 +81,7 @@ for {set Counter 0} {$Counter<$COUNT && $nErr==0} {incr Counter} {
|
||||
}
|
||||
|
||||
# Do one last test to look for a memory leak in the library. This will
|
||||
# only work if SQLite is compiled with the -DMEMORY_DEBUG=1 flag.
|
||||
# only work if SQLite is compiled with the -DSQLITE_DEBUG=1 flag.
|
||||
#
|
||||
if {$LeakList!=""} {
|
||||
puts -nonewline memory-leak-test...
|
||||
|
||||
@ -9,12 +9,12 @@
|
||||
#
|
||||
#***********************************************************************
|
||||
# This file attempts to check the library in an out-of-memory situation.
|
||||
# When compiled with -DMEMORY_DEBUG=1, the SQLite library accepts a special
|
||||
# When compiled with -DSQLITE_DEBUG=1, the SQLite library accepts a special
|
||||
# command (sqlite_malloc_fail N) which causes the N-th malloc to fail. This
|
||||
# special feature is used to see what happens in the library if a malloc
|
||||
# were to really fail due to an out-of-memory situation.
|
||||
#
|
||||
# $Id: malloc.test,v 1.11 2004/11/20 19:18:01 drh Exp $
|
||||
# $Id: malloc.test,v 1.12 2005/01/03 01:33:00 drh Exp $
|
||||
|
||||
set testdir [file dirname $argv0]
|
||||
source $testdir/tester.tcl
|
||||
@ -22,7 +22,7 @@ source $testdir/tester.tcl
|
||||
# Only run these tests if memory debugging is turned on.
|
||||
#
|
||||
if {[info command sqlite_malloc_stat]==""} {
|
||||
puts "Skipping malloc tests: not compiled with -DMEMORY_DEBUG..."
|
||||
puts "Skipping malloc tests: not compiled with -DSQLITE_DEBUG..."
|
||||
finish_test
|
||||
return
|
||||
}
|
||||
|
||||
@ -11,7 +11,7 @@
|
||||
# This file implements some common TCL routines used for regression
|
||||
# testing the SQLite library
|
||||
#
|
||||
# $Id: tester.tcl,v 1.42 2004/11/14 04:04:18 drh Exp $
|
||||
# $Id: tester.tcl,v 1.43 2005/01/03 01:33:00 drh Exp $
|
||||
|
||||
# Make sure tclsqlite3 was compiled correctly. Abort now with an
|
||||
# error message if not.
|
||||
@ -117,7 +117,7 @@ proc do_test {name cmd expected} {
|
||||
}
|
||||
|
||||
# The procedure uses the special "sqlite_malloc_stat" command
|
||||
# (which is only available if SQLite is compiled with -DMEMORY_DEBUG=1)
|
||||
# (which is only available if SQLite is compiled with -DSQLITE_DEBUG=1)
|
||||
# to see how many malloc()s have not been free()ed. The number
|
||||
# of surplus malloc()s is stored in the global variable $::Leak.
|
||||
# If the value in $::Leak grows, it may mean there is a memory leak
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
#
|
||||
# This script looks for memory leaks by analyzing the output of "sqlite"
|
||||
# when compiled with the MEMORY_DEBUG=2 option.
|
||||
# when compiled with the SQLITE_DEBUG=2 option.
|
||||
#
|
||||
/[0-9]+ malloc / {
|
||||
mem[$6] = $0
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
set rcsid {$Id: capi3.tcl,v 1.6 2004/06/30 13:28:33 danielk1977 Exp $}
|
||||
set rcsid {$Id: capi3.tcl,v 1.7 2005/01/03 01:33:00 drh Exp $}
|
||||
source common.tcl
|
||||
header {C/C++ Interface For SQLite Version 3}
|
||||
puts {
|
||||
@ -234,10 +234,10 @@ is executed using:
|
||||
</pre></blockquote>
|
||||
|
||||
<p>
|
||||
The sqlite3_step() routine return SQLITE3_ROW if it is returning a single
|
||||
row of the result set, or SQLITE3_DONE if execution has completed, either
|
||||
normally or due to an error. It might also return SQLITE3_BUSY if it is
|
||||
unable to open the database file. If the return value is SQLITE3_ROW, then
|
||||
The sqlite3_step() routine return SQLITE_ROW if it is returning a single
|
||||
row of the result set, or SQLITE_DONE if execution has completed, either
|
||||
normally or due to an error. It might also return SQLITE_BUSY if it is
|
||||
unable to open the database file. If the return value is SQLITE_ROW, then
|
||||
the following routines can be used to extract information about that row
|
||||
of the result set:
|
||||
</p>
|
||||
@ -339,11 +339,11 @@ User defined functions can be created using the following routine:
|
||||
void (*xStep)(sqlite3_context*,int,sqlite3_value**),
|
||||
void (*xFinal)(sqlite3_context*)
|
||||
);
|
||||
#define SQLITE3_UTF8 1
|
||||
#define SQLITE3_UTF16 2
|
||||
#define SQLITE3_UTF16BE 3
|
||||
#define SQLITE3_UTF16LE 4
|
||||
#define SQLITE3_ANY 5
|
||||
#define SQLITE_UTF8 1
|
||||
#define SQLITE_UTF16 2
|
||||
#define SQLITE_UTF16BE 3
|
||||
#define SQLITE_UTF16LE 4
|
||||
#define SQLITE_ANY 5
|
||||
</pre></blockquote>
|
||||
|
||||
<p>
|
||||
@ -432,8 +432,8 @@ collating sequences:
|
||||
The sqlite3_create_collation() function specifies a collating sequence name
|
||||
and a comparison function to implement that collating sequence. The
|
||||
comparison function is only used for comparing text values. The eTextRep
|
||||
parameter is one of SQLITE3_UTF8, SQLITE3_UTF16LE, SQLITE3_UTF16BE, or
|
||||
SQLITE3_ANY to specify which text representation the comparison function works
|
||||
parameter is one of SQLITE_UTF8, SQLITE_UTF16LE, SQLITE_UTF16BE, or
|
||||
SQLITE_ANY to specify which text representation the comparison function works
|
||||
with. Separate comparison functions can exist for the same collating
|
||||
sequence for each of the UTF-8, UTF-16LE and UTF-16BE text representations.
|
||||
The sqlite3_create_collation16() works like sqlite3_create_collation() except
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
# This script generates the "docs.html" page that describes various
|
||||
# sources of documentation available for SQLite.
|
||||
#
|
||||
set rcsid {$Id: docs.tcl,v 1.8 2004/11/20 06:05:56 danielk1977 Exp $}
|
||||
set rcsid {$Id: docs.tcl,v 1.9 2005/01/03 01:33:00 drh Exp $}
|
||||
source common.tcl
|
||||
header {SQLite Documentation}
|
||||
puts {
|
||||
@ -19,6 +19,12 @@ proc doc {name url desc} {
|
||||
puts {</td></tr>}
|
||||
}
|
||||
|
||||
doc {Appropriate Uses For SQLite} {whentouse.html} {
|
||||
This document describes situations where SQLite is an approriate
|
||||
database engine to use versus situations where a client/server
|
||||
database engine might be a better choice.
|
||||
}
|
||||
|
||||
doc {SQLite In 5 Minutes Or Less} {quickstart.html} {
|
||||
A very quick introduction to programming with SQLite.
|
||||
}
|
||||
@ -59,6 +65,7 @@ doc {Locking And Concurrency<br>In SQLite Version 3} {lockingv3.html} {
|
||||
|
||||
doc {Version 2 DataTypes } {datatypes.html} {
|
||||
A description of how SQLite version 2 handles SQL datatypes.
|
||||
Short summary: Everything is a string.
|
||||
}
|
||||
doc {Version 3 DataTypes } {datatype3.html} {
|
||||
SQLite version 3 introduces the concept of manifest typing, where the
|
||||
|
||||
@ -1,16 +1,9 @@
|
||||
#
|
||||
# Run this TCL script to generate HTML for the goals.html file.
|
||||
#
|
||||
set rcsid {$Id: whentouse.tcl,v 1.2 2004/10/10 17:24:55 drh Exp $}
|
||||
|
||||
puts {<html>
|
||||
<head><title>Appropriate Uses of SQLite</title></head>
|
||||
<body bgcolor=white>
|
||||
<h1 align=center>Appropriate Uses Of SQLite</h1>
|
||||
}
|
||||
puts "<p align=center>
|
||||
(This page was last modified on [lrange $rcsid 3 4] UTC)
|
||||
</p>"
|
||||
set rcsid {$Id: whentouse.tcl,v 1.3 2005/01/03 01:33:00 drh Exp $}
|
||||
source common.tcl
|
||||
header {Appropriate Uses For SQLite}
|
||||
|
||||
puts {
|
||||
<p>
|
||||
@ -67,7 +60,8 @@ medium traffic websites (which is to say, 99.9% of all websites).
|
||||
The amount of web traffic that SQLite can handle depends, of course,
|
||||
on how heavily the website uses its database. Generally
|
||||
speaking, any site that gets fewer than a 100000 hits/day should work
|
||||
fine. The 100000 hits/day figure is a conservative estimate, not a
|
||||
fine with SQLite.
|
||||
The 100000 hits/day figure is a conservative estimate, not a
|
||||
hard upper bound.
|
||||
SQLite has been demonstrated to work with 10 times that amount
|
||||
of traffic.</p>
|
||||
@ -89,7 +83,7 @@ works well as an embedded database in downloadable consumer applications.
|
||||
SQLite has been used with great success as the on-disk file format
|
||||
for desktop applications such as financial analysis tools, CAD
|
||||
packages, record keeping programs, and so forth. The traditional
|
||||
File/Open operation does an sqlite_open() and executes a
|
||||
File/Open operation does an sqlite3_open() and executes a
|
||||
BEGIN TRANSACTION to get exclusive access to the content. File/Save
|
||||
does a COMMIT followed by another BEGIN TRANSACTION. The use
|
||||
of transactions guarantees that updates to the application file are atomic,
|
||||
@ -108,7 +102,8 @@ in surprising little code.
|
||||
<li><p><b>Replacement for <i>ad hoc</i> disk files</b></p>
|
||||
|
||||
<p>Many programs use fopen(), fread(), and fwrite() to create and
|
||||
manage files of data in home-grown formats. SQLite works well as a
|
||||
manage files of data in home-grown formats. SQLite works
|
||||
particularly well as a
|
||||
replacement for these <i>ad hoc</i> data files.</p>
|
||||
</li>
|
||||
|
||||
@ -117,7 +112,7 @@ replacement for these <i>ad hoc</i> data files.</p>
|
||||
<p>
|
||||
For programs that have a lot of data that must be sifted and sorted
|
||||
in diverse ways, it is often easier and quicker to load the data into
|
||||
an in-memory SQLite database and use query with joins and ORDER BY
|
||||
an in-memory SQLite database and use queries with joins and ORDER BY
|
||||
clauses to extract the data in the form and order needed rather than
|
||||
to try to code the same operations manually.
|
||||
Using an SQL database internally in this way also gives the program
|
||||
@ -131,7 +126,7 @@ having to recode every query.
|
||||
<p>
|
||||
Experienced SQL users can employ
|
||||
the command-line <b>sqlite</b> program to analyze miscellaneous
|
||||
datasets. Raw data can be imported using the COPY command, then that
|
||||
datasets. Raw data can be imported from CSV files, then that
|
||||
data can be sliced and diced to generate a myriad of summary
|
||||
reports. Possible uses include website log analysis, sports
|
||||
statistics analysis, compilation of programming metrics, and
|
||||
@ -142,8 +137,8 @@ analysis of experimental results.
|
||||
You can also do the same thing with a enterprise client/server
|
||||
database, of course. The advantages to using SQLite in this situation
|
||||
are that SQLite is much easier to set up and the resulting database
|
||||
is a single file that you can store on a floppy disk or email to
|
||||
a colleague.
|
||||
is a single file that you can store on a floppy disk or flash-memory stick
|
||||
or email to a colleague.
|
||||
</p>
|
||||
</li>
|
||||
|
||||
@ -245,8 +240,8 @@ all other processes are prevented from reading any other part of the
|
||||
database.
|
||||
For many situations, this is not a problem. Each application
|
||||
does its database work quickly and moves on, and no lock lasts for more
|
||||
than a few dozen milliseconds. But there are some problems that require
|
||||
more concurrency, and those problems will need to seek a different
|
||||
than a few dozen milliseconds. But there are some applications that require
|
||||
more concurrency, and those applications may need to seek a different
|
||||
solution.
|
||||
</p>
|
||||
</li>
|
||||
@ -254,13 +249,4 @@ solution.
|
||||
</ul>
|
||||
|
||||
}
|
||||
|
||||
|
||||
puts {
|
||||
<p><hr /></p>
|
||||
<p>
|
||||
<a href="index.html"><img src="/goback.jpg" border=0 />
|
||||
Back to the SQLite home page</a>
|
||||
</p>
|
||||
|
||||
</body></html>}
|
||||
footer $rcsid
|
||||
|
||||
Loading…
Reference in New Issue
Block a user