Documentation Source Text

Check-in [0aa5202f33]
Login

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

Overview
Comment:Add a change log for version 3.8.3. Fix a typo in the FAQ.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 0aa5202f33facdcf7048ce86f109ad5db211b093
User & Date: drh 2013-12-14 12:40:07.889
Context
2013-12-14
14:42
Update the change log with SQLITE_DETERMINISTIC. (check-in: 5bc4dbf151 user: drh tags: trunk)
12:40
Add a change log for version 3.8.3. Fix a typo in the FAQ. (check-in: 0aa5202f33 user: drh tags: trunk)
2013-12-12
14:10
Fix missing "is" in the query planner document. (check-in: 200941601a user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/changes.in.
︙︙
13
14
15
16
17
18
19







20
21
22
23
24
25
26

<tcl>
set nChng 0
proc chng {date desc {options {}}} {
  global nChng aChng
  set aChng($nChng) [list $date $desc $options]
  incr nChng
}








chng {2013-12-06 (3.8.2)} {
<li>Changed the defined behavior for the [CAST expression] when floating point values
    greater than  +9223372036854775807 are cast into into integers so that the
    result is the largest possible integer, +9223372036854775807, instead of
    the smallest possible integer, -9223372036854775808.  After this change, 
    CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead








>
>
>
>
>
>
>








13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

<tcl>
set nChng 0
proc chng {date desc {options {}}} {
  global nChng aChng
  set aChng($nChng) [list $date $desc $options]
  incr nChng
}

chng {2014-02-?? (3.8.3)} {
<li>Add [SQLITE_READONLY_DBMOVED] error code, returned at the beginning of a
    transaction, to indicate that the underlying database file has been renamed
    or moved out from under SQLite.
<li>Performance enhancements.
}

chng {2013-12-06 (3.8.2)} {
<li>Changed the defined behavior for the [CAST expression] when floating point values
    greater than  +9223372036854775807 are cast into into integers so that the
    result is the largest possible integer, +9223372036854775807, instead of
    the smallest possible integer, -9223372036854775808.  After this change, 
    CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead
︙︙
Changes to pages/faq.in.
︙︙
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


  <p>Here is the long answer:
  If you declare a column of a table to be [INTEGER PRIMARY KEY], then
  whenever you insert a NULL
  into that column of the table, the NULL is automatically converted
  into an integer which is one greater than the largest value of that
  column over all other rows in the table, or 1 if the table is empty.
  (If the largest possible integer key, 9223372036854775807, then an
  unused key value is chosen at random.)
  For example, suppose you have a table like this:
<blockquote><pre>
CREATE TABLE t1(
  a INTEGER PRIMARY KEY,
  b INTEGER
);








|








18
19
20
21
22
23
24
25
26
27
28
29
30
31
32


  <p>Here is the long answer:
  If you declare a column of a table to be [INTEGER PRIMARY KEY], then
  whenever you insert a NULL
  into that column of the table, the NULL is automatically converted
  into an integer which is one greater than the largest value of that
  column over all other rows in the table, or 1 if the table is empty.
  (If the largest possible integer key 9223372036854775807 is in use then an
  unused key value is chosen at random.)
  For example, suppose you have a table like this:
<blockquote><pre>
CREATE TABLE t1(
  a INTEGER PRIMARY KEY,
  b INTEGER
);
︙︙
Changes to pages/index.in.
︙︙
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107


</td>
<td width="20"></td><td bgcolor="#044a64" width="1"></td><td width="20"></td>
<td valign="top">
<h3>Current Status</h3>

<p><ul>
<li><a href="releaselog/3_8_2.html">Version 3.8.2</a>
of SQLite is recommended for all new development.
Upgrading from versions 3.7.17, 3.8.0.2, and 3.8.1 is optional.
Upgrading from all other prior versions of SQLite
is recommended.</li>
</ul></p>

<h3>Common Links</h3>

<p><ul>








|

|








91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107


</td>
<td width="20"></td><td bgcolor="#044a64" width="1"></td><td width="20"></td>
<td valign="top">
<h3>Current Status</h3>

<p><ul>
<li><a href="releaselog/3_8_3.html">Version 3.8.3</a>
of SQLite is recommended for all new development.
Upgrading from versions 3.7.17, 3.8.0.2, 3.8.1, and 3.8.2 is optional.
Upgrading from all other prior versions of SQLite
is recommended.</li>
</ul></p>

<h3>Common Links</h3>

<p><ul>
︙︙