|
|
@@ -109,7 +109,7 @@ extern "C" {
|
|
|
*/
|
|
|
#define SQLITE_VERSION "3.8.8"
|
|
|
#define SQLITE_VERSION_NUMBER 3008008
|
|
|
-#define SQLITE_SOURCE_ID "2015-01-01 16:47:43 30891c6b8ebe9dfc939f9695bb45a159fbaaf262"
|
|
|
+#define SQLITE_SOURCE_ID "2015-01-10 18:22:06 46f3aba2692d74c29ab5c1f24a6daac600fd6af8"
|
|
|
|
|
|
/*
|
|
|
** CAPI3REF: Run-Time Library Version Numbers
|
|
|
@@ -1762,6 +1762,17 @@ struct sqlite3_mem_methods {
|
|
|
** bytes per page required for each page in [SQLITE_CONFIG_PAGECACHE].
|
|
|
** The amount of extra space required can change depending on the compiler,
|
|
|
** target platform, and SQLite version.
|
|
|
+**
|
|
|
+** [[SQLITE_CONFIG_PMASZ]]
|
|
|
+** <dt>SQLITE_CONFIG_PMASZ
|
|
|
+** <dd>^The SQLITE_CONFIG_PMASZ option takes a single parameter which
|
|
|
+** is an unsigned integer and sets the "Minimum PMA Size" for the multithreaded
|
|
|
+** sorter to that integer. The default minimum PMA Size is set by the
|
|
|
+** [SQLITE_SORTER_PMASZ] compile-time option. New threads are launched
|
|
|
+** to help with sort operations when multithreaded sorting
|
|
|
+** is enabled (using the [PRAGMA threads] command) and the amount of content
|
|
|
+** to be sorted exceeds the page size times the minimum of the
|
|
|
+** [PRAGMA cache_size] setting and this value.
|
|
|
** </dl>
|
|
|
*/
|
|
|
#define SQLITE_CONFIG_SINGLETHREAD 1 /* nil */
|
|
|
@@ -1788,6 +1799,7 @@ struct sqlite3_mem_methods {
|
|
|
#define SQLITE_CONFIG_MMAP_SIZE 22 /* sqlite3_int64, sqlite3_int64 */
|
|
|
#define SQLITE_CONFIG_WIN32_HEAPSIZE 23 /* int nByte */
|
|
|
#define SQLITE_CONFIG_PCACHE_HDRSZ 24 /* int *psz */
|
|
|
+#define SQLITE_CONFIG_PMASZ 25 /* unsigned int szPma */
|
|
|
|
|
|
/*
|
|
|
** CAPI3REF: Database Connection Configuration Options
|
|
|
@@ -7515,6 +7527,10 @@ SQLITE_API int sqlite3_vtab_on_conflict(sqlite3 *);
|
|
|
** [sqlite3_stmt_scanstatus(S,X,T,V)] interface. Each constant designates a
|
|
|
** different metric for sqlite3_stmt_scanstatus() to return.
|
|
|
**
|
|
|
+** When the value returned to V is a string, space to hold that string is
|
|
|
+** managed by the prepared statement S and will be automatically freed when
|
|
|
+** S is finalized.
|
|
|
+**
|
|
|
** <dl>
|
|
|
** [[SQLITE_SCANSTAT_NLOOP]] <dt>SQLITE_SCANSTAT_NLOOP</dt>
|
|
|
** <dd>^The [sqlite3_int64] variable pointed to by the T parameter will be
|
|
|
@@ -7560,7 +7576,14 @@ SQLITE_API int sqlite3_vtab_on_conflict(sqlite3 *);
|
|
|
/*
|
|
|
** CAPI3REF: Prepared Statement Scan Status
|
|
|
**
|
|
|
-** Return status data for a single loop within query pStmt.
|
|
|
+** This interface returns information about the predicted and measured
|
|
|
+** performance for pStmt. Advanced applications can use this
|
|
|
+** interface to compare the predicted and the measured performance and
|
|
|
+** issue warnings and/or rerun [ANALYZE] if discrepancies are found.
|
|
|
+**
|
|
|
+** Since this interface is expected to be rarely used, it is only
|
|
|
+** available if SQLite is compiled using the [SQLITE_ENABLE_STMT_SCANSTATUS]
|
|
|
+** compile-time option.
|
|
|
**
|
|
|
** The "iScanStatusOp" parameter determines which status information to return.
|
|
|
** The "iScanStatusOp" must be one of the [scanstatus options] or the behavior
|
|
|
@@ -7578,9 +7601,6 @@ SQLITE_API int sqlite3_vtab_on_conflict(sqlite3 *);
|
|
|
** as if the loop did not exist - it returns non-zero and leave the variable
|
|
|
** that pOut points to unchanged.
|
|
|
**
|
|
|
-** This API is only available if the library is built with pre-processor
|
|
|
-** symbol [SQLITE_ENABLE_STMT_SCANSTATUS] defined.
|
|
|
-**
|
|
|
** See also: [sqlite3_stmt_scanstatus_reset()]
|
|
|
*/
|
|
|
SQLITE_API SQLITE_EXPERIMENTAL int sqlite3_stmt_scanstatus(
|