Documentation Source Text

Check-in [dd1def55d8]
Login

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

Overview
Comment:Fix a typo on the quirks.html page.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: dd1def55d82bb32c9e96d15084a9e47728ff693352118234a51f57d0d8cd603e
User & Date: drh 2018-11-28 10:08:08.734
Context
2018-11-28
10:21
Further enhancements to the Quirks document. (check-in: 8a0206bb29 user: drh tags: trunk)
10:08
Fix a typo on the quirks.html page. (check-in: dd1def55d8 user: drh tags: trunk)
2018-11-26
18:57
Caution users to have well-defined column names in VIEWs. (check-in: 5a0203cdca user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/quirks.in.
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
the [PRAGMA foreign_keys] statement.  Or, foreign key enforcement can
be activated at compile-time using the
[-DSQLITE_DEFAULT_FOREIGN_KEYS=1] compile-time option.

<h1>PRIMARY KEYs Can Sometimes Contain NULLs</h1>

<p>
Usually (the exceptions are [INTEGER PRIMARY KEY] tables 
[WITHOUT ROWID] tables) a PRIMARY KEY in an SQLite table is really
the same as a UNIQUE constraint.  Due to an historical oversight,
the column values of such a PRIMARY KEY are allowed to be NULL.
This is a bug, but by the time the problem was discovered there
where so many databases in circulation that depended on the bug that
the decision was made to support the bugging behavior moving forward.
<p>







|







158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
the [PRAGMA foreign_keys] statement.  Or, foreign key enforcement can
be activated at compile-time using the
[-DSQLITE_DEFAULT_FOREIGN_KEYS=1] compile-time option.

<h1>PRIMARY KEYs Can Sometimes Contain NULLs</h1>

<p>
Usually (the exceptions are [INTEGER PRIMARY KEY] tables and
[WITHOUT ROWID] tables) a PRIMARY KEY in an SQLite table is really
the same as a UNIQUE constraint.  Due to an historical oversight,
the column values of such a PRIMARY KEY are allowed to be NULL.
This is a bug, but by the time the problem was discovered there
where so many databases in circulation that depended on the bug that
the decision was made to support the bugging behavior moving forward.
<p>