database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2025-07-29 08:01:23 +03:00
Code Activity

Update documentation for the 2.2.0 release. (CVS 335)

Browse Source 
FossilOrigin-Name: 14392258c5b6385091be8d684e3ea6841941b483
This commit is contained in:
drh
2001-12-22 19:27:39 +00:00
parent 8aff10153e
commit e7ec22019d
10 changed files with 252 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
www/index.tcl
View File

@ -1,7 +1,7 @@
#
# Run this TCL script to generate HTML for the index.html file.
#
set rcsid {$Id: index.tcl,v 1.49 2001/11/24 13:23:05 drh Exp $}
set rcsid {$Id: index.tcl,v 1.50 2001/12/22 19:27:41 drh Exp $}
puts {<html>
<head><title>SQLite: An SQL Database Engine In A C Library</title></head>
@ -66,38 +66,15 @@ The latest source code is
<a href="download.html">available for download</a>.
There are currently no known memory leaks or bugs
in the library.
SQLite 2.1.0 is currently being used in several mission-critical
applications.
SQLite 2.1.7 is currently being used in several mission-critical
applications. SQLite 2.2.0 is in beta-test.
</p>
<p>
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 | sqlite2.0 old.db | sqlite2.1 new.db
</pre></blockquote>
<p>
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.
Whenever either of the first two digits in the version number
for SQLite change, it means that the underlying file format
has changed. See <a href="formatchng.html">formatchng.html</a>
for additional information.
</p>
<h2>Documentation</h2>