Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Futher homepage enhancements. Improvements and typo fixes on secondary pages. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
e6aa1d2d9aeb39403934e2e2d3b5c102 |
User & Date: | drh 2018-12-10 12:52:29.824 |
Context
2018-12-14
| ||
15:54 | Rename the "security.html" document as "Defense Against Dark Arts". Add the additional recommendation to avoid memory-mapped I/O on untrusted database files. (check-in: 11d0259504 user: drh tags: trunk) | |
2018-12-10
| ||
12:52 | Futher homepage enhancements. Improvements and typo fixes on secondary pages. (check-in: e6aa1d2d9a user: drh tags: trunk) | |
12:34 | Further tweaks to the homepage. (check-in: dd073d8325 user: drh tags: trunk) | |
Changes
Changes to pages/features.in.
1 2 3 4 5 6 7 8 9 10 11 12 13 | <title>Features Of SQLite</title> <h1 align=center>Features Of SQLite</h1> <p><ul> <li><a href="transactional.html">Transactions</a> are atomic, consistent, isolated, and durable (ACID) even after system crashes and power failures.</li> <li><a href="zeroconf.html">Zero-configuration</a> - no setup or administration needed.</li> <li>[Full-featured SQL] implementation with advanced capabilities like [partial indexes], [indexes on expressions], [json1|JSON], | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 | <title>Features Of SQLite</title> <h1 align=center>Features Of SQLite</h1> <p><ul> <li><a href="transactional.html">Transactions</a> are atomic, consistent, isolated, and durable (ACID) even after system crashes and power failures.</li> <li><a href="zeroconf.html">Zero-configuration</a> - no setup or administration needed.</li> <li>[Full-featured SQL] implementation with advanced capabilities like [partial indexes], [indexes on expressions], [json1|JSON], [common table expressions], and [window functions]. (<a href="omitted.html">Omitted features</a>)</li> <li>A complete database is stored in a <a href="onefile.html">single cross-platform disk file</a>. Great for use as an [application file format].</li> <li>Supports terabyte-sized databases and gigabyte-sized strings and blobs. (See <a href="limits.html">limits.html</a>.) <li>Small code [footprint]: |
︙ | ︙ |
Changes to pages/index.in.
︙ | ︙ | |||
18 19 20 21 22 23 24 | <p> The SQLite [file format] is stable, cross-platform, and backwards compatible and the developers pledge to keep it that way through at least the year 2050. SQLite database files are commonly uses as a container to transfer rich content between systems [affshort|[1]] | > | | | 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 | <p> The SQLite [file format] is stable, cross-platform, and backwards compatible and the developers pledge to keep it that way through at least the year 2050. SQLite database files are commonly uses as a container to transfer rich content between systems [affshort|[1]] [SQLAR|[2]] [appformat|[3]] and as a long-term archival format for data [recommended storage format|[4]]. There are over 1 trillion SQLite databases in active use. <p> SQLite [https://sqlite.org/src|source code] is in the [public-domain] and is free to everyone to use for any purpose. |
︙ | ︙ |
Changes to pages/whynotgit.in.
︙ | ︙ | |||
58 59 60 61 62 63 64 | <p> Git allows you to go backwards in time easily. Given the latest check-in on a branch, Git lets you see all the ancestors of that check-in. But Git makes it difficult to move in the other direction. Given some historical check-in, it is quite challenging in Git to find out what came next. It can be done, but it is sufficiently | | | 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 | <p> Git allows you to go backwards in time easily. Given the latest check-in on a branch, Git lets you see all the ancestors of that check-in. But Git makes it difficult to move in the other direction. Given some historical check-in, it is quite challenging in Git to find out what came next. It can be done, but it is sufficiently difficult that people rarely do it. Common interfaces for Git, such as GitHub, do not support the ability. <p>It is not impossible to find the descendents of a check-in in Git. It is merely difficult. For example, there is a [https://stackoverflow.com/questions/27960605/find-all-the-direct-descendants-of-a-given-commit#27962018|stackoverflow page] showing the command sequence for finding the descendents of a check-in |
︙ | ︙ | |||
183 184 185 186 187 188 189 | but that introduces another third-party dependency and a centralized service, which mitigate the key advantage of Git which is that it is "distributed". There are various free alternatives to GitHub, such as GitLab, but those too have a lot of dependencies and require a lot of server setup. <p> | | | | | | | 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 | but that introduces another third-party dependency and a centralized service, which mitigate the key advantage of Git which is that it is "distributed". There are various free alternatives to GitHub, such as GitLab, but those too have a lot of dependencies and require a lot of server setup. <p> In contrast, Fossil is a single standalone binary which is installed by putting it on $PATH. That one binary contains all the functionality of core Git and also GitHub and/or GitLab. It manages a community server with wiki, bug tracking, and forums, provides packaged downloads for consumers, login managements, and so forth, with no extra software required. <p> Less administration means that programmers spend more time working on the software (SQLite in this case) and less time fussing with the version control system. <h2>Git provides a poor user experience</h2> |
︙ | ︙ |