Documentation Source Text

<p>
The following additional compile-time options are recommended in order to
provide a full-featured command-line shell:

<ul>
<li> [-DSQLITE_THREADSAFE=0]
<li> [-DSQLITE_ENABLE_EXPLAIN_COMMENTS]
<li> [-DSQLITE_HAVE_ZLIB]
<li> [-DSQLITE_INTROSPECTION_PRAGMAS]
<li> [-DSQLITE_ENABLE_UNKNOWN_SQL_FUNCTION]
<li> [-DSQLITE_ENABLE_STMTVTAB]
<li> [-DSQLITE_ENABLE_DBPAGE_VTAB]
<li> [-DSQLITE_ENABLE_DBSTAT_VTAB]
<li> [-DSQLITE_ENABLE_OFFSET_SQL_FUNC]
<li> [-DSQLITE_ENABLE_JSON1]

COMPILE_OPTION {SQLITE_USE_FCNTL_TRACE} {
  This option causes SQLite to issue extra [SQLITE_FCNTL_TRACE] file controls
  to provide supplementary information to the VFS.  The "vfslog.c" extension
  makes use of this to provide enhanced logs of VFS activity.
}

COMPILE_OPTION {SQLITE_HAVE_ZLIB} {
  This option causes some extensions to link against the 
  [https://zlib.net|zlib compression library].
  <p>
  This option has no affect on the SQLite core.  It is only used by extensions.
  This is option is necessary for the commpression and decompression
  functions that are part of [SQL Archive] support in the
  [command-line shell].

  abundance of primary disk space because the error occurs when writing
  into [temporary disk files] on a system where temporary files are stored
  on a separate partition with much less space that the primary disk.
}
RESCODE SQLITE_CANTOPEN    14   {
  The SQLITE_CANTOPEN result code indicates that SQLite was unable to
  open a file.  The file in question might be a primary database file
  or one of several [temporary disk files].
}
RESCODE SQLITE_PROTOCOL    15   {
  The SQLITE_PROTOCOL result code indicates a problem with the file locking
  protocol used by SQLite.  The SQLITE_PROTOCOL error is currently only
  returned when using [WAL mode] and attempting to start a new transaction.
  There is a race condition that can occur when two separate 
  [database connections] both try to start a transaction at the same time