Documentation Source Text

Check-in [7ca803de2b]
Login

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

Overview
Comment:Change an "is" to a "was" in the news.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 7ca803de2b1eab8dc5946dbe7a2566466bcb4e3a
User & Date: drh 2014-08-14 14:39:04
Context
2014-08-15
00:49
Clarifications to the ON CONFLICT documentation. check-in: 445adeb211 user: drh tags: trunk
2014-08-14
14:39
Change an "is" to a "was" in the news. check-in: 7ca803de2b user: drh tags: trunk
14:37
Update the 3.8.6 news item. check-in: 9af7ac771f user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/news.in.

24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
   Upgrading from all previous versions is recommended.

<p>This release contains the usual assortment of obscure bug fixes.
   One bug, however, deserves special attention.
   A problem appeared in the [CREATE INDEX] command beginning with
   [version 3.8.2] (2013-12-06) that allowed, under some circumstances,
   a UNIQUE index to be created on a column that was not unique.  Once
   the index is created, no new non-unique entries could be inserted, but
   preexisting non-unique entries would remain.  See ticket
   [http://www.sqlite.org/src/info/9a6daf340df99ba93c|9a6daf340df99ba93c]
   for further information.  In addition to fixing this bug, the
   [PRAGMA integrity_check] command has been enhanced to detect
   non-uniqueness in UNIQUE indices, so that if this bug did introduce
   any problems in databases, those problems can be easily detected.








|







24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
   Upgrading from all previous versions is recommended.

<p>This release contains the usual assortment of obscure bug fixes.
   One bug, however, deserves special attention.
   A problem appeared in the [CREATE INDEX] command beginning with
   [version 3.8.2] (2013-12-06) that allowed, under some circumstances,
   a UNIQUE index to be created on a column that was not unique.  Once
   the index was created, no new non-unique entries could be inserted, but
   preexisting non-unique entries would remain.  See ticket
   [http://www.sqlite.org/src/info/9a6daf340df99ba93c|9a6daf340df99ba93c]
   for further information.  In addition to fixing this bug, the
   [PRAGMA integrity_check] command has been enhanced to detect
   non-uniqueness in UNIQUE indices, so that if this bug did introduce
   any problems in databases, those problems can be easily detected.