Documentation Source Text

Check-in [fb87225a7a]
Login

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

Overview
Comment:Fix a typo in the testing.html document.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: fb87225a7af0947ac9c9d8cd21233fa6cc5ff3e373b31ab143861297a51d1fad
User & Date: drh 2018-09-03 10:46:11.724
Context
2018-09-03
10:57
Fix a typo in the CREATE TABLE documentation. (check-in: aff4908d94 user: drh tags: trunk)
10:46
Fix a typo in the testing.html document. (check-in: fb87225a7a user: drh tags: trunk)
2018-08-27
20:52
Enhancements to the virtual table documentation to describe the operation of SQLITE_INDEX_CONSTRAINT_FUNCTION. (check-in: f3d8866e42 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/testing.in.
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
<li>And so forth....
</ul>

<p>Since undefined and implementation-defined behavior is non-portable
and can easily lead to incorrect answers, SQLite works very hard to avoid it.
For example,
when adding two integer column values together as part of an SQL statement,
SQLite does not simple add them together using the C-language "+" operator.
Instead, it first checks to make sure the
addition will not overflow, and if it will, it does the addition using
floating point instead.

<p>To help ensure that SQLite does not make use of undefined or
implementation defined behavior, the test suites are rerun using
instrumented builds that try to detect undefined behavior.  For example,







|







912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
<li>And so forth....
</ul>

<p>Since undefined and implementation-defined behavior is non-portable
and can easily lead to incorrect answers, SQLite works very hard to avoid it.
For example,
when adding two integer column values together as part of an SQL statement,
SQLite does not simply add them together using the C-language "+" operator.
Instead, it first checks to make sure the
addition will not overflow, and if it will, it does the addition using
floating point instead.

<p>To help ensure that SQLite does not make use of undefined or
implementation defined behavior, the test suites are rerun using
instrumented builds that try to detect undefined behavior.  For example,