Documentation Source Text

Check-in [a7a8ecb98d]
Login

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

Overview
Comment:Fix two documentation typos.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: a7a8ecb98df874cd6227f4b826b965713a8fb9bf64edaaf6cba9ddbbfb86f5d4
User & Date: drh 2020-01-26 18:03:49
Context
2020-01-27
18:06
Initial changes for the 3.31.1 patch release. check-in: 505d43b621 user: drh tags: trunk
2020-01-26
18:03
Fix two documentation typos. check-in: a7a8ecb98d user: drh tags: trunk
2020-01-22
19:04
Version 3.31.0 check-in: 44e1ce5453 user: drh tags: trunk, release, version-3.31.0
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/deterministic.in.

69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
^(The built-in [date and time functions] of SQLite are a special case.
These functions are usually considered deterministic.  However, if
these functions use the string "now" as the date, or if they use
the [localtime modifier] or the [utc modifier], then they are
considered non-deterministic.)^  ^Because the function inputs are
not necessarily known until run-time, the date/time functions will
throw an exception if they encounter any of the non-deterministic
features in a context where only deterministic functions are allows.

<p>
Prior to SQLite 3.20.0 ([dateof:3.20.0]) all date/time functions were
always considered non-deterministic.  The ability for date/time functions
to be deterministic sometimes and non-deterministic at other times,
depending on their arguments, was added for the 3.20.0 release.








|







69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
^(The built-in [date and time functions] of SQLite are a special case.
These functions are usually considered deterministic.  However, if
these functions use the string "now" as the date, or if they use
the [localtime modifier] or the [utc modifier], then they are
considered non-deterministic.)^  ^Because the function inputs are
not necessarily known until run-time, the date/time functions will
throw an exception if they encounter any of the non-deterministic
features in a context where only deterministic functions are allowed.

<p>
Prior to SQLite 3.20.0 ([dateof:3.20.0]) all date/time functions were
always considered non-deterministic.  The ability for date/time functions
to be deterministic sometimes and non-deterministic at other times,
depending on their arguments, was added for the 3.20.0 release.

Changes to pages/testing.in.

620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636

<p>Branch coverage is more strict.  With branch coverage, each test and
each subblock within the statement is considered separately.  In order
to achieve 100% branch coverage in the example above, there must be at
least three test cases:</p>

<p><ul>
<li> a<=b
<li> a>b && c==25
<li> a>b && c!=25
</ul></p>

<p>Any one of the above test cases would provide 100% statement coverage
but all three are required for 100% branch coverage.  Generally speaking,
100% branch coverage implies 100% statement coverage, but the converse is
not true.  To reemphasize, the
[TH3] test harness for SQLite provides the stronger form of







|
|
|







620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636

<p>Branch coverage is more strict.  With branch coverage, each test and
each subblock within the statement is considered separately.  In order
to achieve 100% branch coverage in the example above, there must be at
least three test cases:</p>

<p><ul>
<li> a&lt;=b
<li> a&gt;b && c==25
<li> a&gt;b && c!=25
</ul></p>

<p>Any one of the above test cases would provide 100% statement coverage
but all three are required for 100% branch coverage.  Generally speaking,
100% branch coverage implies 100% statement coverage, but the converse is
not true.  To reemphasize, the
[TH3] test harness for SQLite provides the stronger form of