/******************************************************************************

 ** This file is an amalgamation of many separate C source files from SQLite

 ** version 3.26.0.  By combining all the individual C code files into this

 ** single large file, the entire code can be compiled as a single translation

 ** unit.  This allows many compilers to do optimizations that would not be

 ** possible if the files were compiled separately.  Performance improvements

 ** of 5% or more are commonly seen when SQLite is compiled as a single

 ** translation unit.

 **

 ** This file is all you need to compile SQLite.  To use SQLite in other

 ** programs, you need this file and the "sqlite3.h" header file that defines

 ** the programming interface to the SQLite library.  (If you do not have

 ** the "sqlite3.h" header file at hand, you will find a copy embedded within

 ** the text of this file.  Search for "Begin file sqlite3.h" to find the start

 ** of the embedded sqlite3.h header file.) Additional code files may be needed

 ** if you want a wrapper to interface SQLite with your choice of programming

 ** language. The code for the "sqlite3" command-line shell is also in a

 ** separate file. This file contains only code for the core SQLite library.

 */

 #define SQLITE_CORE 1

 #define SQLITE_AMALGAMATION 1

 #ifndef SQLITE_PRIVATE

 # define SQLITE_PRIVATE static

 #endif

 /************** Begin file ctime.c *******************************************/

 /*

 ** 2010 February 23

 **

 ** The author disclaims copyright to this source code.  In place of

 ** a legal notice, here is a blessing:

 **

 **    May you do good and not evil.

 **    May you find forgiveness for yourself and forgive others.

 **    May you share freely, never taking more than you give.

 **

 *************************************************************************

 **

 ** This file implements routines used to report what compile-time options

 ** SQLite was built with.

 */

 #ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS

 /*

 ** Include the configuration header output by 'configure' if we're using the

 ** autoconf-based build

 */

 #if defined(_HAVE_SQLITE_CONFIG_H) && !defined(SQLITECONFIG_H)

 #include "config.h"

 #define SQLITECONFIG_H 1

 #endif

 /* These macros are provided to "stringify" the value of the define

 ** for those options in which the value is meaningful. */

 #define CTIMEOPT_VAL_(opt) #opt

 #define CTIMEOPT_VAL(opt) CTIMEOPT_VAL_(opt)

 /* Like CTIMEOPT_VAL, but especially for SQLITE_DEFAULT_LOOKASIDE. This

 ** option requires a separate macro because legal values contain a single

 ** comma. e.g. (-DSQLITE_DEFAULT_LOOKASIDE="100,100") */

 #define CTIMEOPT_VAL2_(opt1,opt2) #opt1 "," #opt2

 #define CTIMEOPT_VAL2(opt) CTIMEOPT_VAL2_(opt)

 /*

 ** An array of names of all compile-time options.  This array should 

 ** be sorted A-Z.

 **

 ** This array looks large, but in a typical installation actually uses

 ** only a handful of compile-time options, so most times this array is usually

 ** rather short and uses little memory space.

 */

 static const char * const sqlite3azCompileOpt[] = {

 /* 

 ** BEGIN CODE GENERATED BY tool/mkctime.tcl 

 */

 #if SQLITE_32BIT_ROWID

   "32BIT_ROWID",

 #endif

 #if SQLITE_4_BYTE_ALIGNED_MALLOC

   "4_BYTE_ALIGNED_MALLOC",

 #endif

 #if SQLITE_64BIT_STATS

   "64BIT_STATS",

 #endif

 #if SQLITE_ALLOW_COVERING_INDEX_SCAN

   "ALLOW_COVERING_INDEX_SCAN",

 #endif

 #if SQLITE_ALLOW_URI_AUTHORITY

   "ALLOW_URI_AUTHORITY",

 #endif

 #ifdef SQLITE_BITMASK_TYPE

   "BITMASK_TYPE=" CTIMEOPT_VAL(SQLITE_BITMASK_TYPE),

 #endif

 #if SQLITE_BUG_COMPATIBLE_20160819

   "BUG_COMPATIBLE_20160819",

 #endif

 #if SQLITE_CASE_SENSITIVE_LIKE

   "CASE_SENSITIVE_LIKE",

 #endif

 #if SQLITE_CHECK_PAGES

   "CHECK_PAGES",

 #endif

 #if defined(__clang__) && defined(__clang_major__)

   "COMPILER=clang-" CTIMEOPT_VAL(__clang_major__) "."

                     CTIMEOPT_VAL(__clang_minor__) "."

                     CTIMEOPT_VAL(__clang_patchlevel__),

 #elif defined(_MSC_VER)

   "COMPILER=msvc-" CTIMEOPT_VAL(_MSC_VER),

 #elif defined(__GNUC__) && defined(__VERSION__)

   "COMPILER=gcc-" __VERSION__,

 #endif

 #if SQLITE_COVERAGE_TEST

   "COVERAGE_TEST",

 #endif

 #if SQLITE_DEBUG

   "DEBUG",

 #endif

 #if SQLITE_DEFAULT_AUTOMATIC_INDEX

   "DEFAULT_AUTOMATIC_INDEX",

 #endif

 #if SQLITE_DEFAULT_AUTOVACUUM

   "DEFAULT_AUTOVACUUM",

 #endif

 #ifdef SQLITE_DEFAULT_CACHE_SIZE

   "DEFAULT_CACHE_SIZE=" CTIMEOPT_VAL(SQLITE_DEFAULT_CACHE_SIZE),

 #endif

 #if SQLITE_DEFAULT_CKPTFULLFSYNC

   "DEFAULT_CKPTFULLFSYNC",

 #endif

 #ifdef SQLITE_DEFAULT_FILE_FORMAT

   "DEFAULT_FILE_FORMAT=" CTIMEOPT_VAL(SQLITE_DEFAULT_FILE_FORMAT),

 #endif

 #ifdef SQLITE_DEFAULT_FILE_PERMISSIONS

   "DEFAULT_FILE_PERMISSIONS=" CTIMEOPT_VAL(SQLITE_DEFAULT_FILE_PERMISSIONS),

 #endif

 #if SQLITE_DEFAULT_FOREIGN_KEYS

   "DEFAULT_FOREIGN_KEYS",

 #endif

 #ifdef SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT

   "DEFAULT_JOURNAL_SIZE_LIMIT=" CTIMEOPT_VAL(SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT),

 #endif

 #ifdef SQLITE_DEFAULT_LOCKING_MODE

   "DEFAULT_LOCKING_MODE=" CTIMEOPT_VAL(SQLITE_DEFAULT_LOCKING_MODE),

 #endif

 #ifdef SQLITE_DEFAULT_LOOKASIDE

   "DEFAULT_LOOKASIDE=" CTIMEOPT_VAL2(SQLITE_DEFAULT_LOOKASIDE),

 #endif

 #if SQLITE_DEFAULT_MEMSTATUS

   "DEFAULT_MEMSTATUS",

 #endif

 #ifdef SQLITE_DEFAULT_MMAP_SIZE

   "DEFAULT_MMAP_SIZE=" CTIMEOPT_VAL(SQLITE_DEFAULT_MMAP_SIZE),

 #endif

 #ifdef SQLITE_DEFAULT_PAGE_SIZE

   "DEFAULT_PAGE_SIZE=" CTIMEOPT_VAL(SQLITE_DEFAULT_PAGE_SIZE),

 #endif

 #ifdef SQLITE_DEFAULT_PCACHE_INITSZ

   "DEFAULT_PCACHE_INITSZ=" CTIMEOPT_VAL(SQLITE_DEFAULT_PCACHE_INITSZ),

 #endif

 #ifdef SQLITE_DEFAULT_PROXYDIR_PERMISSIONS

   "DEFAULT_PROXYDIR_PERMISSIONS=" CTIMEOPT_VAL(SQLITE_DEFAULT_PROXYDIR_PERMISSIONS),

 #endif

 #if SQLITE_DEFAULT_RECURSIVE_TRIGGERS

   "DEFAULT_RECURSIVE_TRIGGERS",

 #endif

 #ifdef SQLITE_DEFAULT_ROWEST

   "DEFAULT_ROWEST=" CTIMEOPT_VAL(SQLITE_DEFAULT_ROWEST),

 #endif

 #ifdef SQLITE_DEFAULT_SECTOR_SIZE

   "DEFAULT_SECTOR_SIZE=" CTIMEOPT_VAL(SQLITE_DEFAULT_SECTOR_SIZE),

 #endif

 #ifdef SQLITE_DEFAULT_SYNCHRONOUS

   "DEFAULT_SYNCHRONOUS=" CTIMEOPT_VAL(SQLITE_DEFAULT_SYNCHRONOUS),

 #endif

 #ifdef SQLITE_DEFAULT_WAL_AUTOCHECKPOINT

   "DEFAULT_WAL_AUTOCHECKPOINT=" CTIMEOPT_VAL(SQLITE_DEFAULT_WAL_AUTOCHECKPOINT),

 #endif

 #ifdef SQLITE_DEFAULT_WAL_SYNCHRONOUS

   "DEFAULT_WAL_SYNCHRONOUS=" CTIMEOPT_VAL(SQLITE_DEFAULT_WAL_SYNCHRONOUS),

 #endif

 #ifdef SQLITE_DEFAULT_WORKER_THREADS

   "DEFAULT_WORKER_THREADS=" CTIMEOPT_VAL(SQLITE_DEFAULT_WORKER_THREADS),

 #endif

 #if SQLITE_DIRECT_OVERFLOW_READ

   "DIRECT_OVERFLOW_READ",

 #endif

 #if SQLITE_DISABLE_DIRSYNC

   "DISABLE_DIRSYNC",

 #endif

 #if SQLITE_DISABLE_FTS3_UNICODE

   "DISABLE_FTS3_UNICODE",

 #endif

 #if SQLITE_DISABLE_FTS4_DEFERRED

   "DISABLE_FTS4_DEFERRED",

 #endif

 #if SQLITE_DISABLE_INTRINSIC

   "DISABLE_INTRINSIC",

 #endif

 #if SQLITE_DISABLE_LFS

   "DISABLE_LFS",

 #endif

 #if SQLITE_DISABLE_PAGECACHE_OVERFLOW_STATS

   "DISABLE_PAGECACHE_OVERFLOW_STATS",

 #endif

 #if SQLITE_DISABLE_SKIPAHEAD_DISTINCT

   "DISABLE_SKIPAHEAD_DISTINCT",

 #endif

 #ifdef SQLITE_ENABLE_8_3_NAMES

   "ENABLE_8_3_NAMES=" CTIMEOPT_VAL(SQLITE_ENABLE_8_3_NAMES),

 #endif

 #if SQLITE_ENABLE_API_ARMOR

   "ENABLE_API_ARMOR",

 #endif

 #if SQLITE_ENABLE_ATOMIC_WRITE

   "ENABLE_ATOMIC_WRITE",

 #endif

 #if SQLITE_ENABLE_BATCH_ATOMIC_WRITE

   "ENABLE_BATCH_ATOMIC_WRITE",

 #endif

 #if SQLITE_ENABLE_CEROD

   "ENABLE_CEROD=" CTIMEOPT_VAL(SQLITE_ENABLE_CEROD),

 #endif

 #if SQLITE_ENABLE_COLUMN_METADATA

   "ENABLE_COLUMN_METADATA",

 #endif

 #if SQLITE_ENABLE_COLUMN_USED_MASK

   "ENABLE_COLUMN_USED_MASK",

 #endif

 #if SQLITE_ENABLE_COSTMULT

   "ENABLE_COSTMULT",

 #endif

 #if SQLITE_ENABLE_CURSOR_HINTS

   "ENABLE_CURSOR_HINTS",

 #endif

 #if SQLITE_ENABLE_DBSTAT_VTAB

   "ENABLE_DBSTAT_VTAB",

 #endif

 #if SQLITE_ENABLE_EXPENSIVE_ASSERT

   "ENABLE_EXPENSIVE_ASSERT",

 #endif

 #if SQLITE_ENABLE_FTS1

   "ENABLE_FTS1",

 #endif

 #if SQLITE_ENABLE_FTS2

   "ENABLE_FTS2",

 #endif

 #if SQLITE_ENABLE_FTS3

   "ENABLE_FTS3",

 #endif

 #if SQLITE_ENABLE_FTS3_PARENTHESIS

   "ENABLE_FTS3_PARENTHESIS",

 #endif

 #if SQLITE_ENABLE_FTS3_TOKENIZER

   "ENABLE_FTS3_TOKENIZER",

 #endif

 #if SQLITE_ENABLE_FTS4

   "ENABLE_FTS4",

 #endif

 #if SQLITE_ENABLE_FTS5

   "ENABLE_FTS5",

 #endif

 #if SQLITE_ENABLE_GEOPOLY

   "ENABLE_GEOPOLY",

 #endif

 #if SQLITE_ENABLE_HIDDEN_COLUMNS

   "ENABLE_HIDDEN_COLUMNS",

 #endif

 #if SQLITE_ENABLE_ICU

   "ENABLE_ICU",

 #endif

 #if SQLITE_ENABLE_IOTRACE

   "ENABLE_IOTRACE",

 #endif

 #if SQLITE_ENABLE_JSON1

   "ENABLE_JSON1",

 #endif

 #if SQLITE_ENABLE_LOAD_EXTENSION

   "ENABLE_LOAD_EXTENSION",

 #endif

 #ifdef SQLITE_ENABLE_LOCKING_STYLE

   "ENABLE_LOCKING_STYLE=" CTIMEOPT_VAL(SQLITE_ENABLE_LOCKING_STYLE),

 #endif

 #if SQLITE_ENABLE_MEMORY_MANAGEMENT

   "ENABLE_MEMORY_MANAGEMENT",

 #endif

 #if SQLITE_ENABLE_MEMSYS3

   "ENABLE_MEMSYS3",

 #endif

 #if SQLITE_ENABLE_MEMSYS5

   "ENABLE_MEMSYS5",

 #endif

 #if SQLITE_ENABLE_MULTIPLEX

   "ENABLE_MULTIPLEX",

 #endif

 #if SQLITE_ENABLE_NORMALIZE

   "ENABLE_NORMALIZE",

 #endif

 #if SQLITE_ENABLE_NULL_TRIM

   "ENABLE_NULL_TRIM",

 #endif

 #if SQLITE_ENABLE_OVERSIZE_CELL_CHECK

   "ENABLE_OVERSIZE_CELL_CHECK",

 #endif

 #if SQLITE_ENABLE_PREUPDATE_HOOK

   "ENABLE_PREUPDATE_HOOK",

 #endif

 #if SQLITE_ENABLE_QPSG

   "ENABLE_QPSG",

 #endif

 #if SQLITE_ENABLE_RBU

   "ENABLE_RBU",

 #endif

 #if SQLITE_ENABLE_RTREE

   "ENABLE_RTREE",

 #endif

 #if SQLITE_ENABLE_SELECTTRACE

   "ENABLE_SELECTTRACE",

 #endif

 #if SQLITE_ENABLE_SESSION

   "ENABLE_SESSION",

 #endif

 #if SQLITE_ENABLE_SNAPSHOT

   "ENABLE_SNAPSHOT",

 #endif

 #if SQLITE_ENABLE_SORTER_REFERENCES

   "ENABLE_SORTER_REFERENCES",

 #endif

 #if SQLITE_ENABLE_SQLLOG

   "ENABLE_SQLLOG",

 #endif

 #if defined(SQLITE_ENABLE_STAT4)

   "ENABLE_STAT4",

 #elif defined(SQLITE_ENABLE_STAT3)

   "ENABLE_STAT3",

 #endif

 #if SQLITE_ENABLE_STMTVTAB

   "ENABLE_STMTVTAB",

 #endif

 #if SQLITE_ENABLE_STMT_SCANSTATUS

   "ENABLE_STMT_SCANSTATUS",

 #endif

 #if SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION

   "ENABLE_UNKNOWN_SQL_FUNCTION",

 #endif

 #if SQLITE_ENABLE_UNLOCK_NOTIFY

   "ENABLE_UNLOCK_NOTIFY",

 #endif

 #if SQLITE_ENABLE_UPDATE_DELETE_LIMIT

   "ENABLE_UPDATE_DELETE_LIMIT",

 #endif

 #if SQLITE_ENABLE_URI_00_ERROR

   "ENABLE_URI_00_ERROR",

 #endif

 #if SQLITE_ENABLE_VFSTRACE

   "ENABLE_VFSTRACE",

 #endif

 #if SQLITE_ENABLE_WHERETRACE

   "ENABLE_WHERETRACE",

 #endif

 #if SQLITE_ENABLE_ZIPVFS

   "ENABLE_ZIPVFS",

 #endif

 #if SQLITE_EXPLAIN_ESTIMATED_ROWS

   "EXPLAIN_ESTIMATED_ROWS",

 #endif

 #if SQLITE_EXTRA_IFNULLROW

   "EXTRA_IFNULLROW",

 #endif

 #ifdef SQLITE_EXTRA_INIT

   "EXTRA_INIT=" CTIMEOPT_VAL(SQLITE_EXTRA_INIT),

 #endif

 #ifdef SQLITE_EXTRA_SHUTDOWN

   "EXTRA_SHUTDOWN=" CTIMEOPT_VAL(SQLITE_EXTRA_SHUTDOWN),

 #endif

 #ifdef SQLITE_FTS3_MAX_EXPR_DEPTH

   "FTS3_MAX_EXPR_DEPTH=" CTIMEOPT_VAL(SQLITE_FTS3_MAX_EXPR_DEPTH),

 #endif

 #if SQLITE_FTS5_ENABLE_TEST_MI

   "FTS5_ENABLE_TEST_MI",

 #endif

 #if SQLITE_FTS5_NO_WITHOUT_ROWID

   "FTS5_NO_WITHOUT_ROWID",

 #endif

 #if SQLITE_HAS_CODEC

   "HAS_CODEC",

 #endif

 #if HAVE_ISNAN || SQLITE_HAVE_ISNAN

   "HAVE_ISNAN",

 #endif

 #if SQLITE_HOMEGROWN_RECURSIVE_MUTEX

   "HOMEGROWN_RECURSIVE_MUTEX",

 #endif

 #if SQLITE_IGNORE_AFP_LOCK_ERRORS

   "IGNORE_AFP_LOCK_ERRORS",

 #endif

 #if SQLITE_IGNORE_FLOCK_LOCK_ERRORS

   "IGNORE_FLOCK_LOCK_ERRORS",

 #endif

 #if SQLITE_INLINE_MEMCPY

   "INLINE_MEMCPY",

 #endif

 #if SQLITE_INT64_TYPE

   "INT64_TYPE",

 #endif

 #ifdef SQLITE_INTEGRITY_CHECK_ERROR_MAX

   "INTEGRITY_CHECK_ERROR_MAX=" CTIMEOPT_VAL(SQLITE_INTEGRITY_CHECK_ERROR_MAX),

 #endif

 #if SQLITE_LIKE_DOESNT_MATCH_BLOBS

   "LIKE_DOESNT_MATCH_BLOBS",

 #endif

 #if SQLITE_LOCK_TRACE

   "LOCK_TRACE",

 #endif

 #if SQLITE_LOG_CACHE_SPILL

   "LOG_CACHE_SPILL",

 #endif

 #ifdef SQLITE_MALLOC_SOFT_LIMIT

   "MALLOC_SOFT_LIMIT=" CTIMEOPT_VAL(SQLITE_MALLOC_SOFT_LIMIT),

 #endif

 #ifdef SQLITE_MAX_ATTACHED

   "MAX_ATTACHED=" CTIMEOPT_VAL(SQLITE_MAX_ATTACHED),

 #endif

 #ifdef SQLITE_MAX_COLUMN

   "MAX_COLUMN=" CTIMEOPT_VAL(SQLITE_MAX_COLUMN),

 #endif

 #ifdef SQLITE_MAX_COMPOUND_SELECT

   "MAX_COMPOUND_SELECT=" CTIMEOPT_VAL(SQLITE_MAX_COMPOUND_SELECT),

 #endif

 #ifdef SQLITE_MAX_DEFAULT_PAGE_SIZE

   "MAX_DEFAULT_PAGE_SIZE=" CTIMEOPT_VAL(SQLITE_MAX_DEFAULT_PAGE_SIZE),

 #endif

 #ifdef SQLITE_MAX_EXPR_DEPTH

   "MAX_EXPR_DEPTH=" CTIMEOPT_VAL(SQLITE_MAX_EXPR_DEPTH),

 #endif

 #ifdef SQLITE_MAX_FUNCTION_ARG

   "MAX_FUNCTION_ARG=" CTIMEOPT_VAL(SQLITE_MAX_FUNCTION_ARG),

 #endif

 #ifdef SQLITE_MAX_LENGTH

   "MAX_LENGTH=" CTIMEOPT_VAL(SQLITE_MAX_LENGTH),

 #endif

 #ifdef SQLITE_MAX_LIKE_PATTERN_LENGTH

   "MAX_LIKE_PATTERN_LENGTH=" CTIMEOPT_VAL(SQLITE_MAX_LIKE_PATTERN_LENGTH),

 #endif

 #ifdef SQLITE_MAX_MEMORY

   "MAX_MEMORY=" CTIMEOPT_VAL(SQLITE_MAX_MEMORY),

 #endif

 #ifdef SQLITE_MAX_MMAP_SIZE

   "MAX_MMAP_SIZE=" CTIMEOPT_VAL(SQLITE_MAX_MMAP_SIZE),

 #endif

 #ifdef SQLITE_MAX_MMAP_SIZE_

   "MAX_MMAP_SIZE_=" CTIMEOPT_VAL(SQLITE_MAX_MMAP_SIZE_),

 #endif

 #ifdef SQLITE_MAX_PAGE_COUNT

   "MAX_PAGE_COUNT=" CTIMEOPT_VAL(SQLITE_MAX_PAGE_COUNT),

 #endif

 #ifdef SQLITE_MAX_PAGE_SIZE

   "MAX_PAGE_SIZE=" CTIMEOPT_VAL(SQLITE_MAX_PAGE_SIZE),

 #endif

 #ifdef SQLITE_MAX_SCHEMA_RETRY

   "MAX_SCHEMA_RETRY=" CTIMEOPT_VAL(SQLITE_MAX_SCHEMA_RETRY),

 #endif

 #ifdef SQLITE_MAX_SQL_LENGTH

   "MAX_SQL_LENGTH=" CTIMEOPT_VAL(SQLITE_MAX_SQL_LENGTH),

 #endif

 #ifdef SQLITE_MAX_TRIGGER_DEPTH

   "MAX_TRIGGER_DEPTH=" CTIMEOPT_VAL(SQLITE_MAX_TRIGGER_DEPTH),

 #endif

 #ifdef SQLITE_MAX_VARIABLE_NUMBER

   "MAX_VARIABLE_NUMBER=" CTIMEOPT_VAL(SQLITE_MAX_VARIABLE_NUMBER),

 #endif

 #ifdef SQLITE_MAX_VDBE_OP

   "MAX_VDBE_OP=" CTIMEOPT_VAL(SQLITE_MAX_VDBE_OP),

 #endif

 #ifdef SQLITE_MAX_WORKER_THREADS

   "MAX_WORKER_THREADS=" CTIMEOPT_VAL(SQLITE_MAX_WORKER_THREADS),

 #endif

 #if SQLITE_MEMDEBUG

   "MEMDEBUG",

 #endif

 #if SQLITE_MIXED_ENDIAN_64BIT_FLOAT

   "MIXED_ENDIAN_64BIT_FLOAT",

 #endif

 #if SQLITE_MMAP_READWRITE

   "MMAP_READWRITE",

 #endif

 #if SQLITE_MUTEX_NOOP

   "MUTEX_NOOP",

 #endif

 #if SQLITE_MUTEX_NREF

   "MUTEX_NREF",

 #endif

 #if SQLITE_MUTEX_OMIT

   "MUTEX_OMIT",

 #endif

 #if SQLITE_MUTEX_PTHREADS

   "MUTEX_PTHREADS",

 #endif

 #if SQLITE_MUTEX_W32

   "MUTEX_W32",

 #endif

 #if SQLITE_NEED_ERR_NAME

   "NEED_ERR_NAME",

 #endif

 #if SQLITE_NOINLINE

   "NOINLINE",

 #endif

 #if SQLITE_NO_SYNC

   "NO_SYNC",

 #endif

 #if SQLITE_OMIT_ALTERTABLE

   "OMIT_ALTERTABLE",

 #endif

 #if SQLITE_OMIT_ANALYZE

   "OMIT_ANALYZE",

 #endif

 #if SQLITE_OMIT_ATTACH

   "OMIT_ATTACH",

 #endif

 #if SQLITE_OMIT_AUTHORIZATION

   "OMIT_AUTHORIZATION",

 #endif

 #if SQLITE_OMIT_AUTOINCREMENT

   "OMIT_AUTOINCREMENT",

 #endif

 #if SQLITE_OMIT_AUTOINIT

   "OMIT_AUTOINIT",

 #endif

 #if SQLITE_OMIT_AUTOMATIC_INDEX

   "OMIT_AUTOMATIC_INDEX",

 #endif

 #if SQLITE_OMIT_AUTORESET

   "OMIT_AUTORESET",

 #endif

 #if SQLITE_OMIT_AUTOVACUUM

   "OMIT_AUTOVACUUM",

 #endif

 #if SQLITE_OMIT_BETWEEN_OPTIMIZATION

   "OMIT_BETWEEN_OPTIMIZATION",

 #endif

 #if SQLITE_OMIT_BLOB_LITERAL

   "OMIT_BLOB_LITERAL",

 #endif

 #if SQLITE_OMIT_BTREECOUNT

   "OMIT_BTREECOUNT",

 #endif

 #if SQLITE_OMIT_CAST

   "OMIT_CAST",

 #endif

 #if SQLITE_OMIT_CHECK

   "OMIT_CHECK",

 #endif

 #if SQLITE_OMIT_COMPLETE

   "OMIT_COMPLETE",

 #endif

 #if SQLITE_OMIT_COMPOUND_SELECT

   "OMIT_COMPOUND_SELECT",

 #endif

 #if SQLITE_OMIT_CONFLICT_CLAUSE

   "OMIT_CONFLICT_CLAUSE",

 #endif

 #if SQLITE_OMIT_CTE

   "OMIT_CTE",

 #endif

 #if SQLITE_OMIT_DATETIME_FUNCS

   "OMIT_DATETIME_FUNCS",

 #endif

 #if SQLITE_OMIT_DECLTYPE

   "OMIT_DECLTYPE",

 #endif

 #if SQLITE_OMIT_DEPRECATED

   "OMIT_DEPRECATED",

 #endif

 #if SQLITE_OMIT_DISKIO

   "OMIT_DISKIO",

 #endif

 #if SQLITE_OMIT_EXPLAIN

   "OMIT_EXPLAIN",

 #endif

 #if SQLITE_OMIT_FLAG_PRAGMAS

   "OMIT_FLAG_PRAGMAS",

 #endif

 #if SQLITE_OMIT_FLOATING_POINT

   "OMIT_FLOATING_POINT",

 #endif

 #if SQLITE_OMIT_FOREIGN_KEY

   "OMIT_FOREIGN_KEY",

 #endif

 #if SQLITE_OMIT_GET_TABLE

   "OMIT_GET_TABLE",

 #endif

 #if SQLITE_OMIT_HEX_INTEGER

   "OMIT_HEX_INTEGER",

 #endif

 #if SQLITE_OMIT_INCRBLOB

   "OMIT_INCRBLOB",

 #endif

 #if SQLITE_OMIT_INTEGRITY_CHECK

   "OMIT_INTEGRITY_CHECK",

 #endif

 #if SQLITE_OMIT_LIKE_OPTIMIZATION

   "OMIT_LIKE_OPTIMIZATION",

 #endif

 #if SQLITE_OMIT_LOAD_EXTENSION

   "OMIT_LOAD_EXTENSION",

 #endif

 #if SQLITE_OMIT_LOCALTIME

   "OMIT_LOCALTIME",

 #endif

 #if SQLITE_OMIT_LOOKASIDE

   "OMIT_LOOKASIDE",

 #endif

 #if SQLITE_OMIT_MEMORYDB

   "OMIT_MEMORYDB",

 #endif

 #if SQLITE_OMIT_OR_OPTIMIZATION

   "OMIT_OR_OPTIMIZATION",

 #endif

 #if SQLITE_OMIT_PAGER_PRAGMAS

   "OMIT_PAGER_PRAGMAS",

 #endif

 #if SQLITE_OMIT_PARSER_TRACE

   "OMIT_PARSER_TRACE",

 #endif

 #if SQLITE_OMIT_POPEN

   "OMIT_POPEN",

 #endif

 #if SQLITE_OMIT_PRAGMA

   "OMIT_PRAGMA",

 #endif

 #if SQLITE_OMIT_PROGRESS_CALLBACK

   "OMIT_PROGRESS_CALLBACK",

 #endif

 #if SQLITE_OMIT_QUICKBALANCE

   "OMIT_QUICKBALANCE",

 #endif

 #if SQLITE_OMIT_REINDEX

   "OMIT_REINDEX",

 #endif

 #if SQLITE_OMIT_SCHEMA_PRAGMAS

   "OMIT_SCHEMA_PRAGMAS",

 #endif

 #if SQLITE_OMIT_SCHEMA_VERSION_PRAGMAS

   "OMIT_SCHEMA_VERSION_PRAGMAS",

 #endif

 #if SQLITE_OMIT_SHARED_CACHE

   "OMIT_SHARED_CACHE",

 #endif

 #if SQLITE_OMIT_SHUTDOWN_DIRECTORIES

   "OMIT_SHUTDOWN_DIRECTORIES",

 #endif

 #if SQLITE_OMIT_SUBQUERY

   "OMIT_SUBQUERY",

 #endif

 #if SQLITE_OMIT_TCL_VARIABLE

   "OMIT_TCL_VARIABLE",

 #endif

 #if SQLITE_OMIT_TEMPDB

   "OMIT_TEMPDB",

 #endif

 #if SQLITE_OMIT_TEST_CONTROL

   "OMIT_TEST_CONTROL",

 #endif

 #if SQLITE_OMIT_TRACE

   "OMIT_TRACE",

 #endif

 #if SQLITE_OMIT_TRIGGER

   "OMIT_TRIGGER",

 #endif

 #if SQLITE_OMIT_TRUNCATE_OPTIMIZATION

   "OMIT_TRUNCATE_OPTIMIZATION",

 #endif

 #if SQLITE_OMIT_UTF16

   "OMIT_UTF16",

 #endif

 #if SQLITE_OMIT_VACUUM

   "OMIT_VACUUM",

 #endif

 #if SQLITE_OMIT_VIEW

   "OMIT_VIEW",

 #endif

 #if SQLITE_OMIT_VIRTUALTABLE

   "OMIT_VIRTUALTABLE",

 #endif

 #if SQLITE_OMIT_WAL

   "OMIT_WAL",

 #endif

 #if SQLITE_OMIT_WSD

   "OMIT_WSD",

 #endif

 #if SQLITE_OMIT_XFER_OPT

   "OMIT_XFER_OPT",

 #endif

 #if SQLITE_PCACHE_SEPARATE_HEADER

   "PCACHE_SEPARATE_HEADER",

 #endif

 #if SQLITE_PERFORMANCE_TRACE

   "PERFORMANCE_TRACE",

 #endif

 #if SQLITE_POWERSAFE_OVERWRITE

   "POWERSAFE_OVERWRITE",

 #endif

 #if SQLITE_PREFER_PROXY_LOCKING

   "PREFER_PROXY_LOCKING",

 #endif

 #if SQLITE_PROXY_DEBUG

   "PROXY_DEBUG",

 #endif

 #if SQLITE_REVERSE_UNORDERED_SELECTS

   "REVERSE_UNORDERED_SELECTS",

 #endif

 #if SQLITE_RTREE_INT_ONLY

   "RTREE_INT_ONLY",

 #endif

 #if SQLITE_SECURE_DELETE

   "SECURE_DELETE",

 #endif

 #if SQLITE_SMALL_STACK

   "SMALL_STACK",

 #endif

 #ifdef SQLITE_SORTER_PMASZ

   "SORTER_PMASZ=" CTIMEOPT_VAL(SQLITE_SORTER_PMASZ),

 #endif

 #if SQLITE_SOUNDEX

   "SOUNDEX",

 #endif

 #ifdef SQLITE_STAT4_SAMPLES

   "STAT4_SAMPLES=" CTIMEOPT_VAL(SQLITE_STAT4_SAMPLES),

 #endif

 #ifdef SQLITE_STMTJRNL_SPILL

   "STMTJRNL_SPILL=" CTIMEOPT_VAL(SQLITE_STMTJRNL_SPILL),

 #endif

 #if SQLITE_SUBSTR_COMPATIBILITY

   "SUBSTR_COMPATIBILITY",

 #endif

 #if SQLITE_SYSTEM_MALLOC

   "SYSTEM_MALLOC",

 #endif

 #if SQLITE_TCL

   "TCL",

 #endif

 #ifdef SQLITE_TEMP_STORE

   "TEMP_STORE=" CTIMEOPT_VAL(SQLITE_TEMP_STORE),

 #endif

 #if SQLITE_TEST

   "TEST",

 #endif

 #if defined(SQLITE_THREADSAFE)

   "THREADSAFE=" CTIMEOPT_VAL(SQLITE_THREADSAFE),

 #elif defined(THREADSAFE)

   "THREADSAFE=" CTIMEOPT_VAL(THREADSAFE),

 #else

   "THREADSAFE=1",

 #endif

 #if SQLITE_UNLINK_AFTER_CLOSE

   "UNLINK_AFTER_CLOSE",

 #endif

 #if SQLITE_UNTESTABLE

   "UNTESTABLE",

 #endif

 #if SQLITE_USER_AUTHENTICATION

   "USER_AUTHENTICATION",

 #endif

 #if SQLITE_USE_ALLOCA

   "USE_ALLOCA",

 #endif

 #if SQLITE_USE_FCNTL_TRACE

   "USE_FCNTL_TRACE",

 #endif

 #if SQLITE_USE_URI

   "USE_URI",

 #endif

 #if SQLITE_VDBE_COVERAGE

   "VDBE_COVERAGE",

 #endif

 #if SQLITE_WIN32_MALLOC

   "WIN32_MALLOC",

 #endif

 #if SQLITE_ZERO_MALLOC

   "ZERO_MALLOC",

 #endif

 /* 

 ** END CODE GENERATED BY tool/mkctime.tcl 

 */

 };

 SQLITE_PRIVATE const char **sqlite3CompileOptions(int *pnOpt){

   *pnOpt = sizeof(sqlite3azCompileOpt) / sizeof(sqlite3azCompileOpt[0]);

   return (const char**)sqlite3azCompileOpt;

 }

 #endif /* SQLITE_OMIT_COMPILEOPTION_DIAGS */

 /************** End of ctime.c ***********************************************/

 /************** Begin file sqliteInt.h ***************************************/

 /*

 ** 2001 September 15

 **

 ** The author disclaims copyright to this source code.  In place of

 ** a legal notice, here is a blessing:

 **

 **    May you do good and not evil.

 **    May you find forgiveness for yourself and forgive others.

 **    May you share freely, never taking more than you give.

 **

 *************************************************************************

 ** Internal interface definitions for SQLite.

 **

 */

 #ifndef SQLITEINT_H

 #define SQLITEINT_H

 /* Special Comments:

 **

 ** Some comments have special meaning to the tools that measure test

 ** coverage:

 **

 **    NO_TEST                     - The branches on this line are not

 **                                  measured by branch coverage.  This is

 **                                  used on lines of code that actually

 **                                  implement parts of coverage testing.

 **

 **    OPTIMIZATION-IF-TRUE        - This branch is allowed to alway be false

 **                                  and the correct answer is still obtained,

 **                                  though perhaps more slowly.

 **

 **    OPTIMIZATION-IF-FALSE       - This branch is allowed to alway be true

 **                                  and the correct answer is still obtained,

 **                                  though perhaps more slowly.

 **

 **    PREVENTS-HARMLESS-OVERREAD  - This branch prevents a buffer overread

 **                                  that would be harmless and undetectable

 **                                  if it did occur.  

 **

 ** In all cases, the special comment must be enclosed in the usual

 ** slash-asterisk...asterisk-slash comment marks, with no spaces between the 

 ** asterisks and the comment text.

 */

 /*

 ** Make sure the Tcl calling convention macro is defined.  This macro is

 ** only used by test code and Tcl integration code.

 */

 #ifndef SQLITE_TCLAPI

 #  define SQLITE_TCLAPI

 #endif

 /*

 ** Include the header file used to customize the compiler options for MSVC.

 ** This should be done first so that it can successfully prevent spurious

 ** compiler warnings due to subsequent content in this file and other files

 ** that are included by this file.

 */

 /************** Include msvc.h in the middle of sqliteInt.h ******************/

 /************** Begin file msvc.h ********************************************/

 /*

 ** 2015 January 12

 **

 ** The author disclaims copyright to this source code.  In place of

 ** a legal notice, here is a blessing:

 **

 **    May you do good and not evil.

 **    May you find forgiveness for yourself and forgive others.

 **    May you share freely, never taking more than you give.

 **

 ******************************************************************************

 **

 ** This file contains code that is specific to MSVC.

 */

 #ifndef SQLITE_MSVC_H

 #define SQLITE_MSVC_H

 #if defined(_MSC_VER)

 #pragma warning(disable : 4054)

 #pragma warning(disable : 4055)

 #pragma warning(disable : 4100)

 #pragma warning(disable : 4127)

 #pragma warning(disable : 4130)

 #pragma warning(disable : 4152)

 #pragma warning(disable : 4189)

 #pragma warning(disable : 4206)

 #pragma warning(disable : 4210)

 #pragma warning(disable : 4232)

 #pragma warning(disable : 4244)

 #pragma warning(disable : 4305)

 #pragma warning(disable : 4306)

 #pragma warning(disable : 4702)

 #pragma warning(disable : 4706)

 #endif /* defined(_MSC_VER) */

 #endif /* SQLITE_MSVC_H */

 /************** End of msvc.h ************************************************/

 /************** Continuing where we left off in sqliteInt.h ******************/

 /*

 ** Special setup for VxWorks

 */

 /************** Include vxworks.h in the middle of sqliteInt.h ***************/

 /************** Begin file vxworks.h *****************************************/

 /*

 ** 2015-03-02

 **

 ** The author disclaims copyright to this source code.  In place of

 ** a legal notice, here is a blessing:

 **

 **    May you do good and not evil.

 **    May you find forgiveness for yourself and forgive others.

 **    May you share freely, never taking more than you give.

 **

 ******************************************************************************

 **

 ** This file contains code that is specific to Wind River's VxWorks

 */

 #if defined(__RTP__) || defined(_WRS_KERNEL)

 /* This is VxWorks.  Set up things specially for that OS

 */

 #include <vxWorks.h>

 #include <pthread.h>  /* amalgamator: dontcache */

 #define OS_VXWORKS 1

 #define SQLITE_OS_OTHER 0

 #define SQLITE_HOMEGROWN_RECURSIVE_MUTEX 1

 #define SQLITE_OMIT_LOAD_EXTENSION 1

 #define SQLITE_ENABLE_LOCKING_STYLE 0

 #define HAVE_UTIME 1

 #else

 /* This is not VxWorks. */

 #define OS_VXWORKS 0

 #define HAVE_FCHOWN 1

 #define HAVE_READLINK 1

 #define HAVE_LSTAT 1

 #endif /* defined(_WRS_KERNEL) */

 /************** End of vxworks.h *********************************************/

 /************** Continuing where we left off in sqliteInt.h ******************/

 /*

 ** These #defines should enable >2GB file support on POSIX if the

 ** underlying operating system supports it.  If the OS lacks

 ** large file support, or if the OS is windows, these should be no-ops.

 **

 ** Ticket #2739:  The _LARGEFILE_SOURCE macro must appear before any

 ** system #includes.  Hence, this block of code must be the very first

 ** code in all source files.

 **

 ** Large file support can be disabled using the -DSQLITE_DISABLE_LFS switch

 ** on the compiler command line.  This is necessary if you are compiling

 ** on a recent machine (ex: Red Hat 7.2) but you want your code to work

 ** on an older machine (ex: Red Hat 6.0).  If you compile on Red Hat 7.2

 ** without this option, LFS is enable.  But LFS does not exist in the kernel

 ** in Red Hat 6.0, so the code won't work.  Hence, for maximum binary

 ** portability you should omit LFS.

 **

 ** The previous paragraph was written in 2005.  (This paragraph is written

 ** on 2008-11-28.) These days, all Linux kernels support large files, so

 ** you should probably leave LFS enabled.  But some embedded platforms might

 ** lack LFS in which case the SQLITE_DISABLE_LFS macro might still be useful.

 **

 ** Similar is true for Mac OS X.  LFS is only supported on Mac OS X 9 and later.

 */

 #ifndef SQLITE_DISABLE_LFS

 # define _LARGE_FILE       1

 # ifndef _FILE_OFFSET_BITS

 #   define _FILE_OFFSET_BITS 64

 # endif

 # define _LARGEFILE_SOURCE 1

 #endif

 /* The GCC_VERSION and MSVC_VERSION macros are used to

 ** conditionally include optimizations for each of these compilers.  A

 ** value of 0 means that compiler is not being used.  The

 ** SQLITE_DISABLE_INTRINSIC macro means do not use any compiler-specific

 ** optimizations, and hence set all compiler macros to 0

 **

 ** There was once also a CLANG_VERSION macro.  However, we learn that the

 ** version numbers in clang are for "marketing" only and are inconsistent

 ** and unreliable.  Fortunately, all versions of clang also recognize the

 ** gcc version numbers and have reasonable settings for gcc version numbers,

 ** so the GCC_VERSION macro will be set to a correct non-zero value even

 ** when compiling with clang.

 */

 #if defined(__GNUC__) && !defined(SQLITE_DISABLE_INTRINSIC)

 # define GCC_VERSION (__GNUC__*1000000+__GNUC_MINOR__*1000+__GNUC_PATCHLEVEL__)

 #else

 # define GCC_VERSION 0

 #endif

 #if defined(_MSC_VER) && !defined(SQLITE_DISABLE_INTRINSIC)

 # define MSVC_VERSION _MSC_VER

 #else

 # define MSVC_VERSION 0

 #endif

 /* Needed for various definitions... */

 #if defined(__GNUC__) && !defined(_GNU_SOURCE)

 # define _GNU_SOURCE

 #endif

 #if defined(__OpenBSD__) && !defined(_BSD_SOURCE)

 # define _BSD_SOURCE

 #endif

 /*

 ** For MinGW, check to see if we can include the header file containing its

 ** version information, among other things.  Normally, this internal MinGW

 ** header file would [only] be included automatically by other MinGW header

 ** files; however, the contained version information is now required by this

 ** header file to work around binary compatibility issues (see below) and

 ** this is the only known way to reliably obtain it.  This entire #if block

 ** would be completely unnecessary if there was any other way of detecting

 ** MinGW via their preprocessor (e.g. if they customized their GCC to define

 ** some MinGW-specific macros).  When compiling for MinGW, either the

 ** _HAVE_MINGW_H or _HAVE__MINGW_H (note the extra underscore) macro must be

 ** defined; otherwise, detection of conditions specific to MinGW will be

 ** disabled.

 */

 #if defined(_HAVE_MINGW_H)

 # include "mingw.h"

 #elif defined(_HAVE__MINGW_H)

 # include "_mingw.h"

 #endif

 /*

 ** For MinGW version 4.x (and higher), check to see if the _USE_32BIT_TIME_T

 ** define is required to maintain binary compatibility with the MSVC runtime

 ** library in use (e.g. for Windows XP).

 */

 #if !defined(_USE_32BIT_TIME_T) && !defined(_USE_64BIT_TIME_T) && \

     defined(_WIN32) && !defined(_WIN64) && \

     defined(__MINGW_MAJOR_VERSION) && __MINGW_MAJOR_VERSION >= 4 && \

     defined(__MSVCRT__)

 # define _USE_32BIT_TIME_T

 #endif

 /* The public SQLite interface.  The _FILE_OFFSET_BITS macro must appear

 ** first in QNX.  Also, the _USE_32BIT_TIME_T macro must appear first for

 ** MinGW.

 */

 /************** Include sqlite3.h in the middle of sqliteInt.h ***************/

 /************** Begin file sqlite3.h *****************************************/

 /*

 ** 2001-09-15

 **

 ** The author disclaims copyright to this source code.  In place of

 ** a legal notice, here is a blessing:

 **

 **    May you do good and not evil.

 **    May you find forgiveness for yourself and forgive others.

 **    May you share freely, never taking more than you give.

 **

 *************************************************************************

 ** This header file defines the interface that the SQLite library

 ** presents to client programs.  If a C-function, structure, datatype,

 ** or constant definition does not appear in this file, then it is

 ** not a published API of SQLite, is subject to change without

 ** notice, and should not be referenced by programs that use SQLite.

 **

 ** Some of the definitions that are in this file are marked as

 ** "experimental".  Experimental interfaces are normally new

 ** features recently added to SQLite.  We do not anticipate changes

 ** to experimental interfaces but reserve the right to make minor changes

 ** if experience from use "in the wild" suggest such changes are prudent.

 **

 ** The official C-language API documentation for SQLite is derived

 ** from comments in this file.  This file is the authoritative source

 ** on how SQLite interfaces are supposed to operate.

 **

 ** The name of this file under configuration management is "sqlite.h.in".

 ** The makefile makes some minor changes to this file (such as inserting

 ** the version number) and changes its name to "sqlite3.h" as

 ** part of the build process.

 */

 #ifndef SQLITE3_H

 #define SQLITE3_H

 #include <stdarg.h>     /* Needed for the definition of va_list */

 /*

 ** Make sure we can call this stuff from C++.

 */

 #if 0

 extern "C" {

 #endif

 /*

 ** Provide the ability to override linkage features of the interface.

 */

 #ifndef SQLITE_EXTERN

 # define SQLITE_EXTERN extern

 #endif

 #ifndef SQLITE_API

 # define SQLITE_API

 #endif

 #ifndef SQLITE_CDECL

 # define SQLITE_CDECL

 #endif

 #ifndef SQLITE_APICALL

 # define SQLITE_APICALL

 #endif

 #ifndef SQLITE_STDCALL

 # define SQLITE_STDCALL SQLITE_APICALL

 #endif

 #ifndef SQLITE_CALLBACK

 # define SQLITE_CALLBACK

 #endif

 #ifndef SQLITE_SYSAPI

 # define SQLITE_SYSAPI

 #endif

 /*

 ** These no-op macros are used in front of interfaces to mark those

 ** interfaces as either deprecated or experimental.  New applications

 ** should not use deprecated interfaces - they are supported for backwards

 ** compatibility only.  Application writers should be aware that

 ** experimental interfaces are subject to change in point releases.

 **

 ** These macros used to resolve to various kinds of compiler magic that

 ** would generate warning messages when they were used.  But that

 ** compiler magic ended up generating such a flurry of bug reports

 ** that we have taken it all out and gone back to using simple

 ** noop macros.

 */

 #define SQLITE_DEPRECATED

 #define SQLITE_EXPERIMENTAL

 /*

 ** Ensure these symbols were not defined by some previous header file.

 */

 #ifdef SQLITE_VERSION

 # undef SQLITE_VERSION

 #endif

 #ifdef SQLITE_VERSION_NUMBER

 # undef SQLITE_VERSION_NUMBER

 #endif

 /*

 ** CAPI3REF: Compile-Time Library Version Numbers

 **

 ** ^(The [SQLITE_VERSION] C preprocessor macro in the sqlite3.h header

 ** evaluates to a string literal that is the SQLite version in the

 ** format "X.Y.Z" where X is the major version number (always 3 for

 ** SQLite3) and Y is the minor version number and Z is the release number.)^

 ** ^(The [SQLITE_VERSION_NUMBER] C preprocessor macro resolves to an integer

 ** with the value (X*1000000 + Y*1000 + Z) where X, Y, and Z are the same

 ** numbers used in [SQLITE_VERSION].)^

 ** The SQLITE_VERSION_NUMBER for any given release of SQLite will also

 ** be larger than the release from which it is derived.  Either Y will

 ** be held constant and Z will be incremented or else Y will be incremented

 ** and Z will be reset to zero.

 **

 ** Since [version 3.6.18] ([dateof:3.6.18]), 

 ** SQLite source code has been stored in the

 ** <a href="http://www.fossil-scm.org/">Fossil configuration management

 ** system</a>.  ^The SQLITE_SOURCE_ID macro evaluates to

 ** a string which identifies a particular check-in of SQLite

 ** within its configuration management system.  ^The SQLITE_SOURCE_ID

 ** string contains the date and time of the check-in (UTC) and a SHA1

 ** or SHA3-256 hash of the entire source tree.  If the source code has

 ** been edited in any way since it was last checked in, then the last

 ** four hexadecimal digits of the hash may be modified.

 **

 ** See also: [sqlite3_libversion()],

 ** [sqlite3_libversion_number()], [sqlite3_sourceid()],

 ** [sqlite_version()] and [sqlite_source_id()].

 */

 #define SQLITE_VERSION        "3.26.0"

 #define SQLITE_VERSION_NUMBER 3026000

 #define SQLITE_SOURCE_ID      "2018-12-01 12:34:55 bf8c1b2b7a5960c282e543b9c293686dccff272512d08865f4600fb58238b4f9"

 /*

 ** CAPI3REF: Run-Time Library Version Numbers

 ** KEYWORDS: sqlite3_version sqlite3_sourceid

 **

 ** These interfaces provide the same information as the [SQLITE_VERSION],

 ** [SQLITE_VERSION_NUMBER], and [SQLITE_SOURCE_ID] C preprocessor macros

 ** but are associated with the library instead of the header file.  ^(Cautious

 ** programmers might include assert() statements in their application to

 ** verify that values returned by these interfaces match the macros in

 ** the header, and thus ensure that the application is

 ** compiled with matching library and header files.

 **

 ** <blockquote><pre>

 ** assert( sqlite3_libversion_number()==SQLITE_VERSION_NUMBER );

 ** assert( strncmp(sqlite3_sourceid(),SQLITE_SOURCE_ID,80)==0 );

 ** assert( strcmp(sqlite3_libversion(),SQLITE_VERSION)==0 );

 ** </pre></blockquote>)^

 **

 ** ^The sqlite3_version[] string constant contains the text of [SQLITE_VERSION]

 ** macro.  ^The sqlite3_libversion() function returns a pointer to the

 ** to the sqlite3_version[] string constant.  The sqlite3_libversion()

 ** function is provided for use in DLLs since DLL users usually do not have

 ** direct access to string constants within the DLL.  ^The

 ** sqlite3_libversion_number() function returns an integer equal to

 ** [SQLITE_VERSION_NUMBER].  ^(The sqlite3_sourceid() function returns 

 ** a pointer to a string constant whose value is the same as the 

 ** [SQLITE_SOURCE_ID] C preprocessor macro.  Except if SQLite is built

 ** using an edited copy of [the amalgamation], then the last four characters

 ** of the hash might be different from [SQLITE_SOURCE_ID].)^

 **

 ** See also: [sqlite_version()] and [sqlite_source_id()].

 */

 SQLITE_API const char sqlite3_version[] = SQLITE_VERSION;

 SQLITE_API const char *sqlite3_libversion(void);

 SQLITE_API const char *sqlite3_sourceid(void);

 SQLITE_API int sqlite3_libversion_number(void);

 /*

 ** CAPI3REF: Run-Time Library Compilation Options Diagnostics

 **

 ** ^The sqlite3_compileoption_used() function returns 0 or 1 

 ** indicating whether the specified option was defined at 

 ** compile time.  ^The SQLITE_ prefix may be omitted from the 

 ** option name passed to sqlite3_compileoption_used().  

 **

 ** ^The sqlite3_compileoption_get() function allows iterating

 ** over the list of options that were defined at compile time by

 ** returning the N-th compile time option string.  ^If N is out of range,

 ** sqlite3_compileoption_get() returns a NULL pointer.  ^The SQLITE_ 

 ** prefix is omitted from any strings returned by 

 ** sqlite3_compileoption_get().

 **

 ** ^Support for the diagnostic functions sqlite3_compileoption_used()

 ** and sqlite3_compileoption_get() may be omitted by specifying the 

 ** [SQLITE_OMIT_COMPILEOPTION_DIAGS] option at compile time.

 **

 ** See also: SQL functions [sqlite_compileoption_used()] and

 ** [sqlite_compileoption_get()] and the [compile_options pragma].

 */

 #ifndef SQLITE_OMIT_COMPILEOPTION_DIAGS

 SQLITE_API int sqlite3_compileoption_used(const char *zOptName);

 SQLITE_API const char *sqlite3_compileoption_get(int N);

 #endif

 /*

 ** CAPI3REF: Test To See If The Library Is Threadsafe

 **

 ** ^The sqlite3_threadsafe() function returns zero if and only if

 ** SQLite was compiled with mutexing code omitted due to the

 ** [SQLITE_THREADSAFE] compile-time option being set to 0.

 **

 ** SQLite can be compiled with or without mutexes.  When

 ** the [SQLITE_THREADSAFE] C preprocessor macro is 1 or 2, mutexes

 ** are enabled and SQLite is threadsafe.  When the

 ** [SQLITE_THREADSAFE] macro is 0, 

 ** the mutexes are omitted.  Without the mutexes, it is not safe

 ** to use SQLite concurrently from more than one thread.

 **

 ** Enabling mutexes incurs a measurable performance penalty.

 ** So if speed is of utmost importance, it makes sense to disable

 ** the mutexes.  But for maximum safety, mutexes should be enabled.

 ** ^The default behavior is for mutexes to be enabled.

 **

 ** This interface can be used by an application to make sure that the

 ** version of SQLite that it is linking against was compiled with

 ** the desired setting of the [SQLITE_THREADSAFE] macro.

 **

 ** This interface only reports on the compile-time mutex setting

 ** of the [SQLITE_THREADSAFE] flag.  If SQLite is compiled with

 ** SQLITE_THREADSAFE=1 or =2 then mutexes are enabled by default but

 ** can be fully or partially disabled using a call to [sqlite3_config()]

 ** with the verbs [SQLITE_CONFIG_SINGLETHREAD], [SQLITE_CONFIG_MULTITHREAD],

 ** or [SQLITE_CONFIG_SERIALIZED].  ^(The return value of the

 ** sqlite3_threadsafe() function shows only the compile-time setting of

 ** thread safety, not any run-time changes to that setting made by

 ** sqlite3_config(). In other words, the return value from sqlite3_threadsafe()

 ** is unchanged by calls to sqlite3_config().)^

 **

 ** See the [threading mode] documentation for additional information.

 */

 SQLITE_API int sqlite3_threadsafe(void);

 /*

 ** CAPI3REF: Database Connection Handle

 ** KEYWORDS: {database connection} {database connections}

 **

 ** Each open SQLite database is represented by a pointer to an instance of

 ** the opaque structure named "sqlite3".  It is useful to think of an sqlite3

 ** pointer as an object.  The [sqlite3_open()], [sqlite3_open16()], and

 ** [sqlite3_open_v2()] interfaces are its constructors, and [sqlite3_close()]

 ** and [sqlite3_close_v2()] are its destructors.  There are many other

 ** interfaces (such as

 ** [sqlite3_prepare_v2()], [sqlite3_create_function()], and

 ** [sqlite3_busy_timeout()] to name but three) that are methods on an

 ** sqlite3 object.

 */

 typedef struct sqlite3 sqlite3;

 /*

 ** CAPI3REF: 64-Bit Integer Types

 ** KEYWORDS: sqlite_int64 sqlite_uint64

 **

 ** Because there is no cross-platform way to specify 64-bit integer types

 ** SQLite includes typedefs for 64-bit signed and unsigned integers.

 **

 ** The sqlite3_int64 and sqlite3_uint64 are the preferred type definitions.

 ** The sqlite_int64 and sqlite_uint64 types are supported for backwards

 ** compatibility only.

 **

 ** ^The sqlite3_int64 and sqlite_int64 types can store integer values

 ** between -9223372036854775808 and +9223372036854775807 inclusive.  ^The

 ** sqlite3_uint64 and sqlite_uint64 types can store integer values 

 ** between 0 and +18446744073709551615 inclusive.

 */

 #ifdef SQLITE_INT64_TYPE

   typedef SQLITE_INT64_TYPE sqlite_int64;

 # ifdef SQLITE_UINT64_TYPE

     typedef SQLITE_UINT64_TYPE sqlite_uint64;

 # else  

     typedef unsigned SQLITE_INT64_TYPE sqlite_uint64;

 # endif

 #elif defined(_MSC_VER) || defined(__BORLANDC__)

   typedef __int64 sqlite_int64;

   typedef unsigned __int64 sqlite_uint64;

 #else

   typedef long long int sqlite_int64;

   typedef unsigned long long int sqlite_uint64;

 #endif

 typedef sqlite_int64 sqlite3_int64;

 typedef sqlite_uint64 sqlite3_uint64;

 /*

 ** If compiling for a processor that lacks floating point support,

 ** substitute integer for floating-point.

 */

 #ifdef SQLITE_OMIT_FLOATING_POINT

 # define double sqlite3_int64

 #endif

 /*

 ** CAPI3REF: Closing A Database Connection

 ** DESTRUCTOR: sqlite3

 **

 ** ^The sqlite3_close() and sqlite3_close_v2() routines are destructors

 ** for the [sqlite3] object.

 ** ^Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK] if

 ** the [sqlite3] object is successfully destroyed and all associated

 ** resources are deallocated.

 **

 ** ^If the database connection is associated with unfinalized prepared

 ** statements or unfinished sqlite3_backup objects then sqlite3_close()

 ** will leave the database connection open and return [SQLITE_BUSY].

 ** ^If sqlite3_close_v2() is called with unfinalized prepared statements

 ** and/or unfinished sqlite3_backups, then the database connection becomes

 ** an unusable "zombie" which will automatically be deallocated when the

 ** last prepared statement is finalized or the last sqlite3_backup is

 ** finished.  The sqlite3_close_v2() interface is intended for use with

 ** host languages that are garbage collected, and where the order in which

 ** destructors are called is arbitrary.

 **

 ** Applications should [sqlite3_finalize | finalize] all [prepared statements],

 ** [sqlite3_blob_close | close] all [BLOB handles], and 

 ** [sqlite3_backup_finish | finish] all [sqlite3_backup] objects associated

 ** with the [sqlite3] object prior to attempting to close the object.  ^If

 ** sqlite3_close_v2() is called on a [database connection] that still has

 ** outstanding [prepared statements], [BLOB handles], and/or

 ** [sqlite3_backup] objects then it returns [SQLITE_OK] and the deallocation

 ** of resources is deferred until all [prepared statements], [BLOB handles],

 ** and [sqlite3_backup] objects are also destroyed.

 **

 ** ^If an [sqlite3] object is destroyed while a transaction is open,

 ** the transaction is automatically rolled back.

 **

 ** The C parameter to [sqlite3_close(C)] and [sqlite3_close_v2(C)]

 ** must be either a NULL

 ** pointer or an [sqlite3] object pointer obtained

 ** from [sqlite3_open()], [sqlite3_open16()], or

 ** [sqlite3_open_v2()], and not previously closed.

 ** ^Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer

 ** argument is a harmless no-op.

 */

 SQLITE_API int sqlite3_close(sqlite3*);

 SQLITE_API int sqlite3_close_v2(sqlite3*);

 /*

 ** The type for a callback function.

 ** This is legacy and deprecated.  It is included for historical

 ** compatibility and is not documented.

 */

 typedef int (*sqlite3_callback)(void*,int,char**, char**);

 /*

 ** CAPI3REF: One-Step Query Execution Interface

 ** METHOD: sqlite3

 **

 ** The sqlite3_exec() interface is a convenience wrapper around

 ** [sqlite3_prepare_v2()], [sqlite3_step()], and [sqlite3_finalize()],

 ** that allows an application to run multiple statements of SQL

 ** without having to use a lot of C code. 

 **

 ** ^The sqlite3_exec() interface runs zero or more UTF-8 encoded,

 ** semicolon-separate SQL statements passed into its 2nd argument,

 ** in the context of the [database connection] passed in as its 1st

 ** argument.  ^If the callback function of the 3rd argument to

 ** sqlite3_exec() is not NULL, then it is invoked for each result row

 ** coming out of the evaluated SQL statements.  ^The 4th argument to

 ** sqlite3_exec() is relayed through to the 1st argument of each

 ** callback invocation.  ^If the callback pointer to sqlite3_exec()

 ** is NULL, then no callback is ever invoked and result rows are

 ** ignored.

 **

 ** ^If an error occurs while evaluating the SQL statements passed into

 ** sqlite3_exec(), then execution of the current statement stops and

 ** subsequent statements are skipped.  ^If the 5th parameter to sqlite3_exec()

 ** is not NULL then any error message is written into memory obtained

 ** from [sqlite3_malloc()] and passed back through the 5th parameter.

 ** To avoid memory leaks, the application should invoke [sqlite3_free()]

 ** on error message strings returned through the 5th parameter of

 ** sqlite3_exec() after the error message string is no longer needed.

 ** ^If the 5th parameter to sqlite3_exec() is not NULL and no errors

 ** occur, then sqlite3_exec() sets the pointer in its 5th parameter to

 ** NULL before returning.

 **

 ** ^If an sqlite3_exec() callback returns non-zero, the sqlite3_exec()

 ** routine returns SQLITE_ABORT without invoking the callback again and

 ** without running any subsequent SQL statements.

 **

 ** ^The 2nd argument to the sqlite3_exec() callback function is the

 ** number of columns in the result.  ^The 3rd argument to the sqlite3_exec()

 ** callback is an array of pointers to strings obtained as if from

 ** [sqlite3_column_text()], one for each column.  ^If an element of a

 ** result row is NULL then the corresponding string pointer for the

 ** sqlite3_exec() callback is a NULL pointer.  ^The 4th argument to the

 ** sqlite3_exec() callback is an array of pointers to strings where each

 ** entry represents the name of corresponding result column as obtained

 ** from [sqlite3_column_name()].

 **

 ** ^If the 2nd parameter to sqlite3_exec() is a NULL pointer, a pointer

 ** to an empty string, or a pointer that contains only whitespace and/or 

 ** SQL comments, then no SQL statements are evaluated and the database

 ** is not changed.

 **

 ** Restrictions:

 **

 ** <ul>

 ** <li> The application must ensure that the 1st parameter to sqlite3_exec()

 **      is a valid and open [database connection].

 ** <li> The application must not close the [database connection] specified by

 **      the 1st parameter to sqlite3_exec() while sqlite3_exec() is running.

 ** <li> The application must not modify the SQL statement text passed into

 **      the 2nd parameter of sqlite3_exec() while sqlite3_exec() is running.

 ** </ul>

 */

 SQLITE_API int sqlite3_exec(

   sqlite3*,                                  /* An open database */

   const char *sql,                           /* SQL to be evaluated */

   int (*callback)(void*,int,char**,char**),  /* Callback function */

   void *,                                    /* 1st argument to callback */

   char **errmsg                              /* Error msg written here */

 );

 /*

 ** CAPI3REF: Result Codes

 ** KEYWORDS: {result code definitions}

 **

 ** Many SQLite functions return an integer result code from the set shown

 ** here in order to indicate success or failure.

 **

 ** New error codes may be added in future versions of SQLite.

 **

 ** See also: [extended result code definitions]

 */

 #define SQLITE_OK           0   /* Successful result */

 /* beginning-of-error-codes */

 #define SQLITE_ERROR        1   /* Generic error */

 #define SQLITE_INTERNAL     2   /* Internal logic error in SQLite */

 #define SQLITE_PERM         3   /* Access permission denied */

 #define SQLITE_ABORT        4   /* Callback routine requested an abort */

 #define SQLITE_BUSY         5   /* The database file is locked */

 #define SQLITE_LOCKED       6   /* A table in the database is locked */

 #define SQLITE_NOMEM        7   /* A malloc() failed */

 #define SQLITE_READONLY     8   /* Attempt to write a readonly database */

 #define SQLITE_INTERRUPT    9   /* Operation terminated by sqlite3_interrupt()*/

 #define SQLITE_IOERR       10   /* Some kind of disk I/O error occurred */

 #define SQLITE_CORRUPT     11   /* The database disk image is malformed */

 #define SQLITE_NOTFOUND    12   /* Unknown opcode in sqlite3_file_control() */

 #define SQLITE_FULL        13   /* Insertion failed because database is full */

 #define SQLITE_CANTOPEN    14   /* Unable to open the database file */

 #define SQLITE_PROTOCOL    15   /* Database lock protocol error */

 #define SQLITE_EMPTY       16   /* Internal use only */

 #define SQLITE_SCHEMA      17   /* The database schema changed */

 #define SQLITE_TOOBIG      18   /* String or BLOB exceeds size limit */

 #define SQLITE_CONSTRAINT  19   /* Abort due to constraint violation */

 #define SQLITE_MISMATCH    20   /* Data type mismatch */

 #define SQLITE_MISUSE      21   /* Library used incorrectly */

 #define SQLITE_NOLFS       22   /* Uses OS features not supported on host */

 #define SQLITE_AUTH        23   /* Authorization denied */

 #define SQLITE_FORMAT      24   /* Not used */

 #define SQLITE_RANGE       25   /* 2nd parameter to sqlite3_bind out of range */

 #define SQLITE_NOTADB      26   /* File opened that is not a database file */

 #define SQLITE_NOTICE      27   /* Notifications from sqlite3_log() */

 #define SQLITE_WARNING     28   /* Warnings from sqlite3_log() */

 #define SQLITE_ROW         100  /* sqlite3_step() has another row ready */

 #define SQLITE_DONE        101  /* sqlite3_step() has finished executing */

 /* end-of-error-codes */

 /*

 ** CAPI3REF: Extended Result Codes

 ** KEYWORDS: {extended result code definitions}

 **

 ** In its default configuration, SQLite API routines return one of 30 integer

 ** [result codes].  However, experience has shown that many of

 ** these result codes are too coarse-grained.  They do not provide as

 ** much information about problems as programmers might like.  In an effort to

 ** address this, newer versions of SQLite (version 3.3.8 [dateof:3.3.8]

 ** and later) include

 ** support for additional result codes that provide more detailed information

 ** about errors. These [extended result codes] are enabled or disabled

 ** on a per database connection basis using the

 ** [sqlite3_extended_result_codes()] API.  Or, the extended code for

 ** the most recent error can be obtained using

 ** [sqlite3_extended_errcode()].

 */

 #define SQLITE_ERROR_MISSING_COLLSEQ   (SQLITE_ERROR | (1<<8))

 #define SQLITE_ERROR_RETRY             (SQLITE_ERROR | (2<<8))

 #define SQLITE_ERROR_SNAPSHOT          (SQLITE_ERROR | (3<<8))

 #define SQLITE_IOERR_READ              (SQLITE_IOERR | (1<<8))

 #define SQLITE_IOERR_SHORT_READ        (SQLITE_IOERR | (2<<8))

 #define SQLITE_IOERR_WRITE             (SQLITE_IOERR | (3<<8))

 #define SQLITE_IOERR_FSYNC             (SQLITE_IOERR | (4<<8))

 #define SQLITE_IOERR_DIR_FSYNC         (SQLITE_IOERR | (5<<8))

 #define SQLITE_IOERR_TRUNCATE          (SQLITE_IOERR | (6<<8))

 #define SQLITE_IOERR_FSTAT             (SQLITE_IOERR | (7<<8))

 #define SQLITE_IOERR_UNLOCK            (SQLITE_IOERR | (8<<8))

 #define SQLITE_IOERR_RDLOCK            (SQLITE_IOERR | (9<<8))

 #define SQLITE_IOERR_DELETE            (SQLITE_IOERR | (10<<8))

 #define SQLITE_IOERR_BLOCKED           (SQLITE_IOERR | (11<<8))

 #define SQLITE_IOERR_NOMEM             (SQLITE_IOERR | (12<<8))

 #define SQLITE_IOERR_ACCESS            (SQLITE_IOERR | (13<<8))

 #define SQLITE_IOERR_CHECKRESERVEDLOCK (SQLITE_IOERR | (14<<8))

 #define SQLITE_IOERR_LOCK              (SQLITE_IOERR | (15<<8))

 #define SQLITE_IOERR_CLOSE             (SQLITE_IOERR | (16<<8))

 #define SQLITE_IOERR_DIR_CLOSE         (SQLITE_IOERR | (17<<8))

 #define SQLITE_IOERR_SHMOPEN           (SQLITE_IOERR | (18<<8))

 #define SQLITE_IOERR_SHMSIZE           (SQLITE_IOERR | (19<<8))

 #define SQLITE_IOERR_SHMLOCK           (SQLITE_IOERR | (20<<8))

 #define SQLITE_IOERR_SHMMAP            (SQLITE_IOERR | (21<<8))

 #define SQLITE_IOERR_SEEK              (SQLITE_IOERR | (22<<8))

 #define SQLITE_IOERR_DELETE_NOENT      (SQLITE_IOERR | (23<<8))

 #define SQLITE_IOERR_MMAP              (SQLITE_IOERR | (24<<8))

 #define SQLITE_IOERR_GETTEMPPATH       (SQLITE_IOERR | (25<<8))

 #define SQLITE_IOERR_CONVPATH          (SQLITE_IOERR | (26<<8))

 #define SQLITE_IOERR_VNODE             (SQLITE_IOERR | (27<<8))

 #define SQLITE_IOERR_AUTH              (SQLITE_IOERR | (28<<8))

 #define SQLITE_IOERR_BEGIN_ATOMIC      (SQLITE_IOERR | (29<<8))

 #define SQLITE_IOERR_COMMIT_ATOMIC     (SQLITE_IOERR | (30<<8))

 #define SQLITE_IOERR_ROLLBACK_ATOMIC   (SQLITE_IOERR | (31<<8))

 #define SQLITE_LOCKED_SHAREDCACHE      (SQLITE_LOCKED |  (1<<8))

 #define SQLITE_LOCKED_VTAB             (SQLITE_LOCKED |  (2<<8))

 #define SQLITE_BUSY_RECOVERY           (SQLITE_BUSY   |  (1<<8))

 #define SQLITE_BUSY_SNAPSHOT           (SQLITE_BUSY   |  (2<<8))

 #define SQLITE_CANTOPEN_NOTEMPDIR      (SQLITE_CANTOPEN | (1<<8))

 #define SQLITE_CANTOPEN_ISDIR          (SQLITE_CANTOPEN | (2<<8))

 #define SQLITE_CANTOPEN_FULLPATH       (SQLITE_CANTOPEN | (3<<8))

 #define SQLITE_CANTOPEN_CONVPATH       (SQLITE_CANTOPEN | (4<<8))

 #define SQLITE_CANTOPEN_DIRTYWAL       (SQLITE_CANTOPEN | (5<<8)) /* Not Used */

 #define SQLITE_CORRUPT_VTAB            (SQLITE_CORRUPT | (1<<8))

 #define SQLITE_CORRUPT_SEQUENCE        (SQLITE_CORRUPT | (2<<8))

 #define SQLITE_READONLY_RECOVERY       (SQLITE_READONLY | (1<<8))

 #define SQLITE_READONLY_CANTLOCK       (SQLITE_READONLY | (2<<8))

 #define SQLITE_READONLY_ROLLBACK       (SQLITE_READONLY | (3<<8))

 #define SQLITE_READONLY_DBMOVED        (SQLITE_READONLY | (4<<8))

 #define SQLITE_READONLY_CANTINIT       (SQLITE_READONLY | (5<<8))

 #define SQLITE_READONLY_DIRECTORY      (SQLITE_READONLY | (6<<8))

 #define SQLITE_ABORT_ROLLBACK          (SQLITE_ABORT | (2<<8))

 #define SQLITE_CONSTRAINT_CHECK        (SQLITE_CONSTRAINT | (1<<8))

 #define SQLITE_CONSTRAINT_COMMITHOOK   (SQLITE_CONSTRAINT | (2<<8))

 #define SQLITE_CONSTRAINT_FOREIGNKEY   (SQLITE_CONSTRAINT | (3<<8))

 #define SQLITE_CONSTRAINT_FUNCTION     (SQLITE_CONSTRAINT | (4<<8))

 #define SQLITE_CONSTRAINT_NOTNULL      (SQLITE_CONSTRAINT | (5<<8))

 #define SQLITE_CONSTRAINT_PRIMARYKEY   (SQLITE_CONSTRAINT | (6<<8))

 #define SQLITE_CONSTRAINT_TRIGGER      (SQLITE_CONSTRAINT | (7<<8))

 #define SQLITE_CONSTRAINT_UNIQUE       (SQLITE_CONSTRAINT | (8<<8))

 #define SQLITE_CONSTRAINT_VTAB         (SQLITE_CONSTRAINT | (9<<8))

 #define SQLITE_CONSTRAINT_ROWID        (SQLITE_CONSTRAINT |(10<<8))

 #define SQLITE_NOTICE_RECOVER_WAL      (SQLITE_NOTICE | (1<<8))

 #define SQLITE_NOTICE_RECOVER_ROLLBACK (SQLITE_NOTICE | (2<<8))

 #define SQLITE_WARNING_AUTOINDEX       (SQLITE_WARNING | (1<<8))

 #define SQLITE_AUTH_USER               (SQLITE_AUTH | (1<<8))

 #define SQLITE_OK_LOAD_PERMANENTLY     (SQLITE_OK | (1<<8))

 /*

 ** CAPI3REF: Flags For File Open Operations

 **

 ** These bit values are intended for use in the

 ** 3rd parameter to the [sqlite3_open_v2()] interface and

 ** in the 4th parameter to the [sqlite3_vfs.xOpen] method.

 */

 #define SQLITE_OPEN_READONLY         0x00000001  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_READWRITE        0x00000002  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_CREATE           0x00000004  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_DELETEONCLOSE    0x00000008  /* VFS only */

 #define SQLITE_OPEN_EXCLUSIVE        0x00000010  /* VFS only */

 #define SQLITE_OPEN_AUTOPROXY        0x00000020  /* VFS only */

 #define SQLITE_OPEN_URI              0x00000040  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_MEMORY           0x00000080  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_MAIN_DB          0x00000100  /* VFS only */

 #define SQLITE_OPEN_TEMP_DB          0x00000200  /* VFS only */

 #define SQLITE_OPEN_TRANSIENT_DB     0x00000400  /* VFS only */

 #define SQLITE_OPEN_MAIN_JOURNAL     0x00000800  /* VFS only */

 #define SQLITE_OPEN_TEMP_JOURNAL     0x00001000  /* VFS only */

 #define SQLITE_OPEN_SUBJOURNAL       0x00002000  /* VFS only */

 #define SQLITE_OPEN_MASTER_JOURNAL   0x00004000  /* VFS only */

 #define SQLITE_OPEN_NOMUTEX          0x00008000  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_FULLMUTEX        0x00010000  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_SHAREDCACHE      0x00020000  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_PRIVATECACHE     0x00040000  /* Ok for sqlite3_open_v2() */

 #define SQLITE_OPEN_WAL              0x00080000  /* VFS only */

 /* Reserved:                         0x00F00000 */

 /*

 ** CAPI3REF: Device Characteristics

 **

 ** The xDeviceCharacteristics method of the [sqlite3_io_methods]

 ** object returns an integer which is a vector of these

 ** bit values expressing I/O characteristics of the mass storage

 ** device that holds the file that the [sqlite3_io_methods]

 ** refers to.

 **

 ** The SQLITE_IOCAP_ATOMIC property means that all writes of

 ** any size are atomic.  The SQLITE_IOCAP_ATOMICnnn values

 ** mean that writes of blocks that are nnn bytes in size and

 ** are aligned to an address which is an integer multiple of

 ** nnn are atomic.  The SQLITE_IOCAP_SAFE_APPEND value means

 ** that when data is appended to a file, the data is appended

 ** first then the size of the file is extended, never the other

 ** way around.  The SQLITE_IOCAP_SEQUENTIAL property means that

 ** information is written to disk in the same order as calls

 ** to xWrite().  The SQLITE_IOCAP_POWERSAFE_OVERWRITE property means that

 ** after reboot following a crash or power loss, the only bytes in a

 ** file that were written at the application level might have changed

 ** and that adjacent bytes, even bytes within the same sector are

 ** guaranteed to be unchanged.  The SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN

 ** flag indicates that a file cannot be deleted when open.  The

 ** SQLITE_IOCAP_IMMUTABLE flag indicates that the file is on

 ** read-only media and cannot be changed even by processes with

 ** elevated privileges.

 **

 ** The SQLITE_IOCAP_BATCH_ATOMIC property means that the underlying

 ** filesystem supports doing multiple write operations atomically when those

 ** write operations are bracketed by [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] and

 ** [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE].

 */

 #define SQLITE_IOCAP_ATOMIC                 0x00000001

 #define SQLITE_IOCAP_ATOMIC512              0x00000002

 #define SQLITE_IOCAP_ATOMIC1K               0x00000004

 #define SQLITE_IOCAP_ATOMIC2K               0x00000008

 #define SQLITE_IOCAP_ATOMIC4K               0x00000010

 #define SQLITE_IOCAP_ATOMIC8K               0x00000020

 #define SQLITE_IOCAP_ATOMIC16K              0x00000040

 #define SQLITE_IOCAP_ATOMIC32K              0x00000080

 #define SQLITE_IOCAP_ATOMIC64K              0x00000100

 #define SQLITE_IOCAP_SAFE_APPEND            0x00000200

 #define SQLITE_IOCAP_SEQUENTIAL             0x00000400

 #define SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN  0x00000800

 #define SQLITE_IOCAP_POWERSAFE_OVERWRITE    0x00001000

 #define SQLITE_IOCAP_IMMUTABLE              0x00002000

 #define SQLITE_IOCAP_BATCH_ATOMIC           0x00004000

 /*

 ** CAPI3REF: File Locking Levels

 **

 ** SQLite uses one of these integer values as the second

 ** argument to calls it makes to the xLock() and xUnlock() methods

 ** of an [sqlite3_io_methods] object.

 */

 #define SQLITE_LOCK_NONE          0

 #define SQLITE_LOCK_SHARED        1

 #define SQLITE_LOCK_RESERVED      2

 #define SQLITE_LOCK_PENDING       3

 #define SQLITE_LOCK_EXCLUSIVE     4

 /*

 ** CAPI3REF: Synchronization Type Flags

 **

 ** When SQLite invokes the xSync() method of an

 ** [sqlite3_io_methods] object it uses a combination of

 ** these integer values as the second argument.

 **

 ** When the SQLITE_SYNC_DATAONLY flag is used, it means that the

 ** sync operation only needs to flush data to mass storage.  Inode

 ** information need not be flushed. If the lower four bits of the flag

 ** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics.

 ** If the lower four bits equal SQLITE_SYNC_FULL, that means

 ** to use Mac OS X style fullsync instead of fsync().

 **

 ** Do not confuse the SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags

 ** with the [PRAGMA synchronous]=NORMAL and [PRAGMA synchronous]=FULL

 ** settings.  The [synchronous pragma] determines when calls to the

 ** xSync VFS method occur and applies uniformly across all platforms.

 ** The SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL flags determine how

 ** energetic or rigorous or forceful the sync operations are and

 ** only make a difference on Mac OSX for the default SQLite code.

 ** (Third-party VFS implementations might also make the distinction

 ** between SQLITE_SYNC_NORMAL and SQLITE_SYNC_FULL, but among the

 ** operating systems natively supported by SQLite, only Mac OSX

 ** cares about the difference.)

 */

 #define SQLITE_SYNC_NORMAL        0x00002

 #define SQLITE_SYNC_FULL          0x00003

 #define SQLITE_SYNC_DATAONLY      0x00010

 /*

 ** CAPI3REF: OS Interface Open File Handle

 **

 ** An [sqlite3_file] object represents an open file in the 

 ** [sqlite3_vfs | OS interface layer].  Individual OS interface

 ** implementations will

 ** want to subclass this object by appending additional fields

 ** for their own use.  The pMethods entry is a pointer to an

 ** [sqlite3_io_methods] object that defines methods for performing

 ** I/O operations on the open file.

 */

 typedef struct sqlite3_file sqlite3_file;

 struct sqlite3_file {

   const struct sqlite3_io_methods *pMethods;  /* Methods for an open file */

 };

 /*

 ** CAPI3REF: OS Interface File Virtual Methods Object

 **

 ** Every file opened by the [sqlite3_vfs.xOpen] method populates an

 ** [sqlite3_file] object (or, more commonly, a subclass of the

 ** [sqlite3_file] object) with a pointer to an instance of this object.

 ** This object defines the methods used to perform various operations

 ** against the open file represented by the [sqlite3_file] object.

 **

 ** If the [sqlite3_vfs.xOpen] method sets the sqlite3_file.pMethods element 

 ** to a non-NULL pointer, then the sqlite3_io_methods.xClose method

 ** may be invoked even if the [sqlite3_vfs.xOpen] reported that it failed.  The

 ** only way to prevent a call to xClose following a failed [sqlite3_vfs.xOpen]

 ** is for the [sqlite3_vfs.xOpen] to set the sqlite3_file.pMethods element

 ** to NULL.

 **

 ** The flags argument to xSync may be one of [SQLITE_SYNC_NORMAL] or

 ** [SQLITE_SYNC_FULL].  The first choice is the normal fsync().

 ** The second choice is a Mac OS X style fullsync.  The [SQLITE_SYNC_DATAONLY]

 ** flag may be ORed in to indicate that only the data of the file

 ** and not its inode needs to be synced.

 **

 ** The integer values to xLock() and xUnlock() are one of

 ** <ul>

 ** <li> [SQLITE_LOCK_NONE],

 ** <li> [SQLITE_LOCK_SHARED],

 ** <li> [SQLITE_LOCK_RESERVED],

 ** <li> [SQLITE_LOCK_PENDING], or

 ** <li> [SQLITE_LOCK_EXCLUSIVE].

 ** </ul>

 ** xLock() increases the lock. xUnlock() decreases the lock.

 ** The xCheckReservedLock() method checks whether any database connection,

 ** either in this process or in some other process, is holding a RESERVED,

 ** PENDING, or EXCLUSIVE lock on the file.  It returns true

 ** if such a lock exists and false otherwise.

 **

 ** The xFileControl() method is a generic interface that allows custom

 ** VFS implementations to directly control an open file using the

 ** [sqlite3_file_control()] interface.  The second "op" argument is an

 ** integer opcode.  The third argument is a generic pointer intended to

 ** point to a structure that may contain arguments or space in which to

 ** write return values.  Potential uses for xFileControl() might be

 ** functions to enable blocking locks with timeouts, to change the

 ** locking strategy (for example to use dot-file locks), to inquire

 ** about the status of a lock, or to break stale locks.  The SQLite

 ** core reserves all opcodes less than 100 for its own use.

 ** A [file control opcodes | list of opcodes] less than 100 is available.

 ** Applications that define a custom xFileControl method should use opcodes

 ** greater than 100 to avoid conflicts.  VFS implementations should

 ** return [SQLITE_NOTFOUND] for file control opcodes that they do not

 ** recognize.

 **

 ** The xSectorSize() method returns the sector size of the

 ** device that underlies the file.  The sector size is the

 ** minimum write that can be performed without disturbing

 ** other bytes in the file.  The xDeviceCharacteristics()

 ** method returns a bit vector describing behaviors of the

 ** underlying device:

 **

 ** <ul>

 ** <li> [SQLITE_IOCAP_ATOMIC]

 ** <li> [SQLITE_IOCAP_ATOMIC512]

 ** <li> [SQLITE_IOCAP_ATOMIC1K]

 ** <li> [SQLITE_IOCAP_ATOMIC2K]

 ** <li> [SQLITE_IOCAP_ATOMIC4K]

 ** <li> [SQLITE_IOCAP_ATOMIC8K]

 ** <li> [SQLITE_IOCAP_ATOMIC16K]

 ** <li> [SQLITE_IOCAP_ATOMIC32K]

 ** <li> [SQLITE_IOCAP_ATOMIC64K]

 ** <li> [SQLITE_IOCAP_SAFE_APPEND]

 ** <li> [SQLITE_IOCAP_SEQUENTIAL]

 ** <li> [SQLITE_IOCAP_UNDELETABLE_WHEN_OPEN]

 ** <li> [SQLITE_IOCAP_POWERSAFE_OVERWRITE]

 ** <li> [SQLITE_IOCAP_IMMUTABLE]

 ** <li> [SQLITE_IOCAP_BATCH_ATOMIC]

 ** </ul>

 **

 ** The SQLITE_IOCAP_ATOMIC property means that all writes of

 ** any size are atomic.  The SQLITE_IOCAP_ATOMICnnn values

 ** mean that writes of blocks that are nnn bytes in size and

 ** are aligned to an address which is an integer multiple of

 ** nnn are atomic.  The SQLITE_IOCAP_SAFE_APPEND value means

 ** that when data is appended to a file, the data is appended

 ** first then the size of the file is extended, never the other

 ** way around.  The SQLITE_IOCAP_SEQUENTIAL property means that

 ** information is written to disk in the same order as calls

 ** to xWrite().

 **

 ** If xRead() returns SQLITE_IOERR_SHORT_READ it must also fill

 ** in the unread portions of the buffer with zeros.  A VFS that

 ** fails to zero-fill short reads might seem to work.  However,

 ** failure to zero-fill short reads will eventually lead to

 ** database corruption.

 */

 typedef struct sqlite3_io_methods sqlite3_io_methods;

 struct sqlite3_io_methods {

   int iVersion;

   int (*xClose)(sqlite3_file*);

   int (*xRead)(sqlite3_file*, void*, int iAmt, sqlite3_int64 iOfst);

   int (*xWrite)(sqlite3_file*, const void*, int iAmt, sqlite3_int64 iOfst);

   int (*xTruncate)(sqlite3_file*, sqlite3_int64 size);

   int (*xSync)(sqlite3_file*, int flags);

   int (*xFileSize)(sqlite3_file*, sqlite3_int64 *pSize);

   int (*xLock)(sqlite3_file*, int);

   int (*xUnlock)(sqlite3_file*, int);

   int (*xCheckReservedLock)(sqlite3_file*, int *pResOut);

   int (*xFileControl)(sqlite3_file*, int op, void *pArg);

   int (*xSectorSize)(sqlite3_file*);

   int (*xDeviceCharacteristics)(sqlite3_file*);

   /* Methods above are valid for version 1 */

   int (*xShmMap)(sqlite3_file*, int iPg, int pgsz, int, void volatile**);

   int (*xShmLock)(sqlite3_file*, int offset, int n, int flags);

   void (*xShmBarrier)(sqlite3_file*);

   int (*xShmUnmap)(sqlite3_file*, int deleteFlag);

   /* Methods above are valid for version 2 */

   int (*xFetch)(sqlite3_file*, sqlite3_int64 iOfst, int iAmt, void **pp);

   int (*xUnfetch)(sqlite3_file*, sqlite3_int64 iOfst, void *p);

   /* Methods above are valid for version 3 */

   /* Additional methods may be added in future releases */

 };

 /*

 ** CAPI3REF: Standard File Control Opcodes

 ** KEYWORDS: {file control opcodes} {file control opcode}

 **

 ** These integer constants are opcodes for the xFileControl method

 ** of the [sqlite3_io_methods] object and for the [sqlite3_file_control()]

 ** interface.

 **

 ** <ul>

 ** <li>[[SQLITE_FCNTL_LOCKSTATE]]

 ** The [SQLITE_FCNTL_LOCKSTATE] opcode is used for debugging.  This

 ** opcode causes the xFileControl method to write the current state of

 ** the lock (one of [SQLITE_LOCK_NONE], [SQLITE_LOCK_SHARED],

 ** [SQLITE_LOCK_RESERVED], [SQLITE_LOCK_PENDING], or [SQLITE_LOCK_EXCLUSIVE])

 ** into an integer that the pArg argument points to. This capability

 ** is used during testing and is only available when the SQLITE_TEST

 ** compile-time option is used.

 **

 ** <li>[[SQLITE_FCNTL_SIZE_HINT]]

 ** The [SQLITE_FCNTL_SIZE_HINT] opcode is used by SQLite to give the VFS

 ** layer a hint of how large the database file will grow to be during the

 ** current transaction.  This hint is not guaranteed to be accurate but it

 ** is often close.  The underlying VFS might choose to preallocate database

 ** file space based on this hint in order to help writes to the database

 ** file run faster.

 **

 ** <li>[[SQLITE_FCNTL_CHUNK_SIZE]]

 ** The [SQLITE_FCNTL_CHUNK_SIZE] opcode is used to request that the VFS

 ** extends and truncates the database file in chunks of a size specified

 ** by the user. The fourth argument to [sqlite3_file_control()] should 

 ** point to an integer (type int) containing the new chunk-size to use

 ** for the nominated database. Allocating database file space in large

 ** chunks (say 1MB at a time), may reduce file-system fragmentation and

 ** improve performance on some systems.

 **

 ** <li>[[SQLITE_FCNTL_FILE_POINTER]]

 ** The [SQLITE_FCNTL_FILE_POINTER] opcode is used to obtain a pointer

 ** to the [sqlite3_file] object associated with a particular database

 ** connection.  See also [SQLITE_FCNTL_JOURNAL_POINTER].

 **

 ** <li>[[SQLITE_FCNTL_JOURNAL_POINTER]]

 ** The [SQLITE_FCNTL_JOURNAL_POINTER] opcode is used to obtain a pointer

 ** to the [sqlite3_file] object associated with the journal file (either

 ** the [rollback journal] or the [write-ahead log]) for a particular database

 ** connection.  See also [SQLITE_FCNTL_FILE_POINTER].

 **

 ** <li>[[SQLITE_FCNTL_SYNC_OMITTED]]

 ** No longer in use.

 **

 ** <li>[[SQLITE_FCNTL_SYNC]]

 ** The [SQLITE_FCNTL_SYNC] opcode is generated internally by SQLite and

 ** sent to the VFS immediately before the xSync method is invoked on a

 ** database file descriptor. Or, if the xSync method is not invoked 

 ** because the user has configured SQLite with 

 ** [PRAGMA synchronous | PRAGMA synchronous=OFF] it is invoked in place 

 ** of the xSync method. In most cases, the pointer argument passed with

 ** this file-control is NULL. However, if the database file is being synced

 ** as part of a multi-database commit, the argument points to a nul-terminated

 ** string containing the transactions master-journal file name. VFSes that 

 ** do not need this signal should silently ignore this opcode. Applications 

 ** should not call [sqlite3_file_control()] with this opcode as doing so may 

 ** disrupt the operation of the specialized VFSes that do require it.  

 **

 ** <li>[[SQLITE_FCNTL_COMMIT_PHASETWO]]

 ** The [SQLITE_FCNTL_COMMIT_PHASETWO] opcode is generated internally by SQLite

 ** and sent to the VFS after a transaction has been committed immediately

 ** but before the database is unlocked. VFSes that do not need this signal

 ** should silently ignore this opcode. Applications should not call

 ** [sqlite3_file_control()] with this opcode as doing so may disrupt the 

 ** operation of the specialized VFSes that do require it.  

 **

 ** <li>[[SQLITE_FCNTL_WIN32_AV_RETRY]]

 ** ^The [SQLITE_FCNTL_WIN32_AV_RETRY] opcode is used to configure automatic

 ** retry counts and intervals for certain disk I/O operations for the

 ** windows [VFS] in order to provide robustness in the presence of

 ** anti-virus programs.  By default, the windows VFS will retry file read,

 ** file write, and file delete operations up to 10 times, with a delay

 ** of 25 milliseconds before the first retry and with the delay increasing

 ** by an additional 25 milliseconds with each subsequent retry.  This

 ** opcode allows these two values (10 retries and 25 milliseconds of delay)

 ** to be adjusted.  The values are changed for all database connections

 ** within the same process.  The argument is a pointer to an array of two

 ** integers where the first integer is the new retry count and the second

 ** integer is the delay.  If either integer is negative, then the setting

 ** is not changed but instead the prior value of that setting is written

 ** into the array entry, allowing the current retry settings to be

 ** interrogated.  The zDbName parameter is ignored.

 **

 ** <li>[[SQLITE_FCNTL_PERSIST_WAL]]

 ** ^The [SQLITE_FCNTL_PERSIST_WAL] opcode is used to set or query the

 ** persistent [WAL | Write Ahead Log] setting.  By default, the auxiliary

 ** write ahead log ([WAL file]) and shared memory

 ** files used for transaction control

 ** are automatically deleted when the latest connection to the database

 ** closes.  Setting persistent WAL mode causes those files to persist after

 ** close.  Persisting the files is useful when other processes that do not

 ** have write permission on the directory containing the database file want

 ** to read the database file, as the WAL and shared memory files must exist

 ** in order for the database to be readable.  The fourth parameter to

 ** [sqlite3_file_control()] for this opcode should be a pointer to an integer.

 ** That integer is 0 to disable persistent WAL mode or 1 to enable persistent

 ** WAL mode.  If the integer is -1, then it is overwritten with the current

 ** WAL persistence setting.

 **

 ** <li>[[SQLITE_FCNTL_POWERSAFE_OVERWRITE]]

 ** ^The [SQLITE_FCNTL_POWERSAFE_OVERWRITE] opcode is used to set or query the

 ** persistent "powersafe-overwrite" or "PSOW" setting.  The PSOW setting

 ** determines the [SQLITE_IOCAP_POWERSAFE_OVERWRITE] bit of the

 ** xDeviceCharacteristics methods. The fourth parameter to

 ** [sqlite3_file_control()] for this opcode should be a pointer to an integer.

 ** That integer is 0 to disable zero-damage mode or 1 to enable zero-damage

 ** mode.  If the integer is -1, then it is overwritten with the current

 ** zero-damage mode setting.

 **

 ** <li>[[SQLITE_FCNTL_OVERWRITE]]

 ** ^The [SQLITE_FCNTL_OVERWRITE] opcode is invoked by SQLite after opening

 ** a write transaction to indicate that, unless it is rolled back for some

 ** reason, the entire database file will be overwritten by the current 

 ** transaction. This is used by VACUUM operations.

 **

 ** <li>[[SQLITE_FCNTL_VFSNAME]]

 ** ^The [SQLITE_FCNTL_VFSNAME] opcode can be used to obtain the names of

 ** all [VFSes] in the VFS stack.  The names are of all VFS shims and the

 ** final bottom-level VFS are written into memory obtained from 

 ** [sqlite3_malloc()] and the result is stored in the char* variable

 ** that the fourth parameter of [sqlite3_file_control()] points to.

 ** The caller is responsible for freeing the memory when done.  As with

 ** all file-control actions, there is no guarantee that this will actually

 ** do anything.  Callers should initialize the char* variable to a NULL

 ** pointer in case this file-control is not implemented.  This file-control

 ** is intended for diagnostic use only.

 **

 ** <li>[[SQLITE_FCNTL_VFS_POINTER]]

 ** ^The [SQLITE_FCNTL_VFS_POINTER] opcode finds a pointer to the top-level

 ** [VFSes] currently in use.  ^(The argument X in

 ** sqlite3_file_control(db,SQLITE_FCNTL_VFS_POINTER,X) must be

 ** of type "[sqlite3_vfs] **".  This opcodes will set *X

 ** to a pointer to the top-level VFS.)^

 ** ^When there are multiple VFS shims in the stack, this opcode finds the

 ** upper-most shim only.

 **

 ** <li>[[SQLITE_FCNTL_PRAGMA]]

 ** ^Whenever a [PRAGMA] statement is parsed, an [SQLITE_FCNTL_PRAGMA] 

 ** file control is sent to the open [sqlite3_file] object corresponding

 ** to the database file to which the pragma statement refers. ^The argument

 ** to the [SQLITE_FCNTL_PRAGMA] file control is an array of

 ** pointers to strings (char**) in which the second element of the array

 ** is the name of the pragma and the third element is the argument to the

 ** pragma or NULL if the pragma has no argument.  ^The handler for an

 ** [SQLITE_FCNTL_PRAGMA] file control can optionally make the first element

 ** of the char** argument point to a string obtained from [sqlite3_mprintf()]

 ** or the equivalent and that string will become the result of the pragma or

 ** the error message if the pragma fails. ^If the

 ** [SQLITE_FCNTL_PRAGMA] file control returns [SQLITE_NOTFOUND], then normal 

 ** [PRAGMA] processing continues.  ^If the [SQLITE_FCNTL_PRAGMA]

 ** file control returns [SQLITE_OK], then the parser assumes that the

 ** VFS has handled the PRAGMA itself and the parser generates a no-op

 ** prepared statement if result string is NULL, or that returns a copy

 ** of the result string if the string is non-NULL.

 ** ^If the [SQLITE_FCNTL_PRAGMA] file control returns

 ** any result code other than [SQLITE_OK] or [SQLITE_NOTFOUND], that means

 ** that the VFS encountered an error while handling the [PRAGMA] and the

 ** compilation of the PRAGMA fails with an error.  ^The [SQLITE_FCNTL_PRAGMA]

 ** file control occurs at the beginning of pragma statement analysis and so

 ** it is able to override built-in [PRAGMA] statements.

 **

 ** <li>[[SQLITE_FCNTL_BUSYHANDLER]]

 ** ^The [SQLITE_FCNTL_BUSYHANDLER]

 ** file-control may be invoked by SQLite on the database file handle

 ** shortly after it is opened in order to provide a custom VFS with access

 ** to the connections busy-handler callback. The argument is of type (void **)

 ** - an array of two (void *) values. The first (void *) actually points

 ** to a function of type (int (*)(void *)). In order to invoke the connections

 ** busy-handler, this function should be invoked with the second (void *) in

 ** the array as the only argument. If it returns non-zero, then the operation

 ** should be retried. If it returns zero, the custom VFS should abandon the

 ** current operation.

 **

 ** <li>[[SQLITE_FCNTL_TEMPFILENAME]]

 ** ^Application can invoke the [SQLITE_FCNTL_TEMPFILENAME] file-control

 ** to have SQLite generate a

 ** temporary filename using the same algorithm that is followed to generate

 ** temporary filenames for TEMP tables and other internal uses.  The

 ** argument should be a char** which will be filled with the filename

 ** written into memory obtained from [sqlite3_malloc()].  The caller should

 ** invoke [sqlite3_free()] on the result to avoid a memory leak.

 **

 ** <li>[[SQLITE_FCNTL_MMAP_SIZE]]

 ** The [SQLITE_FCNTL_MMAP_SIZE] file control is used to query or set the

 ** maximum number of bytes that will be used for memory-mapped I/O.

 ** The argument is a pointer to a value of type sqlite3_int64 that

 ** is an advisory maximum number of bytes in the file to memory map.  The

 ** pointer is overwritten with the old value.  The limit is not changed if

 ** the value originally pointed to is negative, and so the current limit 

 ** can be queried by passing in a pointer to a negative number.  This

 ** file-control is used internally to implement [PRAGMA mmap_size].

 **

 ** <li>[[SQLITE_FCNTL_TRACE]]

 ** The [SQLITE_FCNTL_TRACE] file control provides advisory information

 ** to the VFS about what the higher layers of the SQLite stack are doing.

 ** This file control is used by some VFS activity tracing [shims].

 ** The argument is a zero-terminated string.  Higher layers in the

 ** SQLite stack may generate instances of this file control if

 ** the [SQLITE_USE_FCNTL_TRACE] compile-time option is enabled.

 **

 ** <li>[[SQLITE_FCNTL_HAS_MOVED]]

 ** The [SQLITE_FCNTL_HAS_MOVED] file control interprets its argument as a

 ** pointer to an integer and it writes a boolean into that integer depending

 ** on whether or not the file has been renamed, moved, or deleted since it

 ** was first opened.

 **

 ** <li>[[SQLITE_FCNTL_WIN32_GET_HANDLE]]

 ** The [SQLITE_FCNTL_WIN32_GET_HANDLE] opcode can be used to obtain the

 ** underlying native file handle associated with a file handle.  This file

 ** control interprets its argument as a pointer to a native file handle and

 ** writes the resulting value there.

 **

 ** <li>[[SQLITE_FCNTL_WIN32_SET_HANDLE]]

 ** The [SQLITE_FCNTL_WIN32_SET_HANDLE] opcode is used for debugging.  This

 ** opcode causes the xFileControl method to swap the file handle with the one

 ** pointed to by the pArg argument.  This capability is used during testing

 ** and only needs to be supported when SQLITE_TEST is defined.

 **

 ** <li>[[SQLITE_FCNTL_WAL_BLOCK]]

 ** The [SQLITE_FCNTL_WAL_BLOCK] is a signal to the VFS layer that it might

 ** be advantageous to block on the next WAL lock if the lock is not immediately

 ** available.  The WAL subsystem issues this signal during rare

 ** circumstances in order to fix a problem with priority inversion.

 ** Applications should <em>not</em> use this file-control.

 **

 ** <li>[[SQLITE_FCNTL_ZIPVFS]]

 ** The [SQLITE_FCNTL_ZIPVFS] opcode is implemented by zipvfs only. All other

 ** VFS should return SQLITE_NOTFOUND for this opcode.

 **

 ** <li>[[SQLITE_FCNTL_RBU]]

 ** The [SQLITE_FCNTL_RBU] opcode is implemented by the special VFS used by

 ** the RBU extension only.  All other VFS should return SQLITE_NOTFOUND for

 ** this opcode.  

 **

 ** <li>[[SQLITE_FCNTL_BEGIN_ATOMIC_WRITE]]

 ** If the [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] opcode returns SQLITE_OK, then

 ** the file descriptor is placed in "batch write mode", which

 ** means all subsequent write operations will be deferred and done

 ** atomically at the next [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE].  Systems

 ** that do not support batch atomic writes will return SQLITE_NOTFOUND.

 ** ^Following a successful SQLITE_FCNTL_BEGIN_ATOMIC_WRITE and prior to

 ** the closing [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE] or

 ** [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE], SQLite will make

 ** no VFS interface calls on the same [sqlite3_file] file descriptor

 ** except for calls to the xWrite method and the xFileControl method

 ** with [SQLITE_FCNTL_SIZE_HINT].

 **

 ** <li>[[SQLITE_FCNTL_COMMIT_ATOMIC_WRITE]]

 ** The [SQLITE_FCNTL_COMMIT_ATOMIC_WRITE] opcode causes all write

 ** operations since the previous successful call to 

 ** [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] to be performed atomically.

 ** This file control returns [SQLITE_OK] if and only if the writes were

 ** all performed successfully and have been committed to persistent storage.

 ** ^Regardless of whether or not it is successful, this file control takes

 ** the file descriptor out of batch write mode so that all subsequent

 ** write operations are independent.

 ** ^SQLite will never invoke SQLITE_FCNTL_COMMIT_ATOMIC_WRITE without

 ** a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE].

 **

 ** <li>[[SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE]]

 ** The [SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE] opcode causes all write

 ** operations since the previous successful call to 

 ** [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE] to be rolled back.

 ** ^This file control takes the file descriptor out of batch write mode

 ** so that all subsequent write operations are independent.

 ** ^SQLite will never invoke SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE without

 ** a prior successful call to [SQLITE_FCNTL_BEGIN_ATOMIC_WRITE].

 **

 ** <li>[[SQLITE_FCNTL_LOCK_TIMEOUT]]

 ** The [SQLITE_FCNTL_LOCK_TIMEOUT] opcode causes attempts to obtain

 ** a file lock using the xLock or xShmLock methods of the VFS to wait

 ** for up to M milliseconds before failing, where M is the single 

 ** unsigned integer parameter.

 **

 ** <li>[[SQLITE_FCNTL_DATA_VERSION]]

 ** The [SQLITE_FCNTL_DATA_VERSION] opcode is used to detect changes to

 ** a database file.  The argument is a pointer to a 32-bit unsigned integer.

 ** The "data version" for the pager is written into the pointer.  The

 ** "data version" changes whenever any change occurs to the corresponding

 ** database file, either through SQL statements on the same database

 ** connection or through transactions committed by separate database

 ** connections possibly in other processes. The [sqlite3_total_changes()]

 ** interface can be used to find if any database on the connection has changed,

 ** but that interface responds to changes on TEMP as well as MAIN and does

 ** not provide a mechanism to detect changes to MAIN only.  Also, the

 ** [sqlite3_total_changes()] interface responds to internal changes only and

 ** omits changes made by other database connections.  The

 ** [PRAGMA data_version] command provide a mechanism to detect changes to

 ** a single attached database that occur due to other database connections,

 ** but omits changes implemented by the database connection on which it is

 ** called.  This file control is the only mechanism to detect changes that

 ** happen either internally or externally and that are associated with

 ** a particular attached database.

 ** </ul>

 */

 #define SQLITE_FCNTL_LOCKSTATE               1

 #define SQLITE_FCNTL_GET_LOCKPROXYFILE       2

 #define SQLITE_FCNTL_SET_LOCKPROXYFILE       3

 #define SQLITE_FCNTL_LAST_ERRNO              4

 #define SQLITE_FCNTL_SIZE_HINT               5

 #define SQLITE_FCNTL_CHUNK_SIZE              6

 #define SQLITE_FCNTL_FILE_POINTER            7

 #define SQLITE_FCNTL_SYNC_OMITTED            8

 #define SQLITE_FCNTL_WIN32_AV_RETRY          9

 #define SQLITE_FCNTL_PERSIST_WAL            10

 #define SQLITE_FCNTL_OVERWRITE              11

 #define SQLITE_FCNTL_VFSNAME                12

 #define SQLITE_FCNTL_POWERSAFE_OVERWRITE    13

 #define SQLITE_FCNTL_PRAGMA                 14

 #define SQLITE_FCNTL_BUSYHANDLER            15

 #define SQLITE_FCNTL_TEMPFILENAME           16

 #define SQLITE_FCNTL_MMAP_SIZE              18

 #define SQLITE_FCNTL_TRACE                  19

 #define SQLITE_FCNTL_HAS_MOVED              20

 #define SQLITE_FCNTL_SYNC                   21

 #define SQLITE_FCNTL_COMMIT_PHASETWO        22

 #define SQLITE_FCNTL_WIN32_SET_HANDLE       23

 #define SQLITE_FCNTL_WAL_BLOCK              24

 #define SQLITE_FCNTL_ZIPVFS                 25

 #define SQLITE_FCNTL_RBU                    26

 #define SQLITE_FCNTL_VFS_POINTER            27

 #define SQLITE_FCNTL_JOURNAL_POINTER        28

 #define SQLITE_FCNTL_WIN32_GET_HANDLE       29

 #define SQLITE_FCNTL_PDB                    30

 #define SQLITE_FCNTL_BEGIN_ATOMIC_WRITE     31

 #define SQLITE_FCNTL_COMMIT_ATOMIC_WRITE    32

 #define SQLITE_FCNTL_ROLLBACK_ATOMIC_WRITE  33

 #define SQLITE_FCNTL_LOCK_TIMEOUT           34

 #define SQLITE_FCNTL_DATA_VERSION           35

 /* deprecated names */

 #define SQLITE_GET_LOCKPROXYFILE      SQLITE_FCNTL_GET_LOCKPROXYFILE

 #define SQLITE_SET_LOCKPROXYFILE      SQLITE_FCNTL_SET_LOCKPROXYFILE

 #define SQLITE_LAST_ERRNO             SQLITE_FCNTL_LAST_ERRNO

 /*

 ** CAPI3REF: Mutex Handle

 **

 ** The mutex module within SQLite defines [sqlite3_mutex] to be an

 ** abstract type for a mutex object.  The SQLite core never looks

 ** at the internal representation of an [sqlite3_mutex].  It only

 ** deals with pointers to the [sqlite3_mutex] object.

 **

 ** Mutexes are created using [sqlite3_mutex_alloc()].

 */

 typedef struct sqlite3_mutex sqlite3_mutex;

 /*

 ** CAPI3REF: Loadable Extension Thunk

 **

 ** A pointer to the opaque sqlite3_api_routines structure is passed as

 ** the third parameter to entry points of [loadable extensions].  This

 ** structure must be typedefed in order to work around compiler warnings

 ** on some platforms.

 */

 typedef struct sqlite3_api_routines sqlite3_api_routines;

 /*

 ** CAPI3REF: OS Interface Object

 **

 ** An instance of the sqlite3_vfs object defines the interface between

 ** the SQLite core and the underlying operating system.  The "vfs"

 ** in the name of the object stands for "virtual file system".  See

 ** the [VFS | VFS documentation] for further information.

 **

 ** The VFS interface is sometimes extended by adding new methods onto

 ** the end.  Each time such an extension occurs, the iVersion field

 ** is incremented.  The iVersion value started out as 1 in

 ** SQLite [version 3.5.0] on [dateof:3.5.0], then increased to 2

 ** with SQLite [version 3.7.0] on [dateof:3.7.0], and then increased

 ** to 3 with SQLite [version 3.7.6] on [dateof:3.7.6].  Additional fields

 ** may be appended to the sqlite3_vfs object and the iVersion value

 ** may increase again in future versions of SQLite.

 ** Note that the structure

 ** of the sqlite3_vfs object changes in the transition from

 ** SQLite [version 3.5.9] to [version 3.6.0] on [dateof:3.6.0]

 ** and yet the iVersion field was not modified.

 **

 ** The szOsFile field is the size of the subclassed [sqlite3_file]

 ** structure used by this VFS.  mxPathname is the maximum length of

 ** a pathname in this VFS.

 **

 ** Registered sqlite3_vfs objects are kept on a linked list formed by

 ** the pNext pointer.  The [sqlite3_vfs_register()]

 ** and [sqlite3_vfs_unregister()] interfaces manage this list

 ** in a thread-safe way.  The [sqlite3_vfs_find()] interface

 ** searches the list.  Neither the application code nor the VFS

 ** implementation should use the pNext pointer.

 **

 ** The pNext field is the only field in the sqlite3_vfs

 ** structure that SQLite will ever modify.  SQLite will only access

 ** or modify this field while holding a particular static mutex.

 ** The application should never modify anything within the sqlite3_vfs

 ** object once the object has been registered.

 **

 ** The zName field holds the name of the VFS module.  The name must

 ** be unique across all VFS modules.

 **

 ** [[sqlite3_vfs.xOpen]]

 ** ^SQLite guarantees that the zFilename parameter to xOpen

 ** is either a NULL pointer or string obtained

 ** from xFullPathname() with an optional suffix added.

 ** ^If a suffix is added to the zFilename parameter, it will

 ** consist of a single "-" character followed by no more than

 ** 11 alphanumeric and/or "-" characters.

 ** ^SQLite further guarantees that

 ** the string will be valid and unchanged until xClose() is

 ** called. Because of the previous sentence,

 ** the [sqlite3_file] can safely store a pointer to the

 ** filename if it needs to remember the filename for some reason.

 ** If the zFilename parameter to xOpen is a NULL pointer then xOpen

 ** must invent its own temporary name for the file.  ^Whenever the 

 ** xFilename parameter is NULL it will also be the case that the

 ** flags parameter will include [SQLITE_OPEN_DELETEONCLOSE].

 **

 ** The flags argument to xOpen() includes all bits set in

 ** the flags argument to [sqlite3_open_v2()].  Or if [sqlite3_open()]

 ** or [sqlite3_open16()] is used, then flags includes at least

 ** [SQLITE_OPEN_READWRITE] | [SQLITE_OPEN_CREATE]. 

 ** If xOpen() opens a file read-only then it sets *pOutFlags to

 ** include [SQLITE_OPEN_READONLY].  Other bits in *pOutFlags may be set.

 **

 ** ^(SQLite will also add one of the following flags to the xOpen()

 ** call, depending on the object being opened:

 **

 ** <ul>

 ** <li>  [SQLITE_OPEN_MAIN_DB]

 ** <li>  [SQLITE_OPEN_MAIN_JOURNAL]

 ** <li>  [SQLITE_OPEN_TEMP_DB]

 ** <li>  [SQLITE_OPEN_TEMP_JOURNAL]

 ** <li>  [SQLITE_OPEN_TRANSIENT_DB]

 ** <li>  [SQLITE_OPEN_SUBJOURNAL]

 ** <li>  [SQLITE_OPEN_MASTER_JOURNAL]

 ** <li>  [SQLITE_OPEN_WAL]

 ** </ul>)^

 **

 ** The file I/O implementation can use the object type flags to

 ** change the way it deals with files.  For example, an application

 ** that does not care about crash recovery or rollback might make

 ** the open of a journal file a no-op.  Writes to this journal would

 ** also be no-ops, and any attempt to read the journal would return

 ** SQLITE_IOERR.  Or the implementation might recognize that a database

 ** file will be doing page-aligned sector reads and writes in a random

 ** order and set up its I/O subsystem accordingly.

 **

 ** SQLite might also add one of the following flags to the xOpen method:

 **

 ** <ul>

 ** <li> [SQLITE_OPEN_DELETEONCLOSE]

 ** <li> [SQLITE_OPEN_EXCLUSIVE]

 ** </ul>

 **

 ** The [SQLITE_OPEN_DELETEONCLOSE] flag means the file should be

 ** deleted when it is closed.  ^The [SQLITE_OPEN_DELETEONCLOSE]

 ** will be set for TEMP databases and their journals, transient

 ** databases, and subjournals.

 **

 ** ^The [SQLITE_OPEN_EXCLUSIVE] flag is always used in conjunction

 ** with the [SQLITE_OPEN_CREATE] flag, which are both directly

 ** analogous to the O_EXCL and O_CREAT flags of the POSIX open()

 ** API.  The SQLITE_OPEN_EXCLUSIVE flag, when paired with the 

 ** SQLITE_OPEN_CREATE, is used to indicate that file should always

 ** be created, and that it is an error if it already exists.

 ** It is <i>not</i> used to indicate the file should be opened 

 ** for exclusive access.

 **

 ** ^At least szOsFile bytes of memory are allocated by SQLite

 ** to hold the  [sqlite3_file] structure passed as the third

 ** argument to xOpen.  The xOpen method does not have to

 ** allocate the structure; it should just fill it in.  Note that

 ** the xOpen method must set the sqlite3_file.pMethods to either

 ** a valid [sqlite3_io_methods] object or to NULL.  xOpen must do

 ** this even if the open fails.  SQLite expects that the sqlite3_file.pMethods

 ** element will be valid after xOpen returns regardless of the success

 ** or failure of the xOpen call.

 **

 ** [[sqlite3_vfs.xAccess]]

 ** ^The flags argument to xAccess() may be [SQLITE_ACCESS_EXISTS]

 ** to test for the existence of a file, or [SQLITE_ACCESS_READWRITE] to

 ** test whether a file is readable and writable, or [SQLITE_ACCESS_READ]

 ** to test whether a file is at least readable.   The file can be a

 ** directory.

 **

 ** ^SQLite will always allocate at least mxPathname+1 bytes for the

 ** output buffer xFullPathname.  The exact size of the output buffer

 ** is also passed as a parameter to both  methods. If the output buffer

 ** is not large enough, [SQLITE_CANTOPEN] should be returned. Since this is

 ** handled as a fatal error by SQLite, vfs implementations should endeavor

 ** to prevent this by setting mxPathname to a sufficiently large value.

 **

 ** The xRandomness(), xSleep(), xCurrentTime(), and xCurrentTimeInt64()

 ** interfaces are not strictly a part of the filesystem, but they are

 ** included in the VFS structure for completeness.

 ** The xRandomness() function attempts to return nBytes bytes

 ** of good-quality randomness into zOut.  The return value is

 ** the actual number of bytes of randomness obtained.

 ** The xSleep() method causes the calling thread to sleep for at

 ** least the number of microseconds given.  ^The xCurrentTime()

 ** method returns a Julian Day Number for the current date and time as

 ** a floating point value.

 ** ^The xCurrentTimeInt64() method returns, as an integer, the Julian

 ** Day Number multiplied by 86400000 (the number of milliseconds in 

 ** a 24-hour day).  

 ** ^SQLite will use the xCurrentTimeInt64() method to get the current

 ** date and time if that method is available (if iVersion is 2 or 

 ** greater and the function pointer is not NULL) and will fall back

 ** to xCurrentTime() if xCurrentTimeInt64() is unavailable.

 **

 ** ^The xSetSystemCall(), xGetSystemCall(), and xNestSystemCall() interfaces

 ** are not used by the SQLite core.  These optional interfaces are provided

 ** by some VFSes to facilitate testing of the VFS code. By overriding 

 ** system calls with functions under its control, a test program can

 ** simulate faults and error conditions that would otherwise be difficult

 ** or impossible to induce.  The set of system calls that can be overridden

 ** varies from one VFS to another, and from one version of the same VFS to the

 ** next.  Applications that use these interfaces must be prepared for any

 ** or all of these interfaces to be NULL or for their behavior to change

 ** from one release to the next.  Applications must not attempt to access

 ** any of these methods if the iVersion of the VFS is less than 3.

 */

 typedef struct sqlite3_vfs sqlite3_vfs;

 typedef void (*sqlite3_syscall_ptr)(void);

 struct sqlite3_vfs {

   int iVersion;            /* Structure version number (currently 3) */

   int szOsFile;            /* Size of subclassed sqlite3_file */

   int mxPathname;          /* Maximum file pathname length */

   sqlite3_vfs *pNext;      /* Next registered VFS */

   const char *zName;       /* Name of this virtual file system */

   void *pAppData;          /* Pointer to application-specific data */

   int (*xOpen)(sqlite3_vfs*, const char *zName, sqlite3_file*,

                int flags, int *pOutFlags);

   int (*xDelete)(sqlite3_vfs*, const char *zName, int syncDir);

   int (*xAccess)(sqlite3_vfs*, const char *zName, int flags, int *pResOut);

   int (*xFullPathname)(sqlite3_vfs*, const char *zName, int nOut, char *zOut);

   void *(*xDlOpen)(sqlite3_vfs*, const char *zFilename);

   void (*xDlError)(sqlite3_vfs*, int nByte, char *zErrMsg);

   void (*(*xDlSym)(sqlite3_vfs*,void*, const char *zSymbol))(void);

   void (*xDlClose)(sqlite3_vfs*, void*);

   int (*xRandomness)(sqlite3_vfs*, int nByte, char *zOut);

   int (*xSleep)(sqlite3_vfs*, int microseconds);

   int (*xCurrentTime)(sqlite3_vfs*, double*);

   int (*xGetLastError)(sqlite3_vfs*, int, char *);

   /*

   ** The methods above are in version 1 of the sqlite_vfs object

   ** definition.  Those that follow are added in version 2 or later

   */

   int (*xCurrentTimeInt64)(sqlite3_vfs*, sqlite3_int64*);

   /*

   ** The methods above are in versions 1 and 2 of the sqlite_vfs object.

   ** Those below are for version 3 and greater.

   */

   int (*xSetSystemCall)(sqlite3_vfs*, const char *zName, sqlite3_syscall_ptr);

   sqlite3_syscall_ptr (*xGetSystemCall)(sqlite3_vfs*, const char *zName);

   const char *(*xNextSystemCall)(sqlite3_vfs*, const char *zName);

   /*

   ** The methods above are in versions 1 through 3 of the sqlite_vfs object.

   ** New fields may be appended in future versions.  The iVersion

   ** value will increment whenever this happens. 

   */

 };

 /*

 ** CAPI3REF: Flags for the xAccess VFS method

 **

 ** These integer constants can be used as the third parameter to

 ** the xAccess method of an [sqlite3_vfs] object.  They determine

 ** what kind of permissions the xAccess method is looking for.

 ** With SQLITE_ACCESS_EXISTS, the xAccess method

 ** simply checks whether the file exists.

 ** With SQLITE_ACCESS_READWRITE, the xAccess method

 ** checks whether the named directory is both readable and writable

 ** (in other words, if files can be added, removed, and renamed within

 ** the directory).

 ** The SQLITE_ACCESS_READWRITE constant is currently used only by the

 ** [temp_store_directory pragma], though this could change in a future

 ** release of SQLite.

 ** With SQLITE_ACCESS_READ, the xAccess method

 ** checks whether the file is readable.  The SQLITE_ACCESS_READ constant is

 ** currently unused, though it might be used in a future release of

 ** SQLite.

 */

 #define SQLITE_ACCESS_EXISTS    0

 #define SQLITE_ACCESS_READWRITE 1   /* Used by PRAGMA temp_store_directory */

 #define SQLITE_ACCESS_READ      2   /* Unused */

 /*

 ** CAPI3REF: Flags for the xShmLock VFS method

 **

 ** These integer constants define the various locking operations

 ** allowed by the xShmLock method of [sqlite3_io_methods].  The

 ** following are the only legal combinations of flags to the

 ** xShmLock method:

 **

 ** <ul>

 ** <li>  SQLITE_SHM_LOCK | SQLITE_SHM_SHARED

 ** <li>  SQLITE_SHM_LOCK | SQLITE_SHM_EXCLUSIVE

 ** <li>  SQLITE_SHM_UNLOCK | SQLITE_SHM_SHARED

 ** <li>  SQLITE_SHM_UNLOCK | SQLITE_SHM_EXCLUSIVE

 ** </ul>

 **

 ** When unlocking, the same SHARED or EXCLUSIVE flag must be supplied as

 ** was given on the corresponding lock.  

 **

 ** The xShmLock method can transition between unlocked and SHARED or

 ** between unlocked and EXCLUSIVE.  It cannot transition between SHARED

 ** and EXCLUSIVE.

 */

 #define SQLITE_SHM_UNLOCK       1

 #define SQLITE_SHM_LOCK         2

 #define SQLITE_SHM_SHARED       4

 #define SQLITE_SHM_EXCLUSIVE    8

 /*

 ** CAPI3REF: Maximum xShmLock index

 **

 ** The xShmLock method on [sqlite3_io_methods] may use values

 ** between 0 and this upper bound as its "offset" argument.

 ** The SQLite core will never attempt to acquire or release a

 ** lock outside of this range

 */

 #define SQLITE_SHM_NLOCK        8

 /*

 ** CAPI3REF: Initialize The SQLite Library

 **

 ** ^The sqlite3_initialize() routine initializes the

 ** SQLite library.  ^The sqlite3_shutdown() routine

 ** deallocates any resources that were allocated by sqlite3_initialize().

 ** These routines are designed to aid in process initialization and

 ** shutdown on embedded systems.  Workstation applications using

 ** SQLite normally do not need to invoke either of these routines.

 **

 ** A call to sqlite3_initialize() is an "effective" call if it is

 ** the first time sqlite3_initialize() is invoked during the lifetime of

 ** the process, or if it is the first time sqlite3_initialize() is invoked

 ** following a call to sqlite3_shutdown().  ^(Only an effective call

 ** of sqlite3_initialize() does any initialization.  All other calls

 ** are harmless no-ops.)^

 **

 ** A call to sqlite3_shutdown() is an "effective" call if it is the first

 ** call to sqlite3_shutdown() since the last sqlite3_initialize().  ^(Only

 ** an effective call to sqlite3_shutdown() does any deinitialization.

 ** All other valid calls to sqlite3_shutdown() are harmless no-ops.)^

 **

 ** The sqlite3_initialize() interface is threadsafe, but sqlite3_shutdown()

 ** is not.  The sqlite3_shutdown() interface must only be called from a

 ** single thread.  All open [database connections] must be closed and all

 ** other SQLite resources must be deallocated prior to invoking

 ** sqlite3_shutdown().

 **

 ** Among other things, ^sqlite3_initialize() will invoke

 ** sqlite3_os_init().  Similarly, ^sqlite3_shutdown()

 ** will invoke sqlite3_os_end().

 **

 ** ^The sqlite3_initialize() routine returns [SQLITE_OK] on success.

 ** ^If for some reason, sqlite3_initialize() is unable to initialize

 ** the library (perhaps it is unable to allocate a needed resource such

 ** as a mutex) it returns an [error code] other than [SQLITE_OK].

 **

 ** ^The sqlite3_initialize() routine is called internally by many other

 ** SQLite interfaces so that an application usually does not need to

 ** invoke sqlite3_initialize() directly.  For example, [sqlite3_open()]

 ** calls sqlite3_initialize() so the SQLite library will be automatically

 ** initialized when [sqlite3_open()] is called if it has not be initialized

 ** already.  ^However, if SQLite is compiled with the [SQLITE_OMIT_AUTOINIT]

 ** compile-time option, then the automatic calls to sqlite3_initialize()

 ** are omitted and the application must call sqlite3_initialize() directly

 ** prior to using any other SQLite interface.  For maximum portability,

 ** it is recommended that applications always invoke sqlite3_initialize()

 ** directly prior to using any other SQLite interface.  Future releases

 ** of SQLite may require this.  In other words, the behavior exhibited

 ** when SQLite is compiled with [SQLITE_OMIT_AUTOINIT] might become the

 ** default behavior in some future release of SQLite.

 **

 ** The sqlite3_os_init() routine does operating-system specific

 ** initialization of the SQLite library.  The sqlite3_os_end()

 ** routine undoes the effect of sqlite3_os_init().  Typical tasks

 ** performed by these routines include allocation or deallocation

 ** of static resources, initialization of global variables,

 ** setting up a default [sqlite3_vfs] module, or setting up

 ** a default configuration using [sqlite3_config()].

 **

 ** The application should never invoke either sqlite3_os_init()

 ** or sqlite3_os_end() directly.  The application should only invoke

 ** sqlite3_initialize() and sqlite3_shutdown().  The sqlite3_os_init()

 ** interface is called automatically by sqlite3_initialize() and

 ** sqlite3_os_end() is called by sqlite3_shutdown().  Appropriate

 ** implementations for sqlite3_os_init() and sqlite3_os_end()

 ** are built into SQLite when it is compiled for Unix, Windows, or OS/2.

 ** When [custom builds | built for other platforms]

 ** (using the [SQLITE_OS_OTHER=1] compile-time

 ** option) the application must supply a suitable implementation for

 ** sqlite3_os_init() and sqlite3_os_end().  An application-supplied

 ** implementation of sqlite3_os_init() or sqlite3_os_end()

 ** must return [SQLITE_OK] on success and some other [error code] upon

 ** failure.

 */

 SQLITE_API int sqlite3_initialize(void);

 SQLITE_API int sqlite3_shutdown(void);

 SQLITE_API int sqlite3_os_init(void);

 SQLITE_API int sqlite3_os_end(void);

 /*

 ** CAPI3REF: Configuring The SQLite Library

 **

 ** The sqlite3_config() interface is used to make global configuration

 ** changes to SQLite in order to tune SQLite to the specific needs of

 ** the application.  The default configuration is recommended for most

 ** applications and so this routine is usually not necessary.  It is

 ** provided to support rare applications with unusual needs.

 **

 ** <b>The sqlite3_config() interface is not threadsafe. The application

 ** must ensure that no other SQLite interfaces are invoked by other

 ** threads while sqlite3_config() is running.</b>

 **

 ** The sqlite3_config() interface

 ** may only be invoked prior to library initialization using

 ** [sqlite3_initialize()] or after shutdown by [sqlite3_shutdown()].

 ** ^If sqlite3_config() is called after [sqlite3_initialize()] and before

 ** [sqlite3_shutdown()] then it will return SQLITE_MISUSE.

 ** Note, however, that ^sqlite3_config() can be called as part of the

 ** implementation of an application-defined [sqlite3_os_init()].

 **

 ** The first argument to sqlite3_config() is an integer

 ** [configuration option] that determines

 ** what property of SQLite is to be configured.  Subsequent arguments

 ** vary depending on the [configuration option]

 ** in the first argument.

 **

 ** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK].

 ** ^If the option is unknown or SQLite is unable to set the option

 ** then this routine returns a non-zero [error code].

 */

 SQLITE_API int sqlite3_config(int, ...);

 /*

 ** CAPI3REF: Configure database connections

 ** METHOD: sqlite3

 **

 ** The sqlite3_db_config() interface is used to make configuration

 ** changes to a [database connection].  The interface is similar to

 ** [sqlite3_config()] except that the changes apply to a single

 ** [database connection] (specified in the first argument).

 **

 ** The second argument to sqlite3_db_config(D,V,...)  is the

 ** [SQLITE_DBCONFIG_LOOKASIDE | configuration verb] - an integer code 

 ** that indicates what aspect of the [database connection] is being configured.

 ** Subsequent arguments vary depending on the configuration verb.

 **

 ** ^Calls to sqlite3_db_config() return SQLITE_OK if and only if

 ** the call is considered successful.

 */

 SQLITE_API int sqlite3_db_config(sqlite3*, int op, ...);

 /*

 ** CAPI3REF: Memory Allocation Routines

 **

 ** An instance of this object defines the interface between SQLite

 ** and low-level memory allocation routines.

 **

 ** This object is used in only one place in the SQLite interface.

 ** A pointer to an instance of this object is the argument to

 ** [sqlite3_config()] when the configuration option is

 ** [SQLITE_CONFIG_MALLOC] or [SQLITE_CONFIG_GETMALLOC].  

 ** By creating an instance of this object

 ** and passing it to [sqlite3_config]([SQLITE_CONFIG_MALLOC])

 ** during configuration, an application can specify an alternative

 ** memory allocation subsystem for SQLite to use for all of its

 ** dynamic memory needs.

 **

 ** Note that SQLite comes with several [built-in memory allocators]

 ** that are perfectly adequate for the overwhelming majority of applications

 ** and that this object is only useful to a tiny minority of applications

 ** with specialized memory allocation requirements.  This object is

 ** also used during testing of SQLite in order to specify an alternative

 ** memory allocator that simulates memory out-of-memory conditions in

 ** order to verify that SQLite recovers gracefully from such

 ** conditions.

 **

 ** The xMalloc, xRealloc, and xFree methods must work like the

 ** malloc(), realloc() and free() functions from the standard C library.

 ** ^SQLite guarantees that the second argument to

 ** xRealloc is always a value returned by a prior call to xRoundup.

 **

 ** xSize should return the allocated size of a memory allocation

 ** previously obtained from xMalloc or xRealloc.  The allocated size

 ** is always at least as big as the requested size but may be larger.

 **

 ** The xRoundup method returns what would be the allocated size of

 ** a memory allocation given a particular requested size.  Most memory

 ** allocators round up memory allocations at least to the next multiple

 ** of 8.  Some allocators round up to a larger multiple or to a power of 2.

 ** Every memory allocation request coming in through [sqlite3_malloc()]

 ** or [sqlite3_realloc()] first calls xRoundup.  If xRoundup returns 0, 

 ** that causes the corresponding memory allocation to fail.

 **

 ** The xInit method initializes the memory allocator.  For example,

 ** it might allocate any require mutexes or initialize internal data

 ** structures.  The xShutdown method is invoked (indirectly) by

 ** [sqlite3_shutdown()] and should deallocate any resources acquired

 ** by xInit.  The pAppData pointer is used as the only parameter to

 ** xInit and xShutdown.