sqlite3: upgrade 3.43.1 -> 3.43.2

Changelog:
============
-Add support for Contentless-Delete FTS5 Indexes.
-Enhancements to the date and time functions:
-Added the octet_length(X) SQL function.
-Added the sqlite3_stmt_explain() API.
-Query planner enhancements:
-Enhancements to the decimal extension:
-If X is a floating-point value, then the decimal(X) function now does a full
 expansion of that value into its exact decimal equivalent.
-Performance enhancements to JSON processing results in a 2x performance
 improvement for some kinds of processing on large JSON strings.
-New makefile target "verify-source" checks to ensure that there are no
 unintentional changes in the source tree.
-Added the SQLITE_USE_SEH compile-time option that enables Structured Exception
 Handling on Windows while working with the memory-mapped shm file that is part
 of WAL mode processing. This option is enabled by default when building on
 Windows using Makefile.msc.
-The VFS for unix now assumes that the nanosleep() system call is available
 unless compiled with -DHAVE_NANOSLEEP=0.

(From OE-Core rev: e2ce12ded0672063c74fc794b0fd8828b1c0e776)

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/meta/recipes-support/sqlite/sqlite3_3.43.1.bb b/meta/recipes-support/sqlite/sqlite3_3.43.2.bb
index 93146358c7..64c1013625 100644
--- a/meta/recipes-support/sqlite/sqlite3_3.43.1.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.43.2.bb
@@ -4,7 +4,7 @@ LICENSE = "PD"
 LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=786d3dc581eff03f4fd9e4a77ed00c66"
 
 SRC_URI = "http://www.sqlite.org/2023/sqlite-autoconf-${SQLITE_PV}.tar.gz"
-SRC_URI[sha256sum] = "39116c94e76630f22d54cd82c3cea308565f1715f716d1b2527f1c9c969ba4d9"
+SRC_URI[sha256sum] = "6d422b6f62c4de2ca80d61860e3a3fb693554d2f75bb1aaca743ccc4d6f609f0"
 
 CVE_STATUS[CVE-2023-36191] = "disputed: The error is a bug. It has been fixed upstream. But it is not a vulnerability"