-C Comment\schanges\s(CVS\s308)
-D 2001-11-10T13:51:08
+C Version\s2.1.0\sprerelease\s(CVS\s309)
+D 2001-11-12T12:43:22
F Makefile.in 6801df952cb1df64aa32e4de85fed24511d28efd
F Makefile.template 1fdb891f14083ee0b63cf7282f91529634438e7a
F README a4c0ba11354ef6ba0776b400d057c59da47a4cc0
F www/crosscompile.tcl c99efacb3aefaa550c6e80d91b240f55eb9fd33e
F www/download.tcl 3e51c9ff1326b0a182846134987301310dff7d60
F www/dynload.tcl 02eb8273aa78cfa9070dd4501dca937fb22b466c
-F www/index.tcl b9d166d09fa4237d31d78be49f2b8b205e6e7678
+F www/index.tcl fa0ee4b5343fd216ee5db0285501e45484189484
F www/lang.tcl f0e953bfeaaba4c33117ec4bca639dd71ba0e13e
F www/mingw.tcl fc5f4ba9d336b6e8c97347cc6496d6162461ef60
F www/opcode.tcl 7989ed328316454c7030dcdb60f09ae1e017286d
F www/sqlite.tcl 6a21242a272e9c0939a04419a51c3d50cae33e3e
F www/tclsqlite.tcl 13d50723f583888fc80ae1a38247c0ab415066fa
F www/vdbe.tcl bb7d620995f0a987293e9d4fb6185a3b077e9b44
-P 6e7e7dbf8e93d00eced88404aed792fcf9e75b7d
-R 18e925419ed8c85ff1b4931f4627f2c0
+P 2d2ad264aad6fbdcef586e73d750e3fde842252f
+R 16c00ab1c6dd8026c015350394df2b49
U drh
-Z a3df24ec6e762840d7c455a8f753602e
+Z a0e64c7188bd5b5811337fabdc6b35c2
#
# Run this TCL script to generate HTML for the index.html file.
#
-set rcsid {$Id: index.tcl,v 1.46 2001/11/01 14:41:34 drh Exp $}
+set rcsid {$Id: index.tcl,v 1.47 2001/11/12 12:43:22 drh Exp $}
puts {<html>
<head><title>SQLite: An SQL Database Engine In A C Library</title></head>
<li>A complete database (with multiple tables and indices) is
stored in a single disk file.</li>
<li>Atomic commit and rollback protect data integrity.</li>
-<li>Small memory footprint: about 12000 lines of C code.</li>
+<li>Small memory footprint: about 14000 lines of C code.</li>
<li><a href="speed.html">Four times faster</a> than PostgreSQL.
Twice as fast as SQLite 1.0.</li>
<li>Very simple
<a href="download.html">available for download</a>.
There are currently no known memory leaks or bugs
in the library.
-SQLite is currently being used in several mission-critical
+SQLite 2.1.0 is currently being used in several mission-critical
applications.
</p>
<p>
-The file format used changed beginning with version 2.0.0. Version 1.0.X
-of SQLite used GDBM as its database backend. Version 2.0.0 and later
-use a built-in implementation of B-trees. If you have older 1.0 databases
-you will need to convert them before they can be read using a 2.0
-release of SQLite. The following command will convert a legacy
-database into the new 2.0 format:
+The SQLite file format changed beginning with version 2.1.0. The
+same basic B-Tree structure from version 2.0.0 is used but the
+details of indices where altered to permit better query optimization
+and the B-Tree table entry headers where changed slightly to expand the
+maximum amount of data on a row from 64KB to 16MB.
+The file format changes
+between 2.0.8 and 2.1.0 are small but they still require that you
+dump and restore your old databases. The following command should
+suffice:
</p>
<blockquote><pre>
-echo .dump | sqlite1.0 old.db | sqlite2.0 new.db
+echo .dump | sqlite2.0 old.db | sqlite2.1 new.db
</pre></blockquote>
<p>
-The above command assumes that <b>sqlite1.0</b> is sqlite version 1.0
-and <b>sqlite2.0</b> is sqlite version 2.0. The old database is stored
-in a directory named <b>old.db</b> and the new database is created in
-the file <b>new.db</b>.
+The above command assumes that <b>sqlite2.0</b> is any of the
+2.0 series of sqlite command-line tools and <b>sqlite2.1</b> is the
+new version 2.1 sqlite command-line tool.
+</p>
+
+<p>
+Version 1.0.X of SQLite used GDBM as its backend and so its
+file format is complete incompatable with all version 2.0 and
+version 2.1 SQLite releases. Legacy databases must be dumped to
+ASCII and reloaded, as shown above, before they can be used with
+newer versions of SQLite.
</p>
<h2>Documentation</h2>
projects / thirdparty / sqlite.git / commitdiff
