minetest.git - modified minetest for gpcfs purposes

about summary refs log tree commit diff

path: root/src/script/cpp_api/s_security.h

diff options

Diffstat (limited to 'src/script/cpp_api/s_security.h')

0 files changed, 0 insertions, 0 deletions

e 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

@@ -650,9 +650,9 @@ extern "C" {

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

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

-#define SQLITE_VERSION "3.7.6.3"

-#define SQLITE_VERSION_NUMBER 3007006

-#define SQLITE_SOURCE_ID "2011-05-19 13:26:54 ed1da510a239ea767a01dc332b667119fa3c908e"

+#define SQLITE_VERSION "3.7.7.1"

+#define SQLITE_VERSION_NUMBER 3007007

+#define SQLITE_SOURCE_ID "2011-06-28 17:39:05 af0d91adf497f5f36ec3813f04235a6e195a605f"

** CAPI3REF: Run-Time Library Version Numbers

@@ -853,7 +853,7 @@ typedef int (*sqlite3_callback)(void*,int,char**, char**);

** 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

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

+** 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.

@@ -918,7 +918,8 @@ SQLITE_API int sqlite3_exec(

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

-** See also: [SQLITE_IOERR_READ | extended result codes]

+** See also: [SQLITE_IOERR_READ | extended result codes],

+** [sqlite3_vtab_on_conflict()] [SQLITE_ROLLBACK | result codes].

#define SQLITE_OK 0 /* Successful result */

/* beginning-of-error-codes */

@@ -995,17 +996,21 @@ SQLITE_API int sqlite3_exec(

#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_LOCKED_SHAREDCACHE (SQLITE_LOCKED | (1<<8))

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

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

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

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

+#define SQLITE_READONLY_CANTLOCK (SQLITE_READONLY | (2<<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 xOpen method of the

-** [sqlite3_vfs] object.

+** 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() */

@@ -1013,6 +1018,7 @@ SQLITE_API int sqlite3_exec(

#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_MAIN_DB 0x00000100 /* VFS only */

#define SQLITE_OPEN_TEMP_DB 0x00000200 /* VFS only */

#define SQLITE_OPEN_TRANSIENT_DB 0x00000400 /* VFS only */

@@ -1123,17 +1129,18 @@ struct sqlite3_file {

** CAPI3REF: OS Interface File Virtual Methods Object

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

+** 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 xOpen method sets the sqlite3_file.pMethods element

+** 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 xOpen reported that it failed. The

-** only way to prevent a call to xClose following a failed xOpen

-** is for the xOpen to set the sqlite3_file.pMethods element to NULL.

+** 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().

@@ -1305,7 +1312,8 @@ typedef struct sqlite3_mutex sqlite3_mutex;

** 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".

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

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

** The value of the iVersion field is initially 1 but may be larger in

** future versions of SQLite. Additional fields may be appended to this

@@ -1334,6 +1342,7 @@ typedef struct sqlite3_mutex sqlite3_mutex;

** 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.

@@ -1411,6 +1420,7 @@ typedef struct sqlite3_mutex sqlite3_mutex;

** 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]

@@ -1435,7 +1445,7 @@ typedef struct sqlite3_mutex sqlite3_mutex;

** 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 multipled by 86400000 (the number of milliseconds in

+** 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

@@ -1657,9 +1667,9 @@ SQLITE_API int sqlite3_os_end(void);

** implementation of an application-defined [sqlite3_os_init()].

** The first argument to sqlite3_config() is an integer

-** [SQLITE_CONFIG_SINGLETHREAD | configuration option] that determines

+** [configuration option] that determines

** what property of SQLite is to be configured. Subsequent arguments

-** vary depending on the [SQLITE_CONFIG_SINGLETHREAD | configuration option]

+** vary depending on the [configuration option]

** in the first argument.

** ^When a configuration option is set, sqlite3_config() returns [SQLITE_OK].

@@ -1769,6 +1779,7 @@ struct sqlite3_mem_methods {

** CAPI3REF: Configuration Options

+** KEYWORDS: {configuration option}

** These constants are the available integer configuration options that

** can be passed as the first argument to the [sqlite3_config()] interface.

@@ -1781,7 +1792,7 @@ struct sqlite3_mem_methods {

** is invoked.

** <dl>

-** <dt>SQLITE_CONFIG_SINGLETHREAD</dt>

+** [[SQLITE_CONFIG_SINGLETHREAD]] <dt>SQLITE_CONFIG_SINGLETHREAD</dt>

** <dd>There are no arguments to this option. ^This option sets the

** [threading mode] to Single-thread. In other words, it disables

** all mutexing and puts SQLite into a mode where it can only be used

@@ -1792,7 +1803,7 @@ struct sqlite3_mem_methods {

** [SQLITE_ERROR] if called with the SQLITE_CONFIG_SINGLETHREAD

** configuration option.</dd>

-** <dt>SQLITE_CONFIG_MULTITHREAD</dt>

+** [[SQLITE_CONFIG_MULTITHREAD]] <dt>SQLITE_CONFIG_MULTITHREAD</dt>

** <dd>There are no arguments to this option. ^This option sets the

** [threading mode] to Multi-thread. In other words, it disables

** mutexing on [database connection] and [prepared statement] objects.

@@ -1806,7 +1817,7 @@ struct sqlite3_mem_methods {

** [sqlite3_config()] will return [SQLITE_ERROR] if called with the

** SQLITE_CONFIG_MULTITHREAD configuration option.</dd>

-** <dt>SQLITE_CONFIG_SERIALIZED</dt>

+** [[SQLITE_CONFIG_SERIALIZED]] <dt>SQLITE_CONFIG_SERIALIZED</dt>

** <dd>There are no arguments to this option. ^This option sets the

** [threading mode] to Serialized. In other words, this option enables

** all mutexes including the recursive

@@ -1822,7 +1833,7 @@ struct sqlite3_mem_methods {

** [sqlite3_config()] will return [SQLITE_ERROR] if called with the

** SQLITE_CONFIG_SERIALIZED configuration option.</dd>

-** <dt>SQLITE_CONFIG_MALLOC</dt>

+** [[SQLITE_CONFIG_MALLOC]] <dt>SQLITE_CONFIG_MALLOC</dt>

** <dd> ^(This option takes a single argument which is a pointer to an

** instance of the [sqlite3_mem_methods] structure. The argument specifies

** alternative low-level memory allocation routines to be used in place of

@@ -1830,7 +1841,7 @@ struct sqlite3_mem_methods {

** its own private copy of the content of the [sqlite3_mem_methods] structure

** before the [sqlite3_config()] call returns.</dd>

-** <dt>SQLITE_CONFIG_GETMALLOC</dt>

+** [[SQLITE_CONFIG_GETMALLOC]] <dt>SQLITE_CONFIG_GETMALLOC</dt>

** <dd> ^(This option takes a single argument which is a pointer to an

** instance of the [sqlite3_mem_methods] structure. The [sqlite3_mem_methods]

** structure is filled with the currently defined memory allocation routines.)^

@@ -1838,7 +1849,7 @@ struct sqlite3_mem_methods {

** routines with a wrapper that simulations memory allocation failure or

** tracks memory usage, for example. </dd>

-** <dt>SQLITE_CONFIG_MEMSTATUS</dt>

+** [[SQLITE_CONFIG_MEMSTATUS]] <dt>SQLITE_CONFIG_MEMSTATUS</dt>

** <dd> ^This option takes single argument of type int, interpreted as a

** boolean, which enables or disables the collection of memory allocation

** statistics. ^(When memory allocation statistics are disabled, the

@@ -1854,7 +1865,7 @@ struct sqlite3_mem_methods {

** allocation statistics are disabled by default.

** </dd>

-** <dt>SQLITE_CONFIG_SCRATCH</dt>

+** [[SQLITE_CONFIG_SCRATCH]] <dt>SQLITE_CONFIG_SCRATCH</dt>

** <dd> ^This option specifies a static memory buffer that SQLite can use for

** scratch memory. There are three arguments: A pointer an 8-byte

** aligned memory buffer from which the scratch allocations will be

@@ -1870,9 +1881,9 @@ struct sqlite3_mem_methods {

** scratch memory beyond what is provided by this configuration option, then

** [sqlite3_malloc()] will be used to obtain the memory needed.</dd>

-** <dt>SQLITE_CONFIG_PAGECACHE</dt>

+** [[SQLITE_CONFIG_PAGECACHE]] <dt>SQLITE_CONFIG_PAGECACHE</dt>

** <dd> ^This option specifies a static memory buffer that SQLite can use for

-** the database page cache with the default page cache implemenation.

+** the database page cache with the default page cache implementation.

** This configuration should not be used if an application-define page

** cache implementation is loaded using the SQLITE_CONFIG_PCACHE option.

** There are three arguments to this option: A pointer to 8-byte aligned

@@ -1891,7 +1902,7 @@ struct sqlite3_mem_methods {

** be aligned to an 8-byte boundary or subsequent behavior of SQLite

** will be undefined.</dd>

-** <dt>SQLITE_CONFIG_HEAP</dt>

+** [[SQLITE_CONFIG_HEAP]] <dt>SQLITE_CONFIG_HEAP</dt>

** <dd> ^This option specifies a static memory buffer that SQLite will use

** for all of its dynamic memory allocation needs beyond those provided

** for by [SQLITE_CONFIG_SCRATCH] and [SQLITE_CONFIG_PAGECACHE].

@@ -1908,7 +1919,7 @@ struct sqlite3_mem_methods {

** The minimum allocation size is capped at 2^12. Reasonable values

** for the minimum allocation size are 2^5 through 2^8.</dd>

-** <dt>SQLITE_CONFIG_MUTEX</dt>

+** [[SQLITE_CONFIG_MUTEX]] <dt>SQLITE_CONFIG_MUTEX</dt>

** <dd> ^(This option takes a single argument which is a pointer to an

** instance of the [sqlite3_mutex_methods] structure. The argument specifies

** alternative low-level mutex routines to be used in place

@@ -1920,7 +1931,7 @@ struct sqlite3_mem_methods {

** [sqlite3_config()] with the SQLITE_CONFIG_MUTEX configuration option will

** return [SQLITE_ERROR].</dd>

-** <dt>SQLITE_CONFIG_GETMUTEX</dt>

+** [[SQLITE_CONFIG_GETMUTEX]] <dt>SQLITE_CONFIG_GETMUTEX</dt>

** <dd> ^(This option takes a single argument which is a pointer to an

** instance of the [sqlite3_mutex_methods] structure. The

** [sqlite3_mutex_methods]

@@ -1933,7 +1944,7 @@ struct sqlite3_mem_methods {

** [sqlite3_config()] with the SQLITE_CONFIG_GETMUTEX configuration option will

** return [SQLITE_ERROR].</dd>

-** <dt>SQLITE_CONFIG_LOOKASIDE</dt>

+** [[SQLITE_CONFIG_LOOKASIDE]] <dt>SQLITE_CONFIG_LOOKASIDE</dt>

** <dd> ^(This option takes two arguments that determine the default

** memory allocation for the lookaside memory allocator on each

** [database connection]. The first argument is the

@@ -1943,18 +1954,18 @@ struct sqlite3_mem_methods {

** verb to [sqlite3_db_config()] can be used to change the lookaside

** configuration on individual connections.)^ </dd>

-** <dt>SQLITE_CONFIG_PCACHE</dt>

+** [[SQLITE_CONFIG_PCACHE]] <dt>SQLITE_CONFIG_PCACHE</dt>

** <dd> ^(This option takes a single argument which is a pointer to

** an [sqlite3_pcache_methods] object. This object specifies the interface

** to a custom page cache implementation.)^ ^SQLite makes a copy of the

** object and uses it for page cache memory allocations.</dd>

-** <dt>SQLITE_CONFIG_GETPCACHE</dt>

+** [[SQLITE_CONFIG_GETPCACHE]] <dt>SQLITE_CONFIG_GETPCACHE</dt>

** <dd> ^(This option takes a single argument which is a pointer to an

** [sqlite3_pcache_methods] object. SQLite copies of the current

** page cache implementation into that object.)^ </dd>

-** <dt>SQLITE_CONFIG_LOG</dt>

+** [[SQLITE_CONFIG_LOG]] <dt>SQLITE_CONFIG_LOG</dt>

** <dd> ^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a

** function with a call signature of void(*)(void*,int,const char*),

** and a pointer to void. ^If the function pointer is not NULL, it is

@@ -1972,6 +1983,18 @@ struct sqlite3_mem_methods {

** In a multi-threaded application, the application-defined logger

** function must be threadsafe. </dd>

+** [[SQLITE_CONFIG_URI]] <dt>SQLITE_CONFIG_URI

+** <dd> This option takes a single argument of type int. If non-zero, then

+** URI handling is globally enabled. If the parameter is zero, then URI handling

+** is globally disabled. If URI handling is globally enabled, all filenames

+** passed to [sqlite3_open()], [sqlite3_open_v2()], [sqlite3_open16()] or

+** specified as part of [ATTACH] commands are interpreted as URIs, regardless

+** of whether or not the [SQLITE_OPEN_URI] flag is set when the database

+** connection is opened. If it is globally disabled, filenames are

+** only interpreted as URIs if the SQLITE_OPEN_URI flag is set when the

+** database connection is opened. By default, URI handling is globally

+** disabled. The default value may be changed by compiling with the

+** [SQLITE_USE_URI] symbol defined.

** </dl>

#define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */

@@ -1990,6 +2013,7 @@ struct sqlite3_mem_methods {

#define SQLITE_CONFIG_PCACHE 14 /* sqlite3_pcache_methods* */

#define SQLITE_CONFIG_GETPCACHE 15 /* sqlite3_pcache_methods* */

#define SQLITE_CONFIG_LOG 16 /* xFunc, void* */

+#define SQLITE_CONFIG_URI 17 /* int */

** CAPI3REF: Database Connection Configuration Options

@@ -2075,13 +2099,17 @@ SQLITE_API int sqlite3_extended_result_codes(sqlite3*, int onoff);

** ^This routine returns the [rowid] of the most recent

** successful [INSERT] into the database from the [database connection]

-** in the first argument. ^If no successful [INSERT]s

+** in the first argument. ^As of SQLite version 3.7.7, this routines

+** records the last insert rowid of both ordinary tables and [virtual tables].

+** ^If no successful [INSERT]s

** have ever occurred on that database connection, zero is returned.

-** ^(If an [INSERT] occurs within a trigger, then the [rowid] of the inserted

-** row is returned by this routine as long as the trigger is running.

-** But once the trigger terminates, the value returned by this routine

-** reverts to the last value inserted before the trigger fired.)^

+** ^(If an [INSERT] occurs within a trigger or within a [virtual table]

+** method, then this routine will return the [rowid] of the inserted

+** row as long as the trigger or virtual table method is running.

+** But once the trigger or virtual table method ends, the value returned

+** by this routine reverts to what it was before the trigger or virtual

+** table method began.)^

** ^An [INSERT] that fails due to a constraint violation is not a

** successful [INSERT] and does not change the value returned by this

@@ -2744,6 +2772,9 @@ SQLITE_API int sqlite3_set_authorizer(

** to signal SQLite whether or not the action is permitted. See the

** [sqlite3_set_authorizer | authorizer documentation] for additional

** information.

+**

+** Note that SQLITE_IGNORE is also used as a [SQLITE_ROLLBACK | return code]

+** from the [sqlite3_vtab_on_conflict()] interface.

#define SQLITE_DENY 1 /* Abort the SQL statement with an error */

#define SQLITE_IGNORE 2 /* Don't allow access, but don't generate an error */

@@ -2866,7 +2897,7 @@ SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);

** CAPI3REF: Opening A New Database Connection

-** ^These routines open an SQLite database file whose name is given by the

+** ^These routines open an SQLite database file as specified by the

** filename argument. ^The filename argument is interpreted as UTF-8 for

** sqlite3_open() and sqlite3_open_v2() and as UTF-16 in the native byte

** order for sqlite3_open16(). ^(A [database connection] handle is usually

@@ -2893,7 +2924,7 @@ SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);

** sqlite3_open_v2() can take one of

** the following three values, optionally combined with the

** [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX], [SQLITE_OPEN_SHAREDCACHE],

-** and/or [SQLITE_OPEN_PRIVATECACHE] flags:)^

+** [SQLITE_OPEN_PRIVATECACHE], and/or [SQLITE_OPEN_URI] flags:)^

** <dl>

** ^(<dt>[SQLITE_OPEN_READONLY]</dt>

@@ -2912,9 +2943,8 @@ SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);

** </dl>

** If the 3rd parameter to sqlite3_open_v2() is not one of the

-** combinations shown above or one of the combinations shown above combined

-** with the [SQLITE_OPEN_NOMUTEX], [SQLITE_OPEN_FULLMUTEX],

-** [SQLITE_OPEN_SHAREDCACHE] and/or [SQLITE_OPEN_PRIVATECACHE] flags,

+** combinations shown above optionally combined with other

+** [SQLITE_OPEN_READONLY | SQLITE_OPEN_* bits]

** then the behavior is undefined.

** ^If the [SQLITE_OPEN_NOMUTEX] flag is set, then the database connection

@@ -2929,6 +2959,11 @@ SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);

** [SQLITE_OPEN_PRIVATECACHE] flag causes the database connection to not

** participate in [shared cache mode] even if it is enabled.

+** ^The fourth parameter to sqlite3_open_v2() is the name of the

+** [sqlite3_vfs] object that defines the operating system interface that

+** the new database connection should use. ^If the fourth parameter is

+** a NULL pointer then the default [sqlite3_vfs] object is used.

+**

** ^If the filename is ":memory:", then a private, temporary in-memory database

** is created for the connection. ^This in-memory database will vanish when

** the database connection is closed. Future versions of SQLite might

@@ -2941,10 +2976,111 @@ SQLITE_API void sqlite3_progress_handler(sqlite3*, int, int(*)(void*), void*);

** on-disk database will be created. ^This private database will be

** automatically deleted as soon as the database connection is closed.

-** ^The fourth parameter to sqlite3_open_v2() is the name of the

-** [sqlite3_vfs] object that defines the operating system interface that

-** the new database connection should use. ^If the fourth parameter is

-** a NULL pointer then the default [sqlite3_vfs] object is used.

+** [[URI filenames in sqlite3_open()]] <h3>URI Filenames</h3>

+**

+** ^If [URI filename] interpretation is enabled, and the filename argument

+** begins with "file:", then the filename is interpreted as a URI. ^URI

+** filename interpretation is enabled if the [SQLITE_OPEN_URI] flag is

+** set in the fourth argument to sqlite3_open_v2(), or if it has

+** been enabled globally using the [SQLITE_CONFIG_URI] option with the

+** [sqlite3_config()] method or by the [SQLITE_USE_URI] compile-time option.

+** As of SQLite version 3.7.7, URI filename interpretation is turned off

+** by default, but future releases of SQLite might enable URI filename

+** interpretation by default. See "[URI filenames]" for additional

+** information.

+**

+** URI filenames are parsed according to RFC 3986. ^If the URI contains an

+** authority, then it must be either an empty string or the string

+** "localhost". ^If the authority is not an empty string or "localhost", an

+** error is returned to the caller. ^The fragment component of a URI, if

+** present, is ignored.

+**

+** ^SQLite uses the path component of the URI as the name of the disk file

+** which contains the database. ^If the path begins with a '/' character,

+** then it is interpreted as an absolute path. ^If the path does not begin

+** with a '/' (meaning that the authority section is omitted from the URI)

+** then the path is interpreted as a relative path.

+** ^On windows, the first component of an absolute path

+** is a drive specification (e.g. "C:").

+**

+** [[core URI query parameters]]

+** The query component of a URI may contain parameters that are interpreted

+** either by SQLite itself, or by a [VFS | custom VFS implementation].

+** SQLite interprets the following three query parameters:

+**

+** <ul>

+** <li> <b>vfs</b>: ^The "vfs" parameter may be used to specify the name of

+** a VFS object that provides the operating system interface that should

+** be used to access the database file on disk. ^If this option is set to

+** an empty string the default VFS object is used. ^Specifying an unknown

+** VFS is an error. ^If sqlite3_open_v2() is used and the vfs option is

+** present, then the VFS specified by the option takes precedence over

+** the value passed as the fourth parameter to sqlite3_open_v2().

+**

+** <li> <b>mode</b>: ^(The mode parameter may be set to either "ro", "rw" or

+** "rwc". Attempting to set it to any other value is an error)^.

+** ^If "ro" is specified, then the database is opened for read-only

+** access, just as if the [SQLITE_OPEN_READONLY] flag had been set in the

+** third argument to sqlite3_prepare_v2(). ^If the mode option is set to

+** "rw", then the database is opened for read-write (but not create)

+** access, as if SQLITE_OPEN_READWRITE (but not SQLITE_OPEN_CREATE) had

+** been set. ^Value "rwc" is equivalent to setting both

+** SQLITE_OPEN_READWRITE and SQLITE_OPEN_CREATE. ^If sqlite3_open_v2() is

+** used, it is an error to specify a value for the mode parameter that is

+** less restrictive than that specified by the flags passed as the third

+** parameter.

+**

+** <li> <b>cache</b>: ^The cache parameter may be set to either "shared" or

+** "private". ^Setting it to "shared" is equivalent to setting the

+** SQLITE_OPEN_SHAREDCACHE bit in the flags argument passed to

+** sqlite3_open_v2(). ^Setting the cache parameter to "private" is

+** equivalent to setting the SQLITE_OPEN_PRIVATECACHE bit.

+** ^If sqlite3_open_v2() is used and the "cache" parameter is present in

+** a URI filename, its value overrides any behaviour requested by setting

+** SQLITE_OPEN_PRIVATECACHE or SQLITE_OPEN_SHAREDCACHE flag.

+** </ul>

+**

+** ^Specifying an unknown parameter in the query component of a URI is not an

+** error. Future versions of SQLite might understand additional query

+** parameters. See "[query parameters with special meaning to SQLite]" for

+** additional information.

+**

+** [[URI filename examples]] <h3>URI filename examples</h3>

+**

+** <table border="1" align=center cellpadding=5>

+** <tr><th> URI filenames <th> Results

+** <tr><td> file:data.db <td>

+** Open the file "data.db" in the current directory.

+** <tr><td> file:/home/fred/data.db<br>

+** file:///home/fred/data.db <br>

+** file://localhost/home/fred/data.db <br> <td>

+** Open the database file "/home/fred/data.db".

+** <tr><td> file://darkstar/home/fred/data.db <td>

+** An error. "darkstar" is not a recognized authority.

+** <tr><td style="white-space:nowrap">

+** file:///C:/Documents%20and%20Settings/fred/Desktop/data.db

+** <td> Windows only: Open the file "data.db" on fred's desktop on drive

+** C:. Note that the %20 escaping in this example is not strictly

+** necessary - space characters can be used literally

+** in URI filenames.

+** <tr><td> file:data.db?mode=ro&cache=private <td>

+** Open file "data.db" in the current directory for read-only access.

+** Regardless of whether or not shared-cache mode is enabled by

+** default, use a private cache.

+** <tr><td> file:/home/fred/data.db?vfs=unix-nolock <td>

+** Open file "/home/fred/data.db". Use the special VFS "unix-nolock".

+** <tr><td> file:data.db?mode=readonly <td>

+** An error. "readonly" is not a valid option for the "mode" parameter.

+** </table>

+**

+** ^URI hexadecimal escape sequences (%HH) are supported within the path and

+** query components of a URI. A hexadecimal escape sequence consists of a

+** percent sign - "%" - followed by exactly two hexadecimal digits

+** specifying an octet value. ^Before the path or query components of a

+** URI filename are interpreted, they are encoded using UTF-8 and all

+** hexadecimal escape sequences replaced by a single byte containing the

+** corresponding octet. If this process generates an invalid UTF-8 encoding,

+** the results are undefined.

** <b>Note to Windows users:</b> The encoding used for the filename argument

** of sqlite3_open() and sqlite3_open_v2() must be UTF-8, not whatever

@@ -2968,6 +3104,26 @@ SQLITE_API int sqlite3_open_v2(

);

+** CAPI3REF: Obtain Values For URI Parameters

+**

+** This is a utility routine, useful to VFS implementations, that checks

+** to see if a database file was a URI that contained a specific query

+** parameter, and if so obtains the value of the query parameter.

+**

+** The zFilename argument is the filename pointer passed into the xOpen()

+** method of a VFS implementation. The zParam argument is the name of the

+** query parameter we seek. This routine returns the value of the zParam

+** parameter if it exists. If the parameter does not exist, this routine

+** returns a NULL pointer.

+**

+** If the zFilename argument to this function is not a pointer that SQLite

+** passed into the xOpen VFS method, then the behavior of this routine

+** is undefined and probably undesirable.

+*/

+SQLITE_API const char *sqlite3_uri_parameter(const char *zFilename, const char *zParam);

+/*

** CAPI3REF: Error Codes And Messages

** ^The sqlite3_errcode() interface returns the numeric [result code] or

@@ -3082,43 +3238,45 @@ SQLITE_API int sqlite3_limit(sqlite3*, int id, int newVal);

** Additional information is available at [limits | Limits in SQLite].

** <dl>

-** ^(<dt>SQLITE_LIMIT_LENGTH</dt>

+** [[SQLITE_LIMIT_LENGTH]] ^(<dt>SQLITE_LIMIT_LENGTH</dt>

** <dd>The maximum size of any string or BLOB or table row, in bytes.<dd>)^

-** ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt>

+** [[SQLITE_LIMIT_SQL_LENGTH]] ^(<dt>SQLITE_LIMIT_SQL_LENGTH</dt>

** <dd>The maximum length of an SQL statement, in bytes.</dd>)^

-** ^(<dt>SQLITE_LIMIT_COLUMN</dt>

+** [[SQLITE_LIMIT_COLUMN]] ^(<dt>SQLITE_LIMIT_COLUMN</dt>

** <dd>The maximum number of columns in a table definition or in the

** result set of a [SELECT] or the maximum number of columns in an index

** or in an ORDER BY or GROUP BY clause.</dd>)^

-** ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt>

+** [[SQLITE_LIMIT_EXPR_DEPTH]] ^(<dt>SQLITE_LIMIT_EXPR_DEPTH</dt>

** <dd>The maximum depth of the parse tree on any expression.</dd>)^

-** ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt>

+** [[SQLITE_LIMIT_COMPOUND_SELECT]] ^(<dt>SQLITE_LIMIT_COMPOUND_SELECT</dt>

** <dd>The maximum number of terms in a compound SELECT statement.</dd>)^

-** ^(<dt>SQLITE_LIMIT_VDBE_OP</dt>

+** [[SQLITE_LIMIT_VDBE_OP]] ^(<dt>SQLITE_LIMIT_VDBE_OP</dt>

** <dd>The maximum number of instructions in a virtual machine program

** used to implement an SQL statement. This limit is not currently

** enforced, though that might be added in some future release of

** SQLite.</dd>)^

-** ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt>

+** [[SQLITE_LIMIT_FUNCTION_ARG]] ^(<dt>SQLITE_LIMIT_FUNCTION_ARG</dt>

** <dd>The maximum number of arguments on a function.</dd>)^

-** ^(<dt>SQLITE_LIMIT_ATTACHED</dt>

+** [[SQLITE_LIMIT_ATTACHED]] ^(<dt>SQLITE_LIMIT_ATTACHED</dt>

** <dd>The maximum number of [ATTACH | attached databases].)^</dd>

+** [[SQLITE_LIMIT_LIKE_PATTERN_LENGTH]]

** ^(<dt>SQLITE_LIMIT_LIKE_PATTERN_LENGTH</dt>

** <dd>The maximum length of the pattern argument to the [LIKE] or

** [GLOB] operators.</dd>)^

+** [[SQLITE_LIMIT_VARIABLE_NUMBER]]

** ^(<dt>SQLITE_LIMIT_VARIABLE_NUMBER</dt>

** <dd>The maximum index number of any [parameter] in an SQL statement.)^

-** ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt>

+** [[SQLITE_LIMIT_TRIGGER_DEPTH]] ^(<dt>SQLITE_LIMIT_TRIGGER_DEPTH</dt>

** <dd>The maximum depth of recursion for triggers.</dd>)^

** </dl>

@@ -3647,7 +3805,7 @@ SQLITE_API const void *sqlite3_column_decltype16(sqlite3_stmt*,int);

** ^[SQLITE_BUSY] means that the database engine was unable to acquire the

** database locks it needs to do its job. ^If the statement is a [COMMIT]

** or occurs outside of an explicit transaction, then you can retry the

-** statement. If the statement is not a [COMMIT] and occurs within a

+** statement. If the statement is not a [COMMIT] and occurs within an

** explicit transaction then you should rollback the transaction before

** continuing.

@@ -3926,7 +4084,7 @@ SQLITE_API sqlite3_value *sqlite3_column_value(sqlite3_stmt*, int iCol);

** CAPI3REF: Destroy A Prepared Statement Object

** ^The sqlite3_finalize() function is called to delete a [prepared statement].

-** ^If the most recent evaluation of the statement encountered no errors or

+** ^If the most recent evaluation of the statement encountered no errors

** or if the statement is never been evaluated, then sqlite3_finalize() returns

** SQLITE_OK. ^If the most recent evaluation of statement S failed, then

** sqlite3_finalize(S) returns the appropriate [error code] or

@@ -5153,6 +5311,11 @@ struct sqlite3_module {

void (**pxFunc)(sqlite3_context*,int,sqlite3_value**),

void **ppArg);

int (*xRename)(sqlite3_vtab *pVtab, const char *zNew);

+ /* The methods above are in version 1 of the sqlite_module object. Those

+ ** below are for version 2 and greater. */

+ int (*xSavepoint)(sqlite3_vtab *pVTab, int);

+ int (*xRelease)(sqlite3_vtab *pVTab, int);

+ int (*xRollbackTo)(sqlite3_vtab *pVTab, int);

};

@@ -5835,7 +5998,7 @@ struct sqlite3_mutex_methods {

** ^If the argument to sqlite3_mutex_held() is a NULL pointer then

** the routine should return 1. This seems counter-intuitive since

-** clearly the mutex cannot be held if it does not exist. But the

+** clearly the mutex cannot be held if it does not exist. But

** the reason the mutex does not exist is because the build is not

** using mutexes. And we do not want the assert() containing the

** call to sqlite3_mutex_held() to fail, so a non-zero return is

@@ -5958,7 +6121,8 @@ SQLITE_API int sqlite3_test_control(int op, ...);

#define SQLITE_TESTCTRL_ISKEYWORD 16

#define SQLITE_TESTCTRL_PGHDRSZ 17

#define SQLITE_TESTCTRL_SCRATCHMALLOC 18

-#define SQLITE_TESTCTRL_LAST 18

+#define SQLITE_TESTCTRL_LOCALTIME_FAULT 19

+#define SQLITE_TESTCTRL_LAST 19

** CAPI3REF: SQLite Runtime Status

@@ -5967,7 +6131,7 @@ SQLITE_API int sqlite3_test_control(int op, ...);

** about the performance of SQLite, and optionally to reset various

** highwater marks. ^The first argument is an integer code for

** the specific parameter to measure. ^(Recognized integer codes

-** are of the form [SQLITE_STATUS_MEMORY_USED | SQLITE_STATUS_...].)^

+** are of the form [status parameters | SQLITE_STATUS_...].)^

** ^The current value of the parameter is returned into *pCurrent.

** ^The highest recorded value is returned in *pHighwater. ^If the

** resetFlag is true, then the highest record value is reset after

@@ -5994,12 +6158,13 @@ SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetF

** CAPI3REF: Status Parameters

+** KEYWORDS: {status parameters}

** These integer constants designate various run-time status parameters

** that can be returned by [sqlite3_status()].

** <dl>

-** ^(<dt>SQLITE_STATUS_MEMORY_USED</dt>

+** [[SQLITE_STATUS_MEMORY_USED]] ^(<dt>SQLITE_STATUS_MEMORY_USED</dt>

** <dd>This parameter is the current amount of memory checked out

** using [sqlite3_malloc()], either directly or indirectly. The

** figure includes calls made to [sqlite3_malloc()] by the application

@@ -6009,23 +6174,24 @@ SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetF

** this parameter. The amount returned is the sum of the allocation

** sizes as reported by the xSize method in [sqlite3_mem_methods].</dd>)^

-** ^(<dt>SQLITE_STATUS_MALLOC_SIZE</dt>

+** [[SQLITE_STATUS_MALLOC_SIZE]] ^(<dt>SQLITE_STATUS_MALLOC_SIZE</dt>

** <dd>This parameter records the largest memory allocation request

** handed to [sqlite3_malloc()] or [sqlite3_realloc()] (or their

** internal equivalents). Only the value returned in the

** *pHighwater parameter to [sqlite3_status()] is of interest.

** The value written into the *pCurrent parameter is undefined.</dd>)^

-** ^(<dt>SQLITE_STATUS_MALLOC_COUNT</dt>

+** [[SQLITE_STATUS_MALLOC_COUNT]] ^(<dt>SQLITE_STATUS_MALLOC_COUNT</dt>

** <dd>This parameter records the number of separate memory allocations

** currently checked out.</dd>)^

-** ^(<dt>SQLITE_STATUS_PAGECACHE_USED</dt>

+** [[SQLITE_STATUS_PAGECACHE_USED]] ^(<dt>SQLITE_STATUS_PAGECACHE_USED</dt>

** <dd>This parameter returns the number of pages used out of the

** [pagecache memory allocator] that was configured using

** [SQLITE_CONFIG_PAGECACHE]. The

** value returned is in pages, not in bytes.</dd>)^

+** [[SQLITE_STATUS_PAGECACHE_OVERFLOW]]

** ^(<dt>SQLITE_STATUS_PAGECACHE_OVERFLOW</dt>

** <dd>This parameter returns the number of bytes of page cache

** allocation which could not be satisfied by the [SQLITE_CONFIG_PAGECACHE]

@@ -6035,13 +6201,13 @@ SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetF

** [SQLITE_CONFIG_PAGECACHE]) and allocations that overflowed because

** no space was left in the page cache.</dd>)^

-** ^(<dt>SQLITE_STATUS_PAGECACHE_SIZE</dt>

+** [[SQLITE_STATUS_PAGECACHE_SIZE]] ^(<dt>SQLITE_STATUS_PAGECACHE_SIZE</dt>

** <dd>This parameter records the largest memory allocation request

** handed to [pagecache memory allocator]. Only the value returned in the

** *pHighwater parameter to [sqlite3_status()] is of interest.

** The value written into the *pCurrent parameter is undefined.</dd>)^

-** ^(<dt>SQLITE_STATUS_SCRATCH_USED</dt>

+** [[SQLITE_STATUS_SCRATCH_USED]] ^(<dt>SQLITE_STATUS_SCRATCH_USED</dt>

** <dd>This parameter returns the number of allocations used out of the

** [scratch memory allocator] configured using

** [SQLITE_CONFIG_SCRATCH]. The value returned is in allocations, not

@@ -6049,7 +6215,7 @@ SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetF

** outstanding at time, this parameter also reports the number of threads

** using scratch memory at the same time.</dd>)^

-** ^(<dt>SQLITE_STATUS_SCRATCH_OVERFLOW</dt>

+** [[SQLITE_STATUS_SCRATCH_OVERFLOW]] ^(<dt>SQLITE_STATUS_SCRATCH_OVERFLOW</dt>

** <dd>This parameter returns the number of bytes of scratch memory

** allocation which could not be satisfied by the [SQLITE_CONFIG_SCRATCH]

** buffer and where forced to overflow to [sqlite3_malloc()]. The values

@@ -6059,13 +6225,13 @@ SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetF

** slots were available.

** </dd>)^

-** ^(<dt>SQLITE_STATUS_SCRATCH_SIZE</dt>

+** [[SQLITE_STATUS_SCRATCH_SIZE]] ^(<dt>SQLITE_STATUS_SCRATCH_SIZE</dt>

** <dd>This parameter records the largest memory allocation request

** handed to [scratch memory allocator]. Only the value returned in the

** *pHighwater parameter to [sqlite3_status()] is of interest.

** The value written into the *pCurrent parameter is undefined.</dd>)^

-** ^(<dt>SQLITE_STATUS_PARSER_STACK</dt>

+** [[SQLITE_STATUS_PARSER_STACK]] ^(<dt>SQLITE_STATUS_PARSER_STACK</dt>

** <dd>This parameter records the deepest parser stack. It is only

** meaningful if SQLite is compiled with [YYTRACKMAXSTACKDEPTH].</dd>)^

** </dl>

@@ -6090,9 +6256,9 @@ SQLITE_API int sqlite3_status(int op, int *pCurrent, int *pHighwater, int resetF

** about a single [database connection]. ^The first argument is the

** database connection object to be interrogated. ^The second argument

** is an integer constant, taken from the set of

-** [SQLITE_DBSTATUS_LOOKASIDE_USED | SQLITE_DBSTATUS_*] macros, that

+** [SQLITE_DBSTATUS options], that

** determines the parameter to interrogate. The set of

-** [SQLITE_DBSTATUS_LOOKASIDE_USED | SQLITE_DBSTATUS_*] macros is likely

+** [SQLITE_DBSTATUS options] is likely

** to grow in future releases of SQLite.

** ^The current value of the requested parameter is written into *pCur

@@ -6109,6 +6275,7 @@ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int r

** CAPI3REF: Status Parameters for database connections

+** KEYWORDS: {SQLITE_DBSTATUS options}

** These constants are the available integer "verbs" that can be passed as

** the second argument to the [sqlite3_db_status()] interface.

@@ -6120,15 +6287,16 @@ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int r

** if a discontinued or unsupported verb is invoked.

** <dl>

-** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_USED</dt>

+** [[SQLITE_DBSTATUS_LOOKASIDE_USED]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_USED</dt>

** <dd>This parameter returns the number of lookaside memory slots currently

** checked out.</dd>)^

-** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_HIT</dt>

+** [[SQLITE_DBSTATUS_LOOKASIDE_HIT]] ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_HIT</dt>

** <dd>This parameter returns the number malloc attempts that were

** satisfied using lookaside memory. Only the high-water value is meaningful;

** the current value is always zero.)^

+** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE]]

** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE</dt>

** <dd>This parameter returns the number malloc attempts that might have

** been satisfied using lookaside memory but failed due to the amount of

@@ -6136,6 +6304,7 @@ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int r

** Only the high-water value is meaningful;

** the current value is always zero.)^

+** [[SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL]]

** ^(<dt>SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL</dt>

** <dd>This parameter returns the number malloc attempts that might have

** been satisfied using lookaside memory but failed due to all lookaside

@@ -6143,12 +6312,12 @@ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int r

** Only the high-water value is meaningful;

** the current value is always zero.)^

-** ^(<dt>SQLITE_DBSTATUS_CACHE_USED</dt>

+** [[SQLITE_DBSTATUS_CACHE_USED]] ^(<dt>SQLITE_DBSTATUS_CACHE_USED</dt>

** <dd>This parameter returns the approximate number of of bytes of heap

** memory used by all pager caches associated with the database connection.)^

** ^The highwater mark associated with SQLITE_DBSTATUS_CACHE_USED is always 0.

-** ^(<dt>SQLITE_DBSTATUS_SCHEMA_USED</dt>

+** [[SQLITE_DBSTATUS_SCHEMA_USED]] ^(<dt>SQLITE_DBSTATUS_SCHEMA_USED</dt>

** <dd>This parameter returns the approximate number of of bytes of heap

** memory used to store the schema for all databases associated

** with the connection - main, temp, and any [ATTACH]-ed databases.)^

@@ -6157,7 +6326,7 @@ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int r

** [shared cache mode] being enabled.

** ^The highwater mark associated with SQLITE_DBSTATUS_SCHEMA_USED is always 0.

-** ^(<dt>SQLITE_DBSTATUS_STMT_USED</dt>

+** [[SQLITE_DBSTATUS_STMT_USED]] ^(<dt>SQLITE_DBSTATUS_STMT_USED</dt>

** <dd>This parameter returns the approximate number of of bytes of heap

** and lookaside memory used by all prepared statements associated with

** the database connection.)^

@@ -6179,7 +6348,7 @@ SQLITE_API int sqlite3_db_status(sqlite3*, int op, int *pCur, int *pHiwtr, int r

** CAPI3REF: Prepared Statement Status

** ^(Each prepared statement maintains various

-** [SQLITE_STMTSTATUS_SORT | counters] that measure the number


context:
space:
mode: