Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo on the compile.html page. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
5c613c450ac263f9331df7bb526ca934 |
| User & Date: | drh 2017-04-11 23:14:24 |
Context
|
2017-05-05
| ||
| 12:55 | Import the faster-than-filesystem document from trunk. check-in: 488af3774f user: drh tags: branch-3.18 | |
|
2017-04-12
| ||
| 20:00 | Update fts5 documentation to reflect new column filter capability. check-in: 27ba2d2d59 user: dan tags: trunk | |
|
2017-04-11
| ||
| 23:14 | Fix a typo on the compile.html page. check-in: 5c613c450a user: drh tags: trunk | |
| 19:19 | Fix typos in the howtocorrupt.html document. check-in: 20b925f012 user: drh tags: trunk | |
Changes
Changes to pages/compile.in.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
<p>The following compile-time options are recommended for applications that are able to use them, in order to minimized the number of CPU cycles and the bytes of memory used by SQLite. Not all of these compile-time options are usable by every application. For example, the SQLITE_THREADSAFE=0 option is only usable by applications that never access SQLite from more than one thread at a time. And the SQLITE_OMIT_PROGESS_CALLBACK option is only usable by applications that doe not use the [sqlite3_progress_handler()] interface. And so forth. <p>It is impossible to test every possible combination of compile-time options for SQLite. But the following set of compile-time options is one configuration that is always fully tested. <ol> |
| |
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 |
<p>The following compile-time options are recommended for applications that
are able to use them, in order to minimized the number of CPU cycles and
the bytes of memory used by SQLite.
Not all of these compile-time options are usable by every application.
For example, the SQLITE_THREADSAFE=0 option is only usable by applications
that never access SQLite from more than one thread at a time. And the
SQLITE_OMIT_PROGRESS_CALLBACK option is only usable by applications that
doe not use the [sqlite3_progress_handler()] interface. And so forth.
<p>It is impossible to test every possible combination of compile-time
options for SQLite. But the following set of compile-time options is
one configuration that is always fully tested.
<ol>
|