Documentation Source Text

<li>Fix [CREATE TABLE AS] so that columns of type TEXT never end up
    holding an INT value.  Ticket
    [https://www.sqlite.org/src/info/f2ad7de056ab1dc9200|f2ad7de056ab1dc9200]
<li>Fix [CREATE TABLE AS] so that it does not leave NULL entries in the
    [sqlite_master table] if the SELECT statement on the right-hand side
    aborts with an error.  Ticket
    [https://www.sqlite.org/src/info/873cae2b6e25b|873cae2b6e25b]
<li>Fix the [skip-scan optimization] so that it works correctly when
    the [OR optimization] is used on [WITHOUT ROWID] tables.  Ticket
    [https://www.sqlite.org/src/info/8fd39115d8f46|8fd39115d8f46]
<li>Fix the [sqlite3_memory_used()] and [sqlite3_memory_highwater()] interfaces
    so that they actually do provide a 64-bit answer.
}

chng {2015-05-20 (3.8.10.2)} {
<li>Fix an index corruption issue introduced by [version 3.8.7].  An index
    with a TEXT key can be corrupted by an [INSERT] into the corresponding 

  input rows.
  ^Thus if the BETWEEN term is not used as an index constraint and
  instead must be used to test input rows, the <i>expr1</i> expression is
  only evaluated once.
}

HEADING 1 {OR optimizations} or_opt
hd_keywords {or optimization} {OR optimization}

PARAGRAPH {
  WHERE clause constraints that are connected by OR instead of AND can
  be handled in two different ways.
  ^(If a term consists of multiple subterms containing a common column
  name and separated by OR, like this:
}