-C Version\s3.0.0\s(ALPHA)\s(CVS\s1619)
-D 2004-06-18T12:29:23
+C Fix\stypos\sin\sdocumentation.\s\sFix\spublish.sh\sso\sthat\sit\scorrectly\sbuilds\sthe\nZIP\sarchive\sof\spreprocesses\ssource\scode.\s(CVS\s1620)
+D 2004-06-18T15:13:48
F Makefile.in 5125bd6b92fca76275a6fc6c6ff425484b8cec0a
F Makefile.linux-gcc a9e5a0d309fa7c38e7c14d3ecf7690879d3a5457
F README f1de682fbbd94899d50aca13d387d1b3fd3be2dd
F ltmain.sh f6b283068efa69f06eb8aa1fe4bddfdbdeb35826
F main.mk 6004a81e05581a6b51e4f37a62ed45db089c47cf
F mkdll.sh 68d34a961a1fdfa15ef27fc4f4740be583112124
-F publish.sh e772c09c4fb72f2323a1fb522259640e52040b15
+F publish.sh 5bc5e493fa1773a3c0d9712182de0f5abd494903
F spec.template a38492f1c1dd349fc24cb0565e08afc53045304b
F sqlite.1 83f4a9d37bdf2b7ef079a82d54eaf2e3509ee6ea
F sqlite.def fc4f5734786fe4743cfe2aa98eb2da4b089edb5f
F www/support.tcl 1801397edd271cc39a2aadd54e701184b5181248
F www/tclsqlite.tcl 19191cf2a1010eaeff74c51d83fd5f5a4d899075
F www/vdbe.tcl 59288db1ac5c0616296b26dce071c36cb611dfe9
-F www/version3.tcl f9a4c1a12864e129f6717d22313be01d5657e3aa
+F www/version3.tcl af528563442e3039928f9018327a18157e53a44f
F www/whentouse.tcl a8335bce47cc2fddb07f19052cb0cb4d9129a8e4
-P 9e0e530f10bf70996471650496173dee074c2732
-R e652117e65d118a6c36b9df849e95e4a
+P 8b409aaae42cc36d96536531da41f05bd0cdd29c
+R 06705682ecc02465bea573b58c16c9a3
U drh
-Z a6276db799a30487f4c5e98319787ced
+Z 797649997def2a974837df56baf38e92
-8b409aaae42cc36d96536531da41f05bd0cdd29c
\ No newline at end of file
+fee0c5e308c3de1937185e2060c8757e605ab3a2
\ No newline at end of file
# under Linux
#
make target_source
-rm sqlite_source.zip
cd tsrc
-zip ../sqlite_source.zip *
+zip ../doc/sqlite-source-$VERSW.zip *
rm shell.c
TCLDIR=/home/drh/tcltk/8.2linux
TCLSTUBLIB=$TCLDIR/libtclstub8.2g.a
<p>
The format used by SQLite database files has been completely revised.
The old version 2.1 format and the new 3.0 format are incompatible with
-one another. Version 2.8 of SQLite will not read and version 3.0 database
+one another. Version 2.8 of SQLite will not read a version 3.0 database
files and version 3.0 of SQLite will not read a version 2.8 database file.
</p>
</pre></blockquote>
<p>
-The new database file format uses B+Trees for tables. In a B+Tree, all
+The new database file format uses B+trees for tables. In a B+tree, all
data is stored in the leaves of the tree instead of in both the leaves and
-the intermediate branch nodes. The use of B+Trees for tables allows for
-better scalability and the storage larger data fields without the use of
-overflow pages. Traditional B-Trees are still used for indices.</p>
+the intermediate branch nodes. The use of B+trees for tables allows for
+better scalability and the storage of larger data fields without the use of
+overflow pages. Traditional B-trees are still used for indices.</p>
<p>
The new file format also supports variable pages sizes between 512 and
<p>
The new file format omits unused fields from its disk images. For example,
-indices use only the key part of a B-Tree record and not the data. So
+indices use only the key part of a B-tree record and not the data. So
for indices, the field that records the length of the data is omitted.
Integer values such as the length of key and data are stored using
a variable-length encoding so that only one or two bytes are required to
</p>
<p>
-Details of the low-level B-Tree format used in SQLite version 3.0 can
+Details of the low-level B-tree format used in SQLite version 3.0 can
be found in header comments to the
<a href="http://www.sqlite.org/cvstrac/getfile/sqlite/src/btree.c">btree.c</a>
source file.
</p>
}
-footer {$Id: version3.tcl,v 1.1 2004/06/17 19:04:17 drh Exp $}
+footer {$Id: version3.tcl,v 1.2 2004/06/18 15:13:48 drh Exp $}