Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typo in documentation. (CVS 2597) |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: | 32efcd24612908516fb5bc58ab3fe4790586a220 |
| User & Date: | drh 2005-08-16 14:44:49 |
Context
|
2005-08-18
| ||
| 18:15 | Comment fixes. No changes to the underlying code. (CVS 2598) check-in: b865e243 user: drh tags: trunk | |
|
2005-08-16
| ||
| 14:44 | Fix typo in documentation. (CVS 2597) check-in: 32efcd24 user: drh tags: trunk | |
| 11:11 | Null-terminate the strings array passed to Tcl_GetIndexFromObj. Bug reported on the mailing list. (CVS 2596) check-in: 3a7918a6 user: drh tags: trunk | |
Changes
Changes to www/whentouse.tcl.
1
2
3
4
5
6
7
8
9
10
11
..
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
#
# Run this TCL script to generate HTML for the goals.html file.
#
set rcsid {$Id: whentouse.tcl,v 1.5 2005/03/19 03:41:58 drh Exp $}
source common.tcl
header {Appropriate Uses For SQLite}
puts {
<p>
SQLite is different from most other SQL database engines in that its
primary design goal is to be simple:
................................................................................
<p>
The basic rule of thumb for when it is appropriate to use SQLite is
this: Use SQLite in situations where simplicity of administration,
implementation, and maintenance are more important than the countless
complex features that enterprise database engines provide.
As it turns out, situations where simplicity is the better choice
are more common that many people realize.
</p>
<h2>Situations Where SQLite Works Well</h2>
<ul>
<li><p><b>Websites</b></p>
|
|
|
|
1
2
3
4
5
6
7
8
9
10
11
..
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
#
# Run this TCL script to generate HTML for the goals.html file.
#
set rcsid {$Id: whentouse.tcl,v 1.6 2005/08/16 14:44:49 drh Exp $}
source common.tcl
header {Appropriate Uses For SQLite}
puts {
<p>
SQLite is different from most other SQL database engines in that its
primary design goal is to be simple:
................................................................................
<p>
The basic rule of thumb for when it is appropriate to use SQLite is
this: Use SQLite in situations where simplicity of administration,
implementation, and maintenance are more important than the countless
complex features that enterprise database engines provide.
As it turns out, situations where simplicity is the better choice
are more common than many people realize.
</p>
<h2>Situations Where SQLite Works Well</h2>
<ul>
<li><p><b>Websites</b></p>
|