mirror of
				https://github.com/pocoproject/poco.git
				synced 2025-10-26 02:18:04 +01:00 
			
		
		
		
	Bump to sqlite 3.12.0
This commit is contained in:
		
										
											
												File diff suppressed because it is too large
												Load Diff
											
										
									
								
							| @@ -111,9 +111,9 @@ extern "C" { | ||||
| ** [sqlite3_libversion_number()], [sqlite3_sourceid()], | ||||
| ** [sqlite_version()] and [sqlite_source_id()]. | ||||
| */ | ||||
| #define SQLITE_VERSION        "3.11.1" | ||||
| #define SQLITE_VERSION_NUMBER 3011001 | ||||
| #define SQLITE_SOURCE_ID      "2016-03-03 16:17:53 f047920ce16971e573bc6ec9a48b118c9de2b3a7" | ||||
| #define SQLITE_VERSION        "3.12.0" | ||||
| #define SQLITE_VERSION_NUMBER 3012000 | ||||
| #define SQLITE_SOURCE_ID      "2016-03-29 10:14:15 e9bb4cf40f4971974a74468ef922bdee481c988b" | ||||
|  | ||||
| /* | ||||
| ** CAPI3REF: Run-Time Library Version Numbers | ||||
| @@ -1228,7 +1228,7 @@ struct sqlite3_vfs { | ||||
|   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 figure versions.  The iVersion | ||||
|   ** New fields may be appended in future versions.  The iVersion | ||||
|   ** value will increment whenever this happens.  | ||||
|   */ | ||||
| }; | ||||
| @@ -1820,6 +1820,20 @@ struct sqlite3_mem_methods { | ||||
| ** 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. | ||||
| ** | ||||
| ** [[SQLITE_CONFIG_STMTJRNL_SPILL]] | ||||
| ** <dt>SQLITE_CONFIG_STMTJRNL_SPILL | ||||
| ** <dd>^The SQLITE_CONFIG_STMTJRNL_SPILL option takes a single parameter which | ||||
| ** becomes the [statement journal] spill-to-disk threshold.   | ||||
| ** [Statement journals] are held in memory until their size (in bytes) | ||||
| ** exceeds this threshold, at which point they are written to disk. | ||||
| ** Or if the threshold is -1, statement journals are always held | ||||
| ** exclusively in memory. | ||||
| ** Since many statement journals never become large, setting the spill | ||||
| ** threshold to a value such as 64KiB can greatly reduce the amount of | ||||
| ** I/O required to support statement rollback. | ||||
| ** The default value for this setting is controlled by the | ||||
| ** [SQLITE_STMTJRNL_SPILL] compile-time option. | ||||
| ** </dl> | ||||
| */ | ||||
| #define SQLITE_CONFIG_SINGLETHREAD  1  /* nil */ | ||||
| @@ -1847,6 +1861,7 @@ struct sqlite3_mem_methods { | ||||
| #define SQLITE_CONFIG_WIN32_HEAPSIZE      23  /* int nByte */ | ||||
| #define SQLITE_CONFIG_PCACHE_HDRSZ        24  /* int *psz */ | ||||
| #define SQLITE_CONFIG_PMASZ               25  /* unsigned int szPma */ | ||||
| #define SQLITE_CONFIG_STMTJRNL_SPILL      26  /* int nByte */ | ||||
|  | ||||
| /* | ||||
| ** CAPI3REF: Database Connection Configuration Options | ||||
| @@ -1904,11 +1919,25 @@ struct sqlite3_mem_methods { | ||||
| ** following this call.  The second parameter may be a NULL pointer, in | ||||
| ** which case the trigger setting is not reported back. </dd> | ||||
| ** | ||||
| ** <dt>SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER</dt> | ||||
| ** <dd> ^This option is used to enable or disable the two-argument | ||||
| ** version of the [fts3_tokenizer()] function which is part of the | ||||
| ** [FTS3] full-text search engine extension. | ||||
| ** There should be two additional arguments. | ||||
| ** The first argument is an integer which is 0 to disable fts3_tokenizer() or | ||||
| ** positive to enable fts3_tokenizer() or negative to leave the setting | ||||
| ** unchanged. | ||||
| ** The second parameter is a pointer to an integer into which | ||||
| ** is written 0 or 1 to indicate whether fts3_tokenizer is disabled or enabled | ||||
| ** following this call.  The second parameter may be a NULL pointer, in | ||||
| ** which case the new setting is not reported back. </dd> | ||||
| ** | ||||
| ** </dl> | ||||
| */ | ||||
| #define SQLITE_DBCONFIG_LOOKASIDE       1001  /* void* int int */ | ||||
| #define SQLITE_DBCONFIG_ENABLE_FKEY     1002  /* int int* */ | ||||
| #define SQLITE_DBCONFIG_ENABLE_TRIGGER  1003  /* int int* */ | ||||
| #define SQLITE_DBCONFIG_LOOKASIDE             1001 /* void* int int */ | ||||
| #define SQLITE_DBCONFIG_ENABLE_FKEY           1002 /* int int* */ | ||||
| #define SQLITE_DBCONFIG_ENABLE_TRIGGER        1003 /* int int* */ | ||||
| #define SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER 1004 /* int int* */ | ||||
|  | ||||
|  | ||||
| /* | ||||
| @@ -7489,7 +7518,7 @@ SQLITE_API void SQLITE_CDECL sqlite3_log(int iErrCode, const char *zFormat, ...) | ||||
| ** previously registered write-ahead log callback. ^Note that the | ||||
| ** [sqlite3_wal_autocheckpoint()] interface and the | ||||
| ** [wal_autocheckpoint pragma] both invoke [sqlite3_wal_hook()] and will | ||||
| ** those overwrite any prior [sqlite3_wal_hook()] settings. | ||||
| ** overwrite any prior [sqlite3_wal_hook()] settings. | ||||
| */ | ||||
| SQLITE_API void *SQLITE_STDCALL sqlite3_wal_hook( | ||||
|   sqlite3*,  | ||||
| @@ -7886,6 +7915,18 @@ SQLITE_API void SQLITE_STDCALL sqlite3_stmt_scanstatus_reset(sqlite3_stmt*); | ||||
| */ | ||||
| SQLITE_API int SQLITE_STDCALL sqlite3_db_cacheflush(sqlite3*); | ||||
|  | ||||
| /* | ||||
| ** CAPI3REF: Low-level system error code | ||||
| ** | ||||
| ** ^Attempt to return the underlying operating system error code or error | ||||
| ** number that caused the most reason I/O error or failure to open a file. | ||||
| ** The return value is OS-dependent.  For example, on unix systems, after | ||||
| ** [sqlite3_open_v2()] returns [SQLITE_CANTOPEN], this interface could be | ||||
| ** called to get back the underlying "errno" that caused the problem, such | ||||
| ** as ENOSPC, EAUTH, EISDIR, and so forth.   | ||||
| */ | ||||
| SQLITE_API int SQLITE_STDCALL sqlite3_system_errno(sqlite3*); | ||||
|  | ||||
| /* | ||||
| ** CAPI3REF: Database Snapshot | ||||
| ** KEYWORDS: {snapshot} | ||||
| @@ -7954,7 +7995,11 @@ SQLITE_API SQLITE_EXPERIMENTAL int SQLITE_STDCALL sqlite3_snapshot_get( | ||||
| ** the first operation, apart from other sqlite3_snapshot_open() calls, | ||||
| ** following the [BEGIN] that starts a new read transaction. | ||||
| ** ^A [snapshot] will fail to open if it has been overwritten by a  | ||||
| ** [checkpoint].   | ||||
| ** [checkpoint]. | ||||
| ** ^A [snapshot] will fail to open if the database connection D has not | ||||
| ** previously completed at least one read operation against the database  | ||||
| ** file.  (Hint: Run "[PRAGMA application_id]" against a newly opened | ||||
| ** database connection in order to make it ready to use snapshots.) | ||||
| ** | ||||
| ** The [sqlite3_snapshot_open()] interface is only available when the | ||||
| ** SQLITE_ENABLE_SNAPSHOT compile-time option is used. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user
	 mkrivos
					mkrivos