Documentation Source Text

     run within a trigger.
<li> Add the ability to read from [WAL mode] databases even if the application 
     lacks write permission on the database and its containing directory, as long as
     the -shm and -wal files exist in that directory.
<li> Added the [rtreecheck()] scalar SQL function to the [R-Tree extension].
<li> Added the [sqlite3_vtab_nochange()] and [sqlite3_value_nochange()] interfaces
     to help virtual table implementations optimize UPDATE operations.
<li> Added the [sqlite3_vtab_collation()] interface.
<li> Added support for the [FTS5 initial token|"&#94;" initial token syntax] in FTS5.
<li> New extensions:
<ol type='a'>
  <li> The [Zipfile virtual table] can read and write a 
       [https://en.wikipedia.org/wiki/Zip_(file_format)|ZIP Archive].
  <li> Added the fsdir(PATH) [table-valued function] to the
       [https://sqlite.org/src/file/ext/misc/fileio.c|fileio.c] extension,

RESCODE SQLITE_WARNING_AUTOINDEX       {SQLITE_WARNING | (1<<8)} {
  The SQLITE_WARNING_AUTOINDEX result code is
  passed to the callback of
  [sqlite3_log()] whenever [automatic indexing] is used.
  This can serve as a warning to application designers that the
  database might benefit from additional indexes.
}

RESCODE SQLITE_ERROR_MISSING_COLLSEQ  {SQLITE_ERROR | (1<<8)} {
  The SQLITE_ERROR_MISSING_COLLSEQ result code means that an SQL
  statement could not be prepared because a collating sequence named
  in that SQL statement could not be located.
  <p>
  Sometimes when this error code is encountered, the
  [sqlite3_prepare_v2()] routine will convert the error into
  [SQLITE_ERROR_RETRY] and try again to prepare the SQL statement
  using a different query plan that does not require the use of
  the unknown collating sequence.
}
RESCODE SQLITE_ERROR_RETRY {SQLITE_ERROR | (2<<8)} {
  The SQLITE_ERROR_RETRY is used internally to provoke [sqlite3_prepare_v2()]
  (or one of its sibling routines for creating prepared statements) to
  try again to prepare a statement that failed with an error on the
  previous attempt.
}
RESCODE SQLITE_READONLY_CANTINIT {SQLITE_READONLY | (5<<8)} {
  The SQLITE_READONLY_CANTINIT result code originates in the xShmMap method
  of a [VFS] to indicate that the shared memory region used by [WAL mode]
  exists buts its content is unreliable and unusable by the current process
  since the current process does not have write permission on the shared
  memory region.  (The shared memory region for WAL mode is normally a
  file with a "-wal" suffix that is mmapped into the process space.  If
  the current process does not have write permission on that file, then it
  cannot write into shared memory.)
  <p>
  Higher level logic within SQLite will normally intercept the error code
  and create a temporary in-memory shared memory region so that the current
  process can at least read the content of the database.  This result code
  should not reach the application interface layer.
}
RESCODE SQLITE_READONLY_DIRECTORY {SQLITE_READONLY | (6<<8)} {
  The SQLITE_READONLY_DIRECTORY result code indicates that the database
  is read-only because process does not have permission to create
  a journal file in the same directory as the database and the creation of
  a journal file is a prerequisite for writing.
}

#############################################################################
# Code to process the RESCODE values
#
# Convert formula RESCODE values into numerics
set nResCode 0
set nPrimCode 0

#
foreach val [lsort -int [array names valtoname]] {
  set name $valtoname($val)
  regsub {sqlite_} [string tolower $name] {} tag
  hd_puts "<!--------------------------------------------------------------->\n"
  hd_fragment $tag --override $name
  hd_puts "<h3>($val) $valtoname($val)</h3>\n"
  hd_resolve <p>$resdesc($name)\n\n
}

</tcl>