Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Updates to the topical documentation index. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
19359f2dd79a5aa5568a8d5d7ce9505b |
User & Date: | drh 2014-08-15 17:32:13.768 |
Context
2014-08-15
| ||
19:06 | Version 3.8.6 (check-in: e477e238b6 user: drh tags: trunk, release, version-3.8.6) | |
17:32 | Updates to the topical documentation index. (check-in: 19359f2dd7 user: drh tags: trunk) | |
15:48 | Update the "Appropriate Uses" page and the "Documentation" index. Fix the size information in "Distinctive Features". (check-in: a6e3e556b4 user: drh tags: trunk) | |
Changes
Changes to pages/docs.in.
︙ | ︙ | |||
105 106 107 108 109 110 111 | doc {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. } | < > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | | | | < | | < < < | | < > | > | < < < | < > | < | < < | 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 228 229 230 231 232 233 234 235 236 | doc {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. } heading {SQLite Features and Extensions} { Pages describing specific features or extension modules of SQLite. } doc {8+3 Filenames} {shortnames.html} { How to make SQLite work on filesystems that only support 8+3 filenames. } doc {Autoincrement} {autoinc.html} { A description of the AUTOINCREMENT keyword in SQLite, what it does, why it is sometimes useful, and why it should be avoided if not strictly necessary. } doc {Backup API} {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 {Command-Line Shell} {cli.html} { Notes on using the "sqlite3.exe" command-line interface that can be used to create, modify, and query arbitrary SQLite database files. } doc {Error and Warning Log} {errlog.html} { SQLite supports an "error and warning log" design to capture information about suspicious and/or error events during operation. Embedded applications are encouraged to enable the error and warning log to help with debugging application problems that arise in the field. This document explains how to do that. } doc {Foreign Key Support} {foreignkeys.html} { This document describes the support for foreign key constraints introduced in version 3.6.19. } doc {Full Text Search} {fts3.html} { A description of the SQLite Full Text Search (FTS3) extension. } doc {Internal versus External Blob Storage} {intern-v-extern-blob.html} { Should you store large BLOBs directly in the database, or store them in files and just record the filename in the database? This document seeks to shed light on that question. } doc {Limits In SQLite} {limits.html} { This document describes limitations of SQLite (the maximum length of a string or blob, the maximum size of a database, the maximum number of tables in a database, etc.) and how these limits can be altered at compile-time and run-time. } doc {Memory-Mapped I/O} {mmap.html} { SQLite supports memory-mapped I/O. Learn how to enable memory-mapped I/O and about the various advantages and disadvantages to using memory-mapped I/O in this document. } doc {Multi-threaded Programs and SQLite} {threadsafe.html} { SQLite is safe to use in multi-threaded programs. This document provides the details and hints on how to maximize performance. } doc {Null Handling} {nulls.html} { Different SQL database engines handle NULLs in different ways. The SQL standards are ambiguous. This (circa 2003) document describes how SQLite handles NULLs in comparison with other SQL database engines. } doc {Partial Indexes} {partialindex.html} { A partial index is an index that only covers a subset of the rows in a table. Learn how to use partial indexes in SQLite from this document. } doc {R-Trees} {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 geospatial systems. } doc {Run-Time Loadable Extensions} {loadext.html} { A general overview on how run-time loadable extensions work, how they are compiled, and how developers can create their own run-time loadable extensions for SQLite. } doc {Shared 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 {URI Filenames} {uri.html} { The names of database files can be specified using either an ordinary filename or a URI. Using URI filenames provides additional capabilities, as this document describes. } doc {WITHOUT ROWID Tables} {withoutrowid.html} { The WITHOUT ROWID optimization is a option that can sometimes result in smaller and faster databases. } doc {Write-Ahead Log (WAL) Mode} {wal.html} { Transaction control using a write-ahead log offers more concurrency and is often faster than the default rollback transactions. This document explains how to use WAL mode for improved performance. } heading {Advocacy} { Documents that strive to encourage the use of SQLite. } doc {SQLite As An Application File Format} {appfileformat.html} { This article advocates using SQLite as an application file format in place of XML or JSON or a "pile-of-file". } doc {Well Known Users} {famous.html} { This page lists a small subset of the many thousands of devices and application programs that make use of SQLite. } heading {SQLite Technical/Design Documentation} { These documents are oriented toward describing the internal implementation details and operation of SQLite. } 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. |
︙ | ︙ | |||
218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 | how to port SQLite to new platforms. } 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. } | > > > > > > > > > > < > > > > > > > > > > | > | < < | | < | < > | | > > > | > > > > | > > < < | | > > | 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 | how to port SQLite to new platforms. } 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 {Isolation In SQLite} {isolation.html} { When we say that SQLite transactions are "serializable" what exactly does that mean? How and when are changes made visible within the same database connection and to other database connections? } doc {Overview Of The Optimizer} {optoverview.html} { A quick overview of the various query optimizations that are attempted by the SQLite code generator. } doc {The Next-Generation Query Planner} {queryplanner-ng.html} { Additional information about the SQLite query planner, and in particular the redesign of the query planner that occurred for version 3.8.0. } 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 {Virtual Filesystem} {vfs.html} { The "VFS" object is the interface between the SQLite core and the underlying operating system. Learn more about how the VFS object works and how to create new VFS objects from this article. } doc {Virtual Tables} {vtab.html} { This article describes the virtual table mechanism and API in SQLite and how it can be used to add new capabilities to the core SQLite library. } doc {SQLite File Format} {fileformat2.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 {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. } doc {Private Branches} {privatebranch.html} { This document suggests procedures for maintaining a private branch or fork of SQLite and keeping that branch or fork in sync with the public SQLite source tree. } heading {Obsolete Documents} { The following documents are no longer current and are retained for historical reference only. These documents generally pertain to out-of-date, obsolete, and/or deprecated features and extensions. } 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. <i>NB: This extension is deprecated. [WAL mode] is recommended as a replacement.</i> } |
︙ | ︙ |