Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix typos the source to webpages html files. (CVS 703) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
61bb3af7405aa7b54f3e5519537ea483 |
User & Date: | drh 2002-08-06 12:05:00.000 |
Context
2002-08-11
| ||
20:10 | Fix for ticket #9: Add the ability to read little-endian database files from a big-endian machine and vice versa. (CVS 704) (check-in: ce4b943bf6 user: drh tags: trunk) | |
2002-08-06
| ||
12:05 | Fix typos the source to webpages html files. (CVS 703) (check-in: 61bb3af740 user: drh tags: trunk) | |
2002-08-04
| ||
00:52 | Fix for ticket #131: When a SELECT contains a GROUP BY clause it cannot use an index for sorting. It has to sort as a separate operation after the GROUP BY is complete. (CVS 702) (check-in: 18745c67ac user: drh tags: trunk) | |
Changes
Changes to www/arch.tcl.
1 2 3 | # # Run this Tcl script to generate the sqlite.html file. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this Tcl script to generate the sqlite.html file. # set rcsid {$Id: arch.tcl,v 1.8 2002/08/06 12:05:00 drh Exp $} puts {<html> <head> <title>Architecture of SQLite</title> </head> <body bgcolor=white> <h1 align=center> |
︙ | ︙ | |||
131 132 133 134 135 136 137 | <b>btree.h</b>. </p> <h2>Page Cache</h2> <p>The B-tree module requests information from the disk in 1024 byte chunks. The page cache is reponsible for reading, writing, and | | | | 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 | <b>btree.h</b>. </p> <h2>Page Cache</h2> <p>The B-tree module requests information from the disk in 1024 byte chunks. The page cache is reponsible for reading, writing, and caching these chunks. The page cache also provides the rollback and atomic commit abstraction and takes care of reader/writer locking of the database file. The B-tree driver requests particular pages from the page cache and notifies the page cache when it wants to modify pages or commit or rollback changes and the page cache handles all the messy details of making sure the requests are handled quickly, safely, and efficiently.</p> <p>The code to implement the page cache is contained in the single C source file <b>pager.c</b>. The interface to the page cache subsystem is defined by the header file <b>pager.h</b>. </p> <h2>OS Interface</h2> <p> In order to provide portability between POSIX and Win32 operating systems, SQLite uses an abstraction layer to interface with the operating system. The <b>os.c</b> file contains about 20 routines used for opening and closing files, deleting files, creating and deleting locks on files, flushing the disk cache, and so forth. Each of these functions contains two implementations separated by #ifdefs: one for POSIX and the other for Win32. The interface to the OS abstraction layer is defined by the <b>os.h</b> header file. </p> |
︙ | ︙ |
Changes to www/speed.tcl.
1 2 3 | # # Run this Tcl script to generate the speed.html file. # | | | 1 2 3 4 5 6 7 8 9 10 11 | # # Run this Tcl script to generate the speed.html file. # set rcsid {$Id: speed.tcl,v 1.7 2002/08/06 12:05:01 drh Exp $ } puts {<html> <head> <title>Database Speed Comparison: SQLite versus PostgreSQL</title> </head> <body bgcolor=white> <h1 align=center> |
︙ | ︙ | |||
180 181 182 183 184 185 186 | <tr><td>SQLite 2.4:</td><td align="right"> 6.137</td></tr> <tr><td>SQLite 2.4 (nosync):</td><td align="right"> 6.112</td></tr> </table> <p> This set of 100 queries uses string comparisons instead of numerical comparisions. As a result, the speed of SQLite is | | | 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 | <tr><td>SQLite 2.4:</td><td align="right"> 6.137</td></tr> <tr><td>SQLite 2.4 (nosync):</td><td align="right"> 6.112</td></tr> </table> <p> This set of 100 queries uses string comparisons instead of numerical comparisions. As a result, the speed of SQLite is compariable to or better then PostgreSQL and MySQL. </p> <h2>Test 5: Creating an index</h2> <blockquote> CREATE INDEX i2a ON t2(a);<br>CREATE INDEX i2b ON t2(b); </blockquote><table border=0 cellpadding=0 cellspacing=0> <tr><td>PostgreSQL:</td><td align="right"> 0.510</td></tr> |
︙ | ︙ |