Documentation Source Text

Check-in [f6e2eab4e7]
Login

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

Overview
Comment:Clarify the behavior of AUTOINCREMENT after an UPDATE.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: f6e2eab4e71644b1a8f695e618adc5406a1a1ee0
User & Date: drh 2017-02-02 23:55:23.601
Context
2017-02-03
04:10
Clarify wording about PRAGMA synchronous=NORMAL and WAL mode. (check-in: 7660cac647 user: drh tags: trunk)
2017-02-02
23:55
Clarify the behavior of AUTOINCREMENT after an UPDATE. (check-in: f6e2eab4e7 user: drh tags: trunk)
14:48
Update the wording on the description of the WHEN clause on triggers. (check-in: 09d3dc5c51 user: drh tags: trunk)
Changes
Side-by-Side Diff Ignore Whitespace Patch
Changes to pages/autoinc.in.
︙
91
92
93
94
95
96
97
98

99
100
101
102
103
104
105

91
92
93
94
95
96
97

98
99
100
101
102
103
104
105








-
+









<h1>The AUTOINCREMENT Keyword</h1>

<p>
^If a column has the type INTEGER PRIMARY KEY AUTOINCREMENT then a slightly
different ROWID selection algorithm is used.  
^The ROWID chosen for the new row is at least one larger than the largest ROWID
that has ever before been inserted in that same table.  ^If the table has never
that has ever before existed in that same table.  ^If the table has never
before contained any data, then a ROWID of 1 is used.  ^If the largest possible
ROWID has previously been inserted, then
new INSERTs are not allowed and any attempt to insert a new row will
fail with an SQLITE_FULL error.  
^(Only ROWID values from previous transactions that
were committed are considered.  ROWID values that were rolled back
are ignored and can be reused.)^
︙