Documentation Source Text

Check-in [06a55cbcb5]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix another typo in custombuild.html.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 06a55cbcb5fb756fd5c112df09f6adf775c4bd00
User & Date: dan 2010-01-15 05:16:12.000
Context
2010-01-18
14:12
Add a section to fts3.in to explain how to use the matchinfo() function efficiently. (check-in: 0917dec067 user: dan tags: trunk)
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)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/custombuild.in.
︙︙
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110

<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
the SQLite library that has its mutexes disabled.  Single-threaded








|








96
97
98
99
100
101
102
103
104
105
106
107
108
109
110

<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 where 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
the SQLite library that has its mutexes disabled.  Single-threaded
︙︙