/ Check-in [4f4ac422]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Version 2.1.0 prerelease (CVS 309)
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:4f4ac42214610d900a5d6db63a511d9e7b22f0f9
User & Date: drh 2001-11-12 12:43:22
Context
2001-11-12
13:10
Fix to the SUBSTR() function and to the bigrow test. (CVS 310) check-in: 8437076c user: drh tags: trunk
12:43
Version 2.1.0 prerelease (CVS 309) check-in: 4f4ac422 user: drh tags: trunk
2001-11-10
13:51
Comment changes (CVS 308) check-in: 2d2ad264 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/index.tcl.

1
2
3
4
5
6
7
8
9
10
11
..
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
..
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77



78
79

80
81
82
83
84
85
86
87
88
89
90







91
92
93
94
95
96
97
#
# 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 $}

puts {<html>
<head><title>SQLite: An SQL Database Engine In A C Library</title></head>
<body bgcolor=white>
<h1 align=center>SQLite: An SQL Database Engine In A C Library</h1>
<p align=center>}
puts "This page was last modified on [lrange $rcsid 3 4] GMT<br>"
................................................................................
puts {<h2>Features</h2>

<p><ul>
<li>Implements a large subset of SQL92.</li>
<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><a href="speed.html">Four times faster</a> than PostgreSQL.
    Twice as fast as SQLite 1.0.</li>
<li>Very simple 
<a href="c_interface.html">C/C++ interface</a> requires the use of only
three functions and one opaque structure.</li>
<li><a href="tclsqlite.html">TCL bindings</a> included.</li>
<li>A TCL-based test suite provides near 100% code coverage.</li>
................................................................................
puts {<h2>Current Status</h2>

<p>A <a href="changes.html">change history</a> is available online.
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 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:

</p>

<blockquote><pre>
echo .dump | sqlite1.0 old.db | sqlite2.0 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>.







</p>

<h2>Documentation</h2>

<p>The following documentation is currently available:</p>

<p><ul>



|







 







|







 







|




|
|
|
|
>
>
>
|
<
>



|



|
|
|
|
>
>
>
>
>
>
>







1
2
3
4
5
6
7
8
9
10
11
..
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
..
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81

82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
#
# Run this TCL script to generate HTML for the index.html file.
#
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>
<body bgcolor=white>
<h1 align=center>SQLite: An SQL Database Engine In A C Library</h1>
<p align=center>}
puts "This page was last modified on [lrange $rcsid 3 4] GMT<br>"
................................................................................
puts {<h2>Features</h2>

<p><ul>
<li>Implements a large subset of SQL92.</li>
<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 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="c_interface.html">C/C++ interface</a> requires the use of only
three functions and one opaque structure.</li>
<li><a href="tclsqlite.html">TCL bindings</a> included.</li>
<li>A TCL-based test suite provides near 100% code coverage.</li>
................................................................................
puts {<h2>Current Status</h2>

<p>A <a href="changes.html">change history</a> is available online.
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.
</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.
</p>

<h2>Documentation</h2>

<p>The following documentation is currently available:</p>

<p><ul>