Documentation Source Text

Check-in [ede2d703a0]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Minor tweak to the aff_short.html document.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:ede2d703a03cec111bc4ffa5016938a7bdbdf25afd0e6842dd0c4ad882b81b15
User & Date: drh 2017-06-06 20:24:30
Context
2017-06-07
14:00
Fix typo in the file format document. check-in: 64a0c62941 user: drh tags: trunk
2017-06-06
20:24
Minor tweak to the aff_short.html document. check-in: ede2d703a0 user: drh tags: trunk
17:29
Tweaks to the faster-than-filesystem document to make it more mobile-friendly. check-in: fb0299e43a user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/aff_short.in.

24
25
26
27
28
29
30




31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
There are many advantages to using SQLite as an application file format,
including:
</p>

<ol type="1">
<li><b>Better performance</b>
<ul>




<li> The application only has to load the data it needs, rather
     than reading the entire file and holding a complete parse
     in memory.
<li> Small edits only overwrite the parts of the file that change,
     reducing write time and wear on SSD drives.
<li> In many cases, loading content from an SQLite database
     is faster than reading individual files from disk.
     See [Internal Versus External BLOBs] and
     [faster than the filesystem|35% Faster Than The Filesystem].
</ul>
<li><b>Reduced application cost and complexity</b>
<ul>
<li> No application file I/O code to write and debug.
<li> Content can be accessed and updated using concise SQL queries instead
     of lengthy and error-prone procedural routines.
<li> The file format can be extended in future releases simply







>
>
>
>





<
<
<
<







24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39




40
41
42
43
44
45
46
There are many advantages to using SQLite as an application file format,
including:
</p>

<ol type="1">
<li><b>Better performance</b>
<ul>
<li> Reading and writing from an SQLite database
     is often faster than reading and writing individual files from disk.
     See [faster than the filesystem|35% Faster Than The Filesystem]
     and [Internal Versus External BLOBs].
<li> The application only has to load the data it needs, rather
     than reading the entire file and holding a complete parse
     in memory.
<li> Small edits only overwrite the parts of the file that change,
     reducing write time and wear on SSD drives.




</ul>
<li><b>Reduced application cost and complexity</b>
<ul>
<li> No application file I/O code to write and debug.
<li> Content can be accessed and updated using concise SQL queries instead
     of lengthy and error-prone procedural routines.
<li> The file format can be extended in future releases simply