Documentation Source Text

Check-in [7941cd31c2]
Login

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

Overview
Comment:Fix hyperlink errors in the sqlanalyze.html page.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 7941cd31c2056f6f2c6a9d2bf74ccda368b72d6923905a4f618b897cc1705b50
User & Date: drh 2018-01-25 12:25:43
Context
2018-01-25
16:06
Fix a typo on the privatebranch.html page. check-in: a41da69db7 user: drh tags: trunk
12:25
Fix hyperlink errors in the sqlanalyze.html page. check-in: 7941cd31c2 user: drh tags: trunk
2018-01-22
18:50
Version 3.22.0 check-in: 09b0d075dc user: drh tags: trunk, release, version-3.22.0
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/sqlanalyze.in.

13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
sqlite3_analyzer database.sqlite
</pre></blockquote>

<p>
The output is a human-readable ASCII text report that provides information
on the space utilization of the database file.  The report is intended to
be self-explanatory, though there is some 
<a href='#defs'>additional explanation</a> of the
various parameters reported toward the end of the report.

<p>
The output is also valid SQL.  Most of the report text is contained within
a header comment, with various SQL statements that create and initialize
a database at the
<a href="#sqlx">end of the report</a>.  The constructed database contains
the raw data from which the report was extracted.  Hence the original
report can be read into an instance of the [command-line shell] and then
the raw data can be queried to dig deeper into the space utilization of
a particular database file.

<h2>Implementation</h2>








|






|







13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
sqlite3_analyzer database.sqlite
</pre></blockquote>

<p>
The output is a human-readable ASCII text report that provides information
on the space utilization of the database file.  The report is intended to
be self-explanatory, though there is some 
<a href="sqlanalyze.html#defs">additional explanation</a> of the
various parameters reported toward the end of the report.

<p>
The output is also valid SQL.  Most of the report text is contained within
a header comment, with various SQL statements that create and initialize
a database at the
<a href="sqlanalyze.html#sqlx">end of the report</a>.  The constructed database contains
the raw data from which the report was extracted.  Hence the original
report can be read into an instance of the [command-line shell] and then
the raw data can be queried to dig deeper into the space utilization of
a particular database file.

<h2>Implementation</h2>