Documentation Source Text

Check-in [f8c8d8614f]
Login

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

Overview
Comment:Fix typo in the lang_createindex.html document.
Timelines: family | ancestors | descendants | both | version-3.23
Files: files | file ages | folders
SHA3-256: f8c8d8614fc8ca45c8f6e3ea91731e66340e07407583b1d70763aeca0d279293
User & Date: drh 2018-04-09 01:19:47
Context
2018-04-09
22:34
Fix typos in cpu.html. check-in: fc3877b543 user: drh tags: version-3.23
01:19
Fix typo in the lang_createindex.html document. check-in: f8c8d8614f user: drh tags: version-3.23
2018-04-07
12:00
Fix a typo on the "when to use" page. check-in: 1963430c3f user: drh tags: version-3.23
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/lang.in.

835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
limited to the value set by
[sqlite3_limit]([SQLITE_LIMIT_COLUMN],...).)^</p>

<tcl>hd_fragment uniqueidx {unique index}</tcl>
<p>^If the UNIQUE keyword appears between CREATE and INDEX then duplicate
index entries are not allowed.  ^Any attempt to insert a duplicate entry
will result in an error.  ^For the purposes of unique indices, all NULL values
are considered to different from all other NULL values and are thus unique.
This is one of the two possible interpretations of the SQL-92 standard
(the language in the standard is ambiguous) and is the interpretation
followed by PostgreSQL, MySQL, Firebird, and Oracle.  Informix and
Microsoft SQL Server follow the other interpretation of the standard.</p>

<p>^If the optional IF NOT EXISTS clause is present and another index
with the same name already exists, then this command becomes a no-op.</p>







|







835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
limited to the value set by
[sqlite3_limit]([SQLITE_LIMIT_COLUMN],...).)^</p>

<tcl>hd_fragment uniqueidx {unique index}</tcl>
<p>^If the UNIQUE keyword appears between CREATE and INDEX then duplicate
index entries are not allowed.  ^Any attempt to insert a duplicate entry
will result in an error.  ^For the purposes of unique indices, all NULL values
are considered different from all other NULL values and are thus unique.
This is one of the two possible interpretations of the SQL-92 standard
(the language in the standard is ambiguous) and is the interpretation
followed by PostgreSQL, MySQL, Firebird, and Oracle.  Informix and
Microsoft SQL Server follow the other interpretation of the standard.</p>

<p>^If the optional IF NOT EXISTS clause is present and another index
with the same name already exists, then this command becomes a no-op.</p>