Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix typos in documentation. (CVS 2399) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
aee888ca58a7d059ff3ccb26bf092455 |
User & Date: | drh 2005-03-19 03:41:58.000 |
Context
2005-03-19
| ||
14:45 | Preparations for the release of version 3.2.0. (CVS 2400) (check-in: 90a00e9066 user: drh tags: trunk) | |
03:41 | Fix typos in documentation. (CVS 2399) (check-in: aee888ca58 user: drh tags: trunk) | |
01:41 | Updates to comments and documentation. No changes to code. (CVS 2398) (check-in: e53c77268c user: drh tags: trunk) | |
Changes
Changes to www/different.tcl.
|
| | | 1 2 3 4 5 6 7 8 | set rcsid {$Id: different.tcl,v 1.4 2005/03/19 03:41:58 drh Exp $} source common.tcl header {Distinctive Features Of SQLite} puts { <p> This page highlights some of the characteristics of SQLite that are unusual and which make SQLite different from many other SQL database engines. |
︙ | ︙ | |||
135 136 137 138 139 140 141 | database run faster, since there is less information to move to and from disk. And, the use of variable-length records makes it possible for SQLite to employ manifest typing instead of static typing. } feature readable {Readable source code} { The source code to SQLite is designed to be readable and accessible to | | | 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 | database run faster, since there is less information to move to and from disk. And, the use of variable-length records makes it possible for SQLite to employ manifest typing instead of static typing. } feature readable {Readable source code} { The source code to SQLite is designed to be readable and accessible to the average programmer. All procedures and data structures and many automatic variables are carefully commented with useful information about what they do. Boilerplate commenting is omitted. } feature vdbe {SQL statements compile into virtual machine code} { Every SQL database engine compiles each SQL statement into some kind of internal data structure which is then used to carry out the work of the |
︙ | ︙ | |||
158 159 160 161 162 163 164 | The use of a virtual machine in SQLite has been a great benefit to library's development. The virtual machine provides a crisp, well-defined junction between the front-end of SQLite (the part that parses SQL statements and generates virtual machine code) and the back-end (the part that executes the virtual machine code and computes a result.) The virtual machine allows the developers to see clearly and in an easily readable form what SQLite is trying to do with each statement | | | 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 | The use of a virtual machine in SQLite has been a great benefit to library's development. The virtual machine provides a crisp, well-defined junction between the front-end of SQLite (the part that parses SQL statements and generates virtual machine code) and the back-end (the part that executes the virtual machine code and computes a result.) The virtual machine allows the developers to see clearly and in an easily readable form what SQLite is trying to do with each statement it compiles, which is a tremendous help in debugging. Depending on how it is compiled, SQLite also has the capability of tracing the execution of the virtual machine - printing each virtual machine instruction and its result as it executes. } #feature binding {Tight bindings to dynamic languages} { # Because it is embedded, SQLite can have a much tighter and more natural |
︙ | ︙ |
Changes to www/whentouse.tcl.
1 2 3 | # # Run this TCL script to generate HTML for the goals.html file. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # 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: |
︙ | ︙ | |||
31 32 33 34 35 36 37 | Simplicity in a database engine can be either a strength or a weakness, depending on what you are trying to do. In order to achieve simplicity, SQLite has had to sacrifice other characteristics that some people find useful, such as high concurrency, fine-grained access control, a rich set of built-in functions, stored procedures, esoteric SQL language features, XML and/or Java extensions, tera- or peta-byte scalability, and so forth. If you need some of these | | | 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 | Simplicity in a database engine can be either a strength or a weakness, depending on what you are trying to do. In order to achieve simplicity, SQLite has had to sacrifice other characteristics that some people find useful, such as high concurrency, fine-grained access control, a rich set of built-in functions, stored procedures, esoteric SQL language features, XML and/or Java extensions, tera- or peta-byte scalability, and so forth. If you need some of these features and do not mind the added complexity that they bring, then SQLite is probably not the database for you. SQLite is not intended to be an enterprise database engine. It not designed to compete with Oracle or PostgreSQL. </p> <p> The basic rule of thumb for when it is appropriate to use SQLite is |
︙ | ︙ |