Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in the when-to-use page. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
556d3bb6c49b56d486735faf2e4545a5 |
| User & Date: | drh 2020-02-22 12:53:39 |
Context
|
2020-02-22
| ||
| 21:35 | Fix a typo in datatype3.html. check-in: ea9656e7d7 user: drh tags: trunk | |
| 12:54 | Fix a typo in the when-to-use page. check-in: ee17d2f67b user: drh tags: branch-3.31 | |
| 12:53 | Fix a typo in the when-to-use page. check-in: 556d3bb6c4 user: drh tags: trunk | |
|
2020-02-21
| ||
| 15:27 | Fix typos and improve phrasing in testing.in. check-in: 80df0299e7 user: drh tags: trunk | |
Changes
Changes to pages/whentouse.in.
401 402 403 404 405 406 407 408 409 410 |
</li> <li><p><b>Otherwise → choose SQLite!</b></p> <p>For device-local storage with low writer concurrency and less than a terabyte of content, SQLite is almost always a better solution. SQLite is fast and reliable and it requires no configuration or maintenance. It keeps thing simple. SQLite "just works". </li> </ol> |
| |
401 402 403 404 405 406 407 408 409 410 |
</li>
<li><p><b>Otherwise → choose SQLite!</b></p>
<p>For device-local storage with low writer concurrency and less than a
terabyte of content, SQLite is almost always a better solution. SQLite
is fast and reliable and it requires no configuration or maintenance.
It keeps things simple. SQLite "just works".
</li>
</ol>
|