Documentation Source Text

Check-in [539577139b]
Login

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

Overview
Comment:Fix typos. CVSTrac ticket #2963.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 539577139bc0ad2d5cff5015a07bf20b8817d124
User & Date: drh 2008-02-27 13:07:14
Context
2008-02-27
13:08
Fix another typo. check-in: 45e25daf49 user: drh tags: trunk
13:07
Fix typos. CVSTrac ticket #2963. check-in: 539577139b user: drh tags: trunk
2008-02-26
13:29
Fix typo in the 34to35.html document. check-in: 4b0e57bd4f user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/features.in.



1
2
3
4
5
6
7
..
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58


<h2>About SQLite</h2>

<h3>SQLite Features:</h3>

<p><ul>
<li><a href="transactional.html">Transactions</a>
    are atomic, consistent, isolated, and durable (ACID)
................................................................................

<p><ul>
<li><p><b>Application File Format.</b>
Rather than using fopen() to write XML or some proprietary format into
disk files used by your application, use an SQLite database instead.
You'll avoid having to write and troubleshoot a parser, your data
will be more easily accessible and cross-platform, your updates
will transactional.</p></li>

<li><p><b>Database For Gadgets.</b>
SQLite is popular choice for the database engine in cellphones,
PDAs, MP3 players, set-top boxes, and other electronic gadgets.
SQLite has a small code footprint, makes efficient use of memory,
disk space, and disk bandwidth, is highly reliable, and requires
no maintenance from a Database Adminstrator.</p></li>
>
>







 







|







1
2
3
4
5
6
7
8
9
..
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
<title>SQLite Features</title>

<h2>About SQLite</h2>

<h3>SQLite Features:</h3>

<p><ul>
<li><a href="transactional.html">Transactions</a>
    are atomic, consistent, isolated, and durable (ACID)
................................................................................

<p><ul>
<li><p><b>Application File Format.</b>
Rather than using fopen() to write XML or some proprietary format into
disk files used by your application, use an SQLite database instead.
You'll avoid having to write and troubleshoot a parser, your data
will be more easily accessible and cross-platform, your updates
will be transactional.</p></li>

<li><p><b>Database For Gadgets.</b>
SQLite is popular choice for the database engine in cellphones,
PDAs, MP3 players, set-top boxes, and other electronic gadgets.
SQLite has a small code footprint, makes efficient use of memory,
disk space, and disk bandwidth, is highly reliable, and requires
no maintenance from a Database Adminstrator.</p></li>

Changes to pages/mostdeployed.in.

26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Let us use that number as a proxy for the number of deployed
SQL database engines other than SQLite.  Not every website
runs an SQL database engine, and not ever SQL database engine
runs a website.  Larger websites run multiple
database engines.  But the vast majority of smaller websites
(the long tail) share
a database engine with several other websites,
if they use database engine at all.
And many large SQL database installations have nothing to do with
websites.
So using the number of websites as a surrogate for the number of operational
SQL database engines is a crude approximation, but it is the best
we have so we will go with it.  (Readers are encouraged to submit
better estimates.)</p>








|







26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Let us use that number as a proxy for the number of deployed
SQL database engines other than SQLite.  Not every website
runs an SQL database engine, and not ever SQL database engine
runs a website.  Larger websites run multiple
database engines.  But the vast majority of smaller websites
(the long tail) share
a database engine with several other websites,
if they use a database engine at all.
And many large SQL database installations have nothing to do with
websites.
So using the number of websites as a surrogate for the number of operational
SQL database engines is a crude approximation, but it is the best
we have so we will go with it.  (Readers are encouraged to submit
better estimates.)</p>

Changes to pages/onefile.in.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<title>SQLite: Single File Database</title>

<h2>Single-file Cross-platform Database</h2>

<p>
A database in SQLite is a single disk file.
Furthermore, the file format is cross-platform.
A databae that is created on one machine can be
copied and used on a different machine with
a different architecture.  SQLite databases
are portable across 32-bit and 64-bit machines
and between 
<a href="http://en.wikipedia.org/wiki/Endianness">big-endian</a> and 
<a href="http://en.wikipedia.org/wiki/Endianness">little-endian</a>
architectures.







|







1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<title>SQLite: Single File Database</title>

<h2>Single-file Cross-platform Database</h2>

<p>
A database in SQLite is a single disk file.
Furthermore, the file format is cross-platform.
A database that is created on one machine can be
copied and used on a different machine with
a different architecture.  SQLite databases
are portable across 32-bit and 64-bit machines
and between 
<a href="http://en.wikipedia.org/wiki/Endianness">big-endian</a> and 
<a href="http://en.wikipedia.org/wiki/Endianness">little-endian</a>
architectures.

Changes to pages/selfcontained.in.

47
48
49
50
51
52
53
54
55
"amalgamation" - a single large C source code file.
Projects that want to include SQLite can do so simply
by dropping this one source file (named "sqlite3.c") and
its corresponding header ("sqlite3.h") into their source
tree and compiling it together with the rest of the
code.  SQLite does not link against any external libraries
(other than the C library, as described above) and does
require any special build support.
</p>







|

47
48
49
50
51
52
53
54
55
"amalgamation" - a single large C source code file.
Projects that want to include SQLite can do so simply
by dropping this one source file (named "sqlite3.c") and
its corresponding header ("sqlite3.h") into their source
tree and compiling it together with the rest of the
code.  SQLite does not link against any external libraries
(other than the C library, as described above) and does
not require any special build support.
</p>

Changes to pages/serverless.in.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
..
32
33
34
35
36
37
38
39
40
41
42
<title>SQLite Is Serverless</title>

<h2>SQLite Is Serverless</h2>

<p>
Most SQL database engines are implemented as a separate server process.
Programs that want to access the database communicate with the server
using some kind of interprocess communcation (typically TCP/IP) to send 
requests to the server and to receive back results. 
SQLite does not work this way. 
With SQLite, the process that wants to access the database reads and 
writes directly from the database files on disk. 
There is no intermediary server process.
</p>

................................................................................
And because a server is a single persistent process,
it is able control database access with more precision, 
allowing for finer grain locking and better concurrancy.
</p>

<p>
Most SQL database engines are client/server based. 
Of those that are serverless, SQLite is the only one that 
known to this author that allows multiple applications
to access the same database at the same time. 
</p>







|







 







|



1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
..
32
33
34
35
36
37
38
39
40
41
42
<title>SQLite Is Serverless</title>

<h2>SQLite Is Serverless</h2>

<p>
Most SQL database engines are implemented as a separate server process.
Programs that want to access the database communicate with the server
using some kind of interprocess communication (typically TCP/IP) to send 
requests to the server and to receive back results. 
SQLite does not work this way. 
With SQLite, the process that wants to access the database reads and 
writes directly from the database files on disk. 
There is no intermediary server process.
</p>

................................................................................
And because a server is a single persistent process,
it is able control database access with more precision, 
allowing for finer grain locking and better concurrancy.
</p>

<p>
Most SQL database engines are client/server based. 
Of those that are serverless, SQLite is the only one
known to this author that allows multiple applications
to access the same database at the same time. 
</p>