Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typos in the custombuild.html document. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
63f32cf18cc74044fc03eafe34800b8a |
| User & Date: | drh 2010-01-15 01:21:01 |
Context
|
2010-01-15
| ||
| 05:16 | Fix another typo in custombuild.html. (check-in: 06a55cbcb5 user: dan tags: trunk) | |
| 01:21 | Fix typos in the custombuild.html document. (check-in: 63f32cf18c user: drh tags: trunk) | |
|
2010-01-14
| ||
| 11:43 | Fix an error in the matchinfo example in fts3.html. (check-in: ceff4c1d37 user: dan tags: trunk) | |
Changes
Changes to pages/custombuild.in.
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
...
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
|
<blockquote><pre> -DSQLITE_THREADSAFE=0 </pre></blockquote> <p>Mutexes are cheap but they are not free, so performance will be better when mutexes are completely disabled. The resulting library footprint will also be a little smaller. Disability the mutexes as compile-time is a recommended optimization for applications were it makes sense.</p> <p>When using SQLite as a shared library, an application can test to see whether or not mutexes have been disabled using the [sqlite3_threadsafe()] API. Applications that link against SQLite at run-time and use SQLite from multiple threads should probably check this API to make sure they did not accidently get linked against a version of ................................................................................ startup.</i></p> <h2>4.0 Adding New Virtual File Systems</h2> <p>Since [version 3.5.0], SQLite has supported an interface called the [sqlite3_vfs | virtual file system] or "VFS". This object is somewhat misnamed since it is really an interface to whole underlying operating system, just the filesystem.</p> <p> One of the interesting features of the VFS interface is that SQLite can support multiple VFSes at the same time. Each [database connection] has to choose a single VFS for its use when the connection is first opened using [sqlite3_open_v2()]. But if a process contains multiple [database connections] each can choose |
|
|
|
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
...
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
|
<blockquote><pre> -DSQLITE_THREADSAFE=0 </pre></blockquote> <p>Mutexes are cheap but they are not free, so performance will be better when mutexes are completely disabled. The resulting library footprint will also be a little smaller. Disabling the mutexes at compile-time is a recommended optimization for applications were it makes sense.</p> <p>When using SQLite as a shared library, an application can test to see whether or not mutexes have been disabled using the [sqlite3_threadsafe()] API. Applications that link against SQLite at run-time and use SQLite from multiple threads should probably check this API to make sure they did not accidently get linked against a version of ................................................................................ startup.</i></p> <h2>4.0 Adding New Virtual File Systems</h2> <p>Since [version 3.5.0], SQLite has supported an interface called the [sqlite3_vfs | virtual file system] or "VFS". This object is somewhat misnamed since it is really an interface to whole underlying operating system, not just the filesystem.</p> <p> One of the interesting features of the VFS interface is that SQLite can support multiple VFSes at the same time. Each [database connection] has to choose a single VFS for its use when the connection is first opened using [sqlite3_open_v2()]. But if a process contains multiple [database connections] each can choose |