|
|
@@ -109,7 +109,7 @@ extern "C" {
|
|
|
*/
|
|
|
#define SQLITE_VERSION "3.7.17"
|
|
|
#define SQLITE_VERSION_NUMBER 3007017
|
|
|
-#define SQLITE_SOURCE_ID "2013-04-19 12:32:52 514adbbd8cf3e296f55e8f803bddaac8ad8b2c96"
|
|
|
+#define SQLITE_SOURCE_ID "2013-05-03 20:08:16 9314b08099e7ac99a507a4799f2c6cdd6d597abb"
|
|
|
|
|
|
/*
|
|
|
** CAPI3REF: Run-Time Library Version Numbers
|
|
|
@@ -1604,7 +1604,9 @@ struct sqlite3_mem_methods {
|
|
|
** page cache implementation into that object.)^ </dd>
|
|
|
**
|
|
|
** [[SQLITE_CONFIG_LOG]] <dt>SQLITE_CONFIG_LOG</dt>
|
|
|
-** <dd> ^The SQLITE_CONFIG_LOG option takes two arguments: a pointer to a
|
|
|
+** <dd> The SQLITE_CONFIG_LOG option is used to configure the SQLite
|
|
|
+** global [error log].
|
|
|
+** (^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
|
|
|
** invoked by [sqlite3_log()] to process each logging event. ^If the
|
|
|
@@ -1650,12 +1652,12 @@ struct sqlite3_mem_methods {
|
|
|
** <dt>SQLITE_CONFIG_PCACHE and SQLITE_CONFIG_GETPCACHE
|
|
|
** <dd> These options are obsolete and should not be used by new code.
|
|
|
** They are retained for backwards compatibility but are now no-ops.
|
|
|
-** </dl>
|
|
|
+** </dd>
|
|
|
**
|
|
|
** [[SQLITE_CONFIG_SQLLOG]]
|
|
|
** <dt>SQLITE_CONFIG_SQLLOG
|
|
|
** <dd>This option is only available if sqlite is compiled with the
|
|
|
-** SQLITE_ENABLE_SQLLOG pre-processor macro defined. The first argument should
|
|
|
+** [SQLITE_ENABLE_SQLLOG] pre-processor macro defined. The first argument should
|
|
|
** be a pointer to a function of type void(*)(void*,sqlite3*,const char*, int).
|
|
|
** The second should be of type (void*). The callback is invoked by the library
|
|
|
** in three separate circumstances, identified by the value passed as the
|
|
|
@@ -1665,7 +1667,9 @@ struct sqlite3_mem_methods {
|
|
|
** fourth parameter is 1, then the SQL statement that the third parameter
|
|
|
** points to has just been executed. Or, if the fourth parameter is 2, then
|
|
|
** the connection being passed as the second parameter is being closed. The
|
|
|
-** third parameter is passed NULL In this case.
|
|
|
+** third parameter is passed NULL In this case. An example of using this
|
|
|
+** configuration option can be seen in the "test_sqllog.c" source file in
|
|
|
+** the canonical SQLite source tree.</dd>
|
|
|
**
|
|
|
** [[SQLITE_CONFIG_MMAP_SIZE]]
|
|
|
** <dt>SQLITE_CONFIG_MMAP_SIZE
|
|
|
@@ -2553,6 +2557,9 @@ SQLITE_API int sqlite3_set_authorizer(
|
|
|
** as each triggered subprogram is entered. The callbacks for triggers
|
|
|
** contain a UTF-8 SQL comment that identifies the trigger.)^
|
|
|
**
|
|
|
+** The [SQLITE_TRACE_SIZE_LIMIT] compile-time option can be used to limit
|
|
|
+** the length of [bound parameter] expansion in the output of sqlite3_trace().
|
|
|
+**
|
|
|
** ^The callback function registered by sqlite3_profile() is invoked
|
|
|
** as each SQL statement finishes. ^The profile callback contains
|
|
|
** the original statement text and an estimate of wall-clock time
|
|
|
@@ -3094,7 +3101,8 @@ SQLITE_API int sqlite3_limit(sqlite3*, int id, int newVal);
|
|
|
** <li>
|
|
|
** ^If the database schema changes, instead of returning [SQLITE_SCHEMA] as it
|
|
|
** always used to do, [sqlite3_step()] will automatically recompile the SQL
|
|
|
-** statement and try to run it again.
|
|
|
+** statement and try to run it again. As many as [SQLITE_MAX_SCHEMA_RETRY]
|
|
|
+** retries will occur before sqlite3_step() gives up and returns an error.
|
|
|
** </li>
|
|
|
**
|
|
|
** <li>
|
|
|
@@ -3298,6 +3306,9 @@ typedef struct sqlite3_context sqlite3_context;
|
|
|
** parameter [SQLITE_LIMIT_VARIABLE_NUMBER] (default value: 999).
|
|
|
**
|
|
|
** ^The third argument is the value to bind to the parameter.
|
|
|
+** ^If the third parameter to sqlite3_bind_text() or sqlite3_bind_text16()
|
|
|
+** or sqlite3_bind_blob() is a NULL pointer then the fourth parameter
|
|
|
+** is ignored and the end result is the same as sqlite3_bind_null().
|
|
|
**
|
|
|
** ^(In those routines that have a fourth argument, its value is the
|
|
|
** number of bytes in the parameter. To be clear: the value is the
|
|
|
@@ -6911,7 +6922,7 @@ SQLITE_API int sqlite3_strglob(const char *zGlob, const char *zStr);
|
|
|
/*
|
|
|
** CAPI3REF: Error Logging Interface
|
|
|
**
|
|
|
-** ^The [sqlite3_log()] interface writes a message into the error log
|
|
|
+** ^The [sqlite3_log()] interface writes a message into the [error log]
|
|
|
** established by the [SQLITE_CONFIG_LOG] option to [sqlite3_config()].
|
|
|
** ^If logging is enabled, the zFormat string and subsequent arguments are
|
|
|
** used with [sqlite3_snprintf()] to generate the final output string.
|
mingodad