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 | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: | 61bb3af7405aa7b54f3e5519537ea483 |
User & Date: | drh 2002-08-06 12:05:00 |
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: ce4b943b user: drh tags: trunk | |
2002-08-06
| ||
12:05 | Fix typos the source to webpages html files. (CVS 703) check-in: 61bb3af7 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: 18745c67 user: drh tags: trunk | |
Changes
Changes to www/arch.tcl.
1 1 # 2 2 # Run this Tcl script to generate the sqlite.html file. 3 3 # 4 -set rcsid {$Id: arch.tcl,v 1.7 2001/11/24 13:23:05 drh Exp $} 4 +set rcsid {$Id: arch.tcl,v 1.8 2002/08/06 12:05:00 drh Exp $} 5 5 6 6 puts {<html> 7 7 <head> 8 8 <title>Architecture of SQLite</title> 9 9 </head> 10 10 <body bgcolor=white> 11 11 <h1 align=center> ................................................................................ 131 131 <b>btree.h</b>. 132 132 </p> 133 133 134 134 <h2>Page Cache</h2> 135 135 136 136 <p>The B-tree module requests information from the disk in 1024 byte 137 137 chunks. The page cache is reponsible for reading, writing, and 138 -caching these chunks at the behest of the B-tree module. 138 +caching these chunks. 139 139 The page cache also provides the rollback and atomic commit abstraction 140 140 and takes care of reader/writer locking of the database file. The 141 141 B-tree driver requests particular pages from the page cache and notifies 142 142 the page cache when it wants to modify pages or commit or rollback 143 143 changes and the page cache handles all the messy details of making sure 144 144 the requests are handled quickly, safely, and efficiently.</p> 145 145 ................................................................................ 148 148 is defined by the header file <b>pager.h</b>. 149 149 </p> 150 150 151 151 <h2>OS Interface</h2> 152 152 153 153 <p> 154 154 In order to provide portability between POSIX and Win32 operating systems, 155 -SQLite uses an abstraction layer to interace with the operating system. 155 +SQLite uses an abstraction layer to interface with the operating system. 156 156 The <b>os.c</b> file contains about 20 routines used for opening and 157 157 closing files, deleting files, creating and deleting locks on files, 158 158 flushing the disk cache, and so forth. Each of these functions contains 159 159 two implementations separated by #ifdefs: one for POSIX and the other 160 160 for Win32. The interface to the OS abstraction layer is defined by 161 161 the <b>os.h</b> header file. 162 162 </p>
Changes to www/speed.tcl.
1 1 # 2 2 # Run this Tcl script to generate the speed.html file. 3 3 # 4 -set rcsid {$Id: speed.tcl,v 1.6 2002/03/11 02:06:14 drh Exp $ } 4 +set rcsid {$Id: speed.tcl,v 1.7 2002/08/06 12:05:01 drh Exp $ } 5 5 6 6 puts {<html> 7 7 <head> 8 8 <title>Database Speed Comparison: SQLite versus PostgreSQL</title> 9 9 </head> 10 10 <body bgcolor=white> 11 11 <h1 align=center> ................................................................................ 180 180 <tr><td>SQLite 2.4:</td><td align="right"> 6.137</td></tr> 181 181 <tr><td>SQLite 2.4 (nosync):</td><td align="right"> 6.112</td></tr> 182 182 </table> 183 183 184 184 <p> 185 185 This set of 100 queries uses string comparisons instead of 186 186 numerical comparisions. As a result, the speed of SQLite is 187 -compariable to are better then PostgreSQL and MySQL. 187 +compariable to or better then PostgreSQL and MySQL. 188 188 </p> 189 189 190 190 <h2>Test 5: Creating an index</h2> 191 191 <blockquote> 192 192 CREATE INDEX i2a ON t2(a);<br>CREATE INDEX i2b ON t2(b); 193 193 </blockquote><table border=0 cellpadding=0 cellspacing=0> 194 194 <tr><td>PostgreSQL:</td><td align="right"> 0.510</td></tr>