Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Typos in the shared-cache mode documentation. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | branch-3.32 |
Files: | files | file ages | folders |
SHA3-256: |
f79cc54f2593d4631565819c0ab87de2 |
User & Date: | drh 2020-07-03 09:57:00.635 |
Context
2020-07-11
| ||
00:03 | Fix hyperlink problem in the lang.html page. (check-in: afb2b13396 user: drh tags: branch-3.32) | |
2020-07-03
| ||
09:57 | Typos in the shared-cache mode documentation. (check-in: f79cc54f25 user: drh tags: branch-3.32) | |
2020-06-29
| ||
01:26 | Update the CVE list. (check-in: 7565236dfd user: drh tags: branch-3.32) | |
Changes
Changes to pages/sharedcache.in.
︙ | ︙ | |||
89 90 91 92 93 94 95 | serialize concurrent access attempts on a per-table basis. Tables support two types of locks, "read-locks" and "write-locks". Locks are granted to connections - at any one time, each database connection has either a read-lock, write-lock or no lock on each database table. </p> <p>At any one time, a single table may have any number of active read-locks | | | 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 | serialize concurrent access attempts on a per-table basis. Tables support two types of locks, "read-locks" and "write-locks". Locks are granted to connections - at any one time, each database connection has either a read-lock, write-lock or no lock on each database table. </p> <p>At any one time, a single table may have any number of active read-locks or a single active write lock. To read data from a table, a connection must first obtain a read-lock. To write to a table, a connection must obtain a write-lock on that table. If a required table lock cannot be obtained, the query fails and SQLITE_LOCKED is returned to the caller. </p> <p>Once a connection obtains a table lock, it is not released until the current transaction (read or write) is concluded. |
︙ | ︙ | |||
216 217 218 219 220 221 222 | <h1>Shared Cache And In-Memory Databases</h1> <p> Beginning with SQLite [version 3.7.13] ([dateof:3.7.13]), shared cache can be used on [in-memory databases], provided that the database is created using a [URI filename]. For backwards compatibility, shared cache is always | | | 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 | <h1>Shared Cache And In-Memory Databases</h1> <p> Beginning with SQLite [version 3.7.13] ([dateof:3.7.13]), shared cache can be used on [in-memory databases], provided that the database is created using a [URI filename]. For backwards compatibility, shared cache is always disabled for in-memory databases if the unadorned name ":memory:" is used to open the database. Prior to version 3.7.13, shared cache was always disabled for in-memory databases regardless of the database name used, current system shared cache setting, or query parameters or flags. </p> <p> Enabling shared-cache for an in-memory database allows two or more database connections in the same process to have access to the same in-memory database. An in-memory database in shared cache is automatically deleted and memory is reclaimed when the last connection to that database closes. </p> |