Adding upstream version 3.45.3.upstream/3.45.3

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 23 insertions, 4 deletions

diff --git a/www/capi3ref.html b/www/capi3ref.html
index 86e5ad8..43cecdb 100644
--- a/www/capi3ref.html
+++ b/www/capi3ref.html
@@ -264,6 +264,7 @@ be removed in some future release.</li>
 <li><a href='#sqliteconfigpcache2'>SQLITE_CONFIG_PCACHE2</a></li>
 <li><a href='#sqliteconfigpcachehdrsz'>SQLITE_CONFIG_PCACHE_HDRSZ</a></li>
 <li><a href='#sqliteconfigpmasz'>SQLITE_CONFIG_PMASZ</a></li>
+<li><a href='#sqliteconfigrowidinview'>SQLITE_CONFIG_ROWID_IN_VIEW</a></li>
 <li><a href='#sqliteconfigscratch'>SQLITE_CONFIG_SCRATCH</a></li>
 <li><a href='#sqliteconfigserialized'>SQLITE_CONFIG_SERIALIZED</a></li>
 <li><a href='#sqliteconfigsinglethread'>SQLITE_CONFIG_SINGLETHREAD</a></li>
@@ -5168,6 +5169,7 @@ meaning of each of these checkpoint modes.
 #define SQLITE_CONFIG_SMALL_MALLOC        27  /* boolean */
 #define SQLITE_CONFIG_SORTERREF_SIZE      28  /* int nByte */
 #define SQLITE_CONFIG_MEMDB_MAXSIZE       29  /* sqlite3_int64 */
+#define SQLITE_CONFIG_ROWID_IN_VIEW       30  /* int* */
 </pre></blockquote>
 <p>
 These constants are the available integer configuration options that
@@ -5561,7 +5563,24 @@ size can be adjusted up or down for individual databases using the
 <a href="#sqlitefcntlsizelimit">SQLITE_FCNTL_SIZE_LIMIT</a> <a href="#sqlite3_file_control">file-control</a>.  If this
 configuration setting is never used, then the default maximum is determined
 by the <a href="compile.html#memdb_default_maxsize">SQLITE_MEMDB_DEFAULT_MAXSIZE</a> compile-time option.  If that
-compile-time option is not set, then the default maximum is 1073741824.
+compile-time option is not set, then the default maximum is 1073741824.</p>
+
+<p><a name="sqliteconfigrowidinview"></a>
+
+<dt>SQLITE_CONFIG_ROWID_IN_VIEW
+<dd>The SQLITE_CONFIG_ROWID_IN_VIEW option enables or disables the ability
+for VIEWs to have a ROWID.  The capability can only be enabled if SQLite is
+compiled with -DSQLITE_ALLOW_ROWID_IN_VIEW, in which case the capability
+defaults to on.  This configuration option queries the current setting or
+changes the setting to off or on.  The argument is a pointer to an integer.
+If that integer initially holds a value of 1, then the ability for VIEWs to
+have ROWIDs is activated.  If the integer initially holds zero, then the
+ability is deactivated.  Any other initial value for the integer leaves the
+setting unchanged.  After changes, if any, the integer is written with
+a 1 or 0, if the ability for VIEWs to have ROWIDs is on or off.  If SQLite
+is compiled without -DSQLITE_ALLOW_ROWID_IN_VIEW (which is the usual and
+recommended case) then the integer is always filled with zero, regardless
+if its initial value.
 </dl>
 </p><hr><a name="SQLITE_DBCONFIG_DEFENSIVE"></a>
 <h2>Database Connection Configuration Options</h2>
@@ -6865,9 +6884,9 @@ and EXCLUSIVE.
 <h2>Compile-Time Library Version Numbers</h2>
 </div>
 <blockquote><pre>
-#define SQLITE_VERSION        "3.45.2"
-#define SQLITE_VERSION_NUMBER 3045002
-#define SQLITE_SOURCE_ID      "2024-03-12 11:06:23 d8cd6d49b46a395b13955387d05e9e1a2a47e54fb99f3c9b59835bbefad6af77"
+#define SQLITE_VERSION        "3.45.3"
+#define SQLITE_VERSION_NUMBER 3045003
+#define SQLITE_SOURCE_ID      "2024-04-15 13:34:05 8653b758870e6ef0c98d46b3ace27849054af85da891eb121e9aaa537f1e8355"
 </pre></blockquote>
 <p>
 The <a href="#SQLITE_SOURCE_ID">SQLITE_VERSION</a> C preprocessor macro in the sqlite3.h header