Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a typo on the "when to use" page. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | version-3.23 |
Files: | files | file ages | folders |
SHA3-256: |
1963430c3f3cee2999b92b4a64d5bbd8 |
User & Date: | drh 2018-04-07 12:00:27.509 |
Context
2018-04-09
| ||
01:19 | Fix typo in the lang_createindex.html document. (check-in: f8c8d8614f user: drh tags: version-3.23) | |
2018-04-07
| ||
12:00 | Fix a typo on the "when to use" page. (check-in: 1963430c3f user: drh tags: version-3.23) | |
11:54 | Add "data transfer format" to the use cases for SQLite in the "When to Use" document. (check-in: d232f16b87 user: drh tags: version-3.23) | |
Changes
Changes to pages/whentouse.in.
︙ | ︙ | |||
328 329 330 331 332 333 334 | </li> <li><p><b>High Concurrency</b></p> <p> SQLite supports an unlimited number of simultaneous readers, but it will only allow one writer at any instant in time. | | | 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 | </li> <li><p><b>High Concurrency</b></p> <p> SQLite supports an unlimited number of simultaneous readers, but it will only allow one writer at any instant in time. For many situations, this is not a problem. Writers queue up. Each application does its database work quickly and moves on, and no lock lasts for more than a few dozen milliseconds. But there are some applications that require more concurrency, and those applications may need to seek a different solution. </p> </li> |
︙ | ︙ |