Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Clarification of what counts as using a database connection for restrictions on SQLITE_THREADSAFE=2. |
|---|---|
| Downloads: | Tarball | ZIP archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
84df66d24bcdd725e6f2c65c47894b1a |
| User & Date: | drh 2012-05-30 00:46:18.692 |
Context
|
2012-05-30
| ||
| 14:25 | Fix the "search" box so that it accepts upper and lower case search terms (with case folding) and OR and NEAR search and phrase searches. Exclude some of the aggregate documents from indexing. (check-in: 26dedb8a9a user: drh tags: trunk) | |
| 00:46 | Clarification of what counts as using a database connection for restrictions on SQLITE_THREADSAFE=2. (check-in: 84df66d24b user: drh tags: trunk) | |
|
2012-05-29
| ||
| 01:06 | Add a brief note to the R-Tree documentation to encourage applications to round contained-within query boxes outward slightly to account for round-off error in 64-to-32-bit floating point conversions. (check-in: 1f473ab6ac user: drh tags: trunk) | |
Changes
Changes to pages/compile.in.
| ︙ | ︙ | |||
256 257 258 259 260 261 262 | This option controls whether or not code is included in SQLite to enable it to operate safely in a multithreaded environment. The default is SQLITE_THREADSAFE=1 which is safe for use in a multithreaded environment. When compiled with SQLITE_THREADSAFE=0 all mutexing code is omitted and it is unsafe to use SQLite in a multithreaded program. When compiled with SQLITE_THREADSAFE=2, SQLite can be used in a multithreaded program so long as no two threads attempt to use the same | | > | 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 | This option controls whether or not code is included in SQLite to enable it to operate safely in a multithreaded environment. The default is SQLITE_THREADSAFE=1 which is safe for use in a multithreaded environment. When compiled with SQLITE_THREADSAFE=0 all mutexing code is omitted and it is unsafe to use SQLite in a multithreaded program. When compiled with SQLITE_THREADSAFE=2, SQLite can be used in a multithreaded program so long as no two threads attempt to use the same [database connection] (or any [prepared statements] derived from that database connection) at the same time. To put it another way, SQLITE_THREADSAFE=1 sets the default [threading mode] to Serialized. SQLITE_THREADSAFE=2 sets the default [threading mode] to Multi-threaded. And SQLITE_THREADSAFE=0 sets the [threading mode] to Single-threaded. The value of SQLITE_THREADSAFE can be determined at run-time |
| ︙ | ︙ |