From de1caa20c41f730e54fb6974ba7821fe48816e40 Mon Sep 17 00:00:00 2001
From: Daniel Baumann
SQLite keeps track of the largest ROWID
using an internal table named "sqlite_sequence".
-The sqlite_sequence table is created
-and initialized automatically whenever a normal table that contains an
-AUTOINCREMENT column is created. The content of the sqlite_sequence table
+The sqlite_sequence table is created automatically, if it does not
+already exist, whenever a normal table that contains an
+AUTOINCREMENT column is created. A row in the sqlite_sequence table
+corresponding to the table with the AUTOINCREMENT column is created the
+first time the AUTOINCREMENT table is written and updated on any
+subsequent writes that increase the maximum rowid.
+The content of the sqlite_sequence table
can be modified using ordinary UPDATE, INSERT, and DELETE statements.
But making modifications to this table will likely perturb the AUTOINCREMENT
key generation algorithm. Make sure you know what you are doing before
@@ -266,5 +270,5 @@ algorithm, AUTOINCREMENT is not allowed on WITHOUT R
table column other than INTEGER PRIMARY KEY. Any attempt to use
AUTOINCREMENT on a WITHOUT ROWID table or on a column other than the
INTEGER PRIMARY KEY column results in an error. This page last modified on 2022-01-08 05:02:57 UTC This page last modified on 2024-02-22 16:13:38 UTC
The SQLITE_VERSION C preprocessor macro in the sqlite3.h header
diff --git a/www/c3ref/exec.html b/www/c3ref/exec.html
index f892dab..98edb23 100644
--- a/www/c3ref/exec.html
+++ b/www/c3ref/exec.html
@@ -186,6 +186,8 @@ is a valid and open database connection.
the 1st parameter to sqlite3_exec() while sqlite3_exec() is running.
Compile-Time Library Version Numbers
-#define SQLITE_VERSION "3.45.1"
-#define SQLITE_VERSION_NUMBER 3045001
-#define SQLITE_SOURCE_ID "2024-01-30 16:01:20 e876e51a0ed5c5b3126f52e532044363a014bc594cfefa87ffb5b82257cc467a"
+#define SQLITE_VERSION "3.45.2"
+#define SQLITE_VERSION_NUMBER 3045002
+#define SQLITE_SOURCE_ID "2024-03-12 11:06:23 d8cd6d49b46a395b13955387d05e9e1a2a47e54fb99f3c9b59835bbefad6af77"
See also lists of Objects, diff --git a/www/capi3ref.html b/www/capi3ref.html index a7fce31..86e5ad8 100644 --- a/www/capi3ref.html +++ b/www/capi3ref.html @@ -2937,6 +2937,8 @@ is a valid and open database connection. the 1st parameter to sqlite3_exec() while sqlite3_exec() is running.
-#define SQLITE_VERSION "3.45.1" -#define SQLITE_VERSION_NUMBER 3045001 -#define SQLITE_SOURCE_ID "2024-01-30 16:01:20 e876e51a0ed5c5b3126f52e532044363a014bc594cfefa87ffb5b82257cc467a" +#define SQLITE_VERSION "3.45.2" +#define SQLITE_VERSION_NUMBER 3045002 +#define SQLITE_SOURCE_ID "2024-03-12 11:06:23 d8cd6d49b46a395b13955387d05e9e1a2a47e54fb99f3c9b59835bbefad6af77"
The SQLITE_VERSION C preprocessor macro in the sqlite3.h header diff --git a/www/changes.html b/www/changes.html index b7f5e21..8812a6c 100644 --- a/www/changes.html +++ b/www/changes.html @@ -129,6 +129,25 @@ https://www.sqlite.org/src/timeline?t=release. See the chronology a succinct listing of releases.
+ +Hashes: +
-346 releases -over 23.5 years. +347 releases +over 23.6 years.
This page last modified on 2023-03-03 01:19:02 UTC
diff --git a/www/compile.html b/www/compile.html index 5e300e2..b9acc84 100644 --- a/www/compile.html +++ b/www/compile.html @@ -278,7 +278,7 @@ If SQLite is compiled with -DSQLITE_OMIT_AUTOINIT and a routine like without first calling sqlite3_initialize(), the likely result will be a segfault. -SQLITE_STRICT_SUBTYPE=1. This option causes an error to be raised if an application defined function that does not have the SQLITE_RESULT_SUBTYPE property invokes the sqlite3_result_subtype() interface. The sqlite3_result_subtype() @@ -286,7 +286,7 @@ interface does not work reliably unless the function is registered with the SQLITE_RESULT_SUBTYPE property. This compile-time option is designed to bring this problem to the attention of developers early. -
When all of the recommended compile-time options above are used, the SQLite library will be approximately 3% smaller and use about 5% fewer @@ -2129,5 +2129,5 @@ macros is included for completeness.
This macro may not be used in combination with any of SQLITE_APICALL, SQLITE_CALLBACK, SQLITE_CDECL or SQLITE_SYSAPI. -This page last modified on 2024-01-09 20:59:08 UTC
+This page last modified on 2024-02-01 18:38:39 UTC
diff --git a/www/cves.html b/www/cves.html index 7d1714b..75b22da 100644 --- a/www/cves.html +++ b/www/cves.html @@ -443,7 +443,7 @@ be added.This page last modified on 2024-01-16 16:06:37 UTC
+ diff --git a/www/doc_backlink_crossref.html b/www/doc_backlink_crossref.html index ab6e15c..cbf7cd1 100644 --- a/www/doc_backlink_crossref.html +++ b/www/doc_backlink_crossref.html @@ -208,6 +208,7 @@ antiRobotDefense();This page last modified on 2023-03-31 19:57:15 UTC
+This page last modified on 2023-03-31 19:57:15 UTC
diff --git a/www/doc_target_crossref.html b/www/doc_target_crossref.html index fc35282..59c9844 100644 --- a/www/doc_target_crossref.html +++ b/www/doc_target_crossref.html @@ -1551,6 +1551,7 @@ antiRobotDefense();This page last modified on 2024-01-23 13:42:58 UTC
+ diff --git a/www/json1.html b/www/json1.html index a3f10da..7e15bc0 100644 --- a/www/json1.html +++ b/www/json1.html @@ -395,7 +395,7 @@ internal "parse tree" representation of JSON to be stored on disk, as a BLOB, in a format that we call "JSONB". By storing SQLite's internal binary representation of JSON directly in the database, applications can bypass the overhead of parsing and rendering JSON when reading and -updating JSON values. The internal JSONB format is also uses slightly +updating JSON values. The internal JSONB format also uses slightly less disk space then text JSON.@@ -653,7 +653,7 @@ for infinity and not-a-number.
Most JSON functions do their internal processing using JSONB. So if the -input is text, they first most translate the input text into JSONB. +input is text, they first must translate the input text into JSONB. If the input is already in the JSONB format, no translation is needed, that step can be skipped, and performance is faster. @@ -698,7 +698,7 @@ text JSON when cast to text, then it is accepted as text JSON. This is actually a long-standing bug in the original implementation that the SQLite developers were unaware of. The documentation stated that a BLOB input to a JSON function should raise an error. But in the -actually implementation, the input would be accepted as long +actual implementation, the input would be accepted as long as the BLOB content was a valid JSON string in the text encoding of the database. @@ -1616,5 +1616,5 @@ SELECT DISTINCT json_extract(big.json,'$.id') WHERE json_tree.key='uuid' AND json_tree.value='6fa5181e-5721-11e5-a04e-57f3d7b32808'; - +
This page last modified on 2024-03-06 20:59:22 UTC
diff --git a/www/keyword_index.html b/www/keyword_index.html index a32498e..3a93e33 100644 --- a/www/keyword_index.html +++ b/www/keyword_index.html @@ -3030,6 +3030,7 @@ Other Documentation Indexes:The content in the sqlite_stat4 table cannot be computed with anything less than a full scan. Hence, if a non-zero analysis limit is specified, the sqlite_stat4 table is not computed. -
This page last modified on 2024-01-09 20:59:08 UTC
+This page last modified on 2024-02-21 13:43:47 UTC
diff --git a/www/lang_createtable.html b/www/lang_createtable.html index 74f1589..e0af7b8 100644 --- a/www/lang_createtable.html +++ b/www/lang_createtable.html @@ -163,8 +163,8 @@ mk.innerHTML = "►";