Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add some more links to the docs.html page. Group the links under headings to try to make it easier to find pages. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
379b9f7acd2f4b058a8ac41c28d1e5ab |
User & Date: | dan 2009-05-22 11:45:53.000 |
Context
2009-05-24
| ||
11:01 | Documentation fix: the sqlite3_create_function() interfaces return SQLITE_MISUSE of the number of arguments parameter is out of range. (check-in: d06c1c4318 user: drh tags: trunk) | |
2009-05-22
| ||
11:45 | Add some more links to the docs.html page. Group the links under headings to try to make it easier to find pages. (check-in: 379b9f7acd user: dan tags: trunk) | |
2009-05-21
| ||
11:36 | Minor edits of fileformat.html. (check-in: e216c81d99 user: dan tags: trunk) | |
Changes
Changes to pages/docs.in.
︙ | ︙ | |||
9 10 11 12 13 14 15 16 17 18 19 20 21 | regsub -all { +} $name {\ } name hd_puts "<a href=\"$url\">$name</a></td>" hd_puts {<td width="10"></td>} hd_puts {<td valign="top" align="left">} hd_resolve $desc hd_puts {</td></tr>} } doc {Appropriate Uses For SQLite} {whentouse.html} { This document describes situations where SQLite is an appropriate database engine to use versus situations where a client/server database engine might be a better choice. } | > > > > > > > > > < > > > > > > > > > > > > > > > > > > > > > > | > > > > > > > > > > | > > > > > > > | > > > > | | > > > | | > > | | < < | < < < < < < < | < < < | < | < < > > | < < < < | | > > > | | | | > > > > > > | | < > > | < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < > > > > > > | | | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 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 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 | regsub -all { +} $name {\ } name hd_puts "<a href=\"$url\">$name</a></td>" hd_puts {<td width="10"></td>} hd_puts {<td valign="top" align="left">} hd_resolve $desc hd_puts {</td></tr>} } proc heading {text {caption {}}} { hd_puts {<tr><td colspan=3 style="padding: 3ex 0 0 0">} hd_puts "<b>$text</b>" if {$caption ne ""} { hd_puts {<tr><td colspan=3 style="padding: 0 10ex">} hd_puts $caption } } doc {Appropriate Uses For SQLite} {whentouse.html} { This document describes situations where SQLite is an appropriate database engine to use versus situations where a client/server database engine might be a better choice. } doc {Distinctive Features} {different.html} { This document enumerates and describes some of the features of SQLite that make it different from other SQL database engines. } doc {How SQLite Is Tested} {testing.html} { The reliability and robustness of SQLite is achieved in large part by thorough and careful testing. This document identifies the many tests that occur before very release of SQLite. } doc {Copyright} {copyright.html} { SQLite is in the public domain. This document describes what that means and the implications for contributors. } doc {Frequently Asked Questions} {faq.html} { The title of the document says all... } heading {SQLite Programming Interfaces} { Documentation describing the APIs used to program SQLite, and the SQL dialect that it interprets. } doc {SQLite In 5 Minutes Or Less} {quickstart.html} { A very quick introduction to programming with SQLite. } doc {Introduction to the C/C++ API } {cintro.html} { This document introduces the C/C++ API. Users should read this document before the C/C++ API Reference Guide linked below. } doc {C/C++ API Reference} {c3ref/intro.html} { This document describes each API function separately. } doc {Tcl API} {tclsqlite.html} { A description of the TCL interface bindings for SQLite. } doc {SQL Syntax} {lang.html} { This document describes the SQL language that is understood by SQLite. } doc {Pragma commands} {pragma.html} { This document describes SQLite performance tuning options and other special purpose database commands. } doc {Version 3 DataTypes } {datatype3.html} { SQLite version 3 introduces the concept of manifest typing, where the type of a value is associated with the value itself, not the column that it is stored in. This page describes data typing for SQLite version 3 in further detail. } doc {Null Handling} {nulls.html} { Different SQL database engines handle NULLs in different ways. The SQL standards are ambiguous. This document describes how SQLite handles NULLs in comparison with other SQL database engines. } doc {Unsupported SQL} {omitted.html} { This page describes features of SQL that SQLite does not support. } heading {SQLite Features and Extensions} { Pages describing specific features or extension modules of SQLite. } doc {Using The Online Backup Interface} {backup.html} { The [sqlite3_backup_init | online-backup interface] can be used to copy content from a disk file into an in-memory database or vice versa and it can make a hot backup of a live database. This application note gives examples of how. } doc {Sharing Cache Mode} {sharedcache.html} { Version 3.3.0 and later supports the ability for two or more database connections to share the same page and schema cache. This feature is useful for certain specialized applications. } doc {Unlock Notify} {unlock_notify.html} { The "unlock notify" feature can be used in conjunction with shared cache mode to more efficiently manage resource conflict (database table locks). } doc {Asynchronous IO Mode} {asyncvfs.html} { This page describes the asynchronous IO extension developed alongside SQLite. Using asynchronous IO can cause SQLite to appear more responsive by delegating database writes to a background thread. } doc {Virtual R-Tree Tables} {rtree.html} { A description of the SQLite R-Tree extension. An R-Tree is a specialized data structure that supports fast multi-dimensional range queries often used in geo-spatial systems. } heading {Upgrading SQLite, Backwards Compatibility} doc {Moving From SQLite 3.5 to 3.6} {35to36.html} { A document describing the differences between SQLite version 3.5.9 and 3.6.0. } doc {Moving From SQLite 3.4 to 3.5} {34to35.html} { A document describing the differences between SQLite version 3.4.2 and 3.5.0. } doc {Release History} {changes.html} { A chronology of SQLite releases going back to version 1.0.0 } doc {Backwards Compatibility} {formatchng.html} { This document details all of the incompatible changes to the SQLite file format that have occurred since version 1.0.0. } heading {SQLite Technical/Design Documentation} doc {Temporary Files Used By SQLite} {tempfiles.html} { SQLite can potentially use many different temporary files when processing certain SQL statements. This document describes the many kinds of temporary files that SQLite uses and offers suggestions for avoiding them on systems where creating a temporary file is an expensive operation. } doc {How SQLite Implements Atomic Commit} {atomiccommit.html} { A description of the logic within SQLite that implements transactions with atomic commit, even in the face of power failures. } doc {Locking And Concurrency<br>In SQLite Version 3} {lockingv3.html} { A description of how the new locking code in version 3 increases concurrency and decreases the problem of writer starvation. } doc {Overview Of The Optimizer} {optoverview.html} { A quick overview of the various query optimizations that are attempted by the SQLite code generator. } doc {Architecture} {arch.html} { An architectural overview of the SQLite library, useful for those who want to hack the code. } doc {VDBE Opcodes} {opcode.html} { This document is an automatically generated description of the various opcodes that the VDBE understands. Programmers can use this document as a reference to better understand the output of EXPLAIN listings from SQLite. } doc {SQLite File Format} {fileformat.html} { A description of the format used for SQLite database and journal files, and other details required to create software to read and write SQLite databases without using SQLite. } doc {Compilation Options} {compile.html} { This document describes the compile time options that may be set to modify the default behavior of the library or omit optional features in order to reduce binary size. } heading {Old Documents} { These documents either pertain to SQLite version 2 or were written during the transition period between versions 2 and 3. They are no longer strictly applicable to recent versions of SQLite, but the information found within may still be useful. } doc {Version 2 C/C++ API} {c_interface.html} { A description of the C/C++ interface bindings for SQLite through version 2.8 } doc {Version 2 DataTypes } {datatypes.html} { A description of how SQLite version 2 handles SQL datatypes. Short summary: Everything is a string. } doc {VDBE Tutorial} {vdbe.html} { The VDBE is the subsystem within SQLite that does the actual work of executing SQL statements. This page describes the principles of operation for the VDBE in SQLite version 2.7. This is essential reading for anyone who want to modify the SQLite sources. } doc {SQLite Version 3} {version3.html} { A summary of of the changes between SQLite version 2.8 and SQLite version 3.0. } doc {Version 3 C/C++ API} {capi3.html} { A summary of of the API related changes between SQLite version 2.8 and SQLite version 3.0. } doc {Speed Comparison} {speed.html} { The speed of version 2.7.6 of SQLite is compared against PostgreSQL and MySQL. } </tcl> </table> |