A failed attempt to add a new sqlite3_result_zeroterminated() interface that

is a hint to SQLite that a TEXT result does have a zero terminator. The idea is to avoid unnecessary copying of TEXT values. This seems like an unnecessary complication at the moment, but maybe I'll return to this later. Note that this check-in does not work - it is a proof of concept only. FossilOrigin-Name: a0de01108c4b462f8e79bc58fbfe40dec562bbec682679fd0479c79a3c415578
2023-07-28 12:59:10 +00:00
200 changed files with 1826 additions and 24251 deletions
@@ -57,7 +57,6 @@ LIBTCL = @TCL_LIB_SPEC@
 #
 READLINE_FLAGS = -DHAVE_READLINE=@TARGET_HAVE_READLINE@ @TARGET_READLINE_INC@
 READLINE_FLAGS += -DHAVE_EDITLINE=@TARGET_HAVE_EDITLINE@
-READLINE_FLAGS += -DHAVE_LINENOISE=@TARGET_HAVE_LINENOISE@

 # The library that programs using readline() must link against.
 #
@@ -1292,17 +1291,11 @@ fulltestonly:	$(TESTPROGS) fuzztest
 	./testfixture$(TEXE) $(TOP)/test/full.test

 # Fuzz testing
-#
-# WARNING: When the "fuzztest" target is run by the testrunner.tcl script,
-# it does not actually run this code. Instead, it schedules equivalent 
-# commands. Therefore, if this target is updated, then code in
-# testrunner_data.tcl (search for "trd_fuzztest_data") must also be updated.
-#
-fuzztest:	fuzzcheck$(TEXE) $(FUZZDATA) sessionfuzz$(TEXE)
+fuzztest:	fuzzcheck$(TEXE) $(FUZZDATA) sessionfuzz$(TEXE) $(TOP)/test/sessionfuzz-data1.db
 	./fuzzcheck$(TEXE) $(FUZZDATA)
 	./sessionfuzz$(TEXE) run $(TOP)/test/sessionfuzz-data1.db

-valgrindfuzz:	fuzzcheck$(TEXT) $(FUZZDATA) sessionfuzz$(TEXE)
+valgrindfuzz:	fuzzcheck$(TEXT) $(FUZZDATA) sessionfuzz$(TEXE) $(TOP)/test/sessionfuzz-data1.db
 	valgrind ./fuzzcheck$(TEXE) --cell-size-check --limit-mem 10M $(FUZZDATA)
 	valgrind ./sessionfuzz$(TEXE) run $(TOP)/test/sessionfuzz-data1.db

@@ -1321,12 +1314,6 @@ testrunner:	testfixture$(TEXE)
 #
 devtest:	testfixture$(TEXE) fuzztest testrunner

-mdevtest:
-	$(TCLSH_CMD) $(TOP)/test/testrunner.tcl mdevtest
-
-sdevtest:
-	$(TCLSH_CMD) $(TOP)/test/testrunner.tcl sdevtest
-
 # Testing for a release
 #
 releasetest: testfixture$(TEXE)
@@ -1469,11 +1456,6 @@ amalgamation-tarball: sqlite3.c sqlite3rc.h
 snapshot-tarball: sqlite3.c sqlite3rc.h
 	TOP=$(TOP) sh $(TOP)/tool/mkautoconfamal.sh --snapshot

-# Build a ZIP archive containing various command-line tools.
-#
-tool-zip:	testfixture sqlite3 sqldiff sqlite3_analyzer tool/mktoolzip.tcl
-	./testfixture $(TOP)/tool/mktoolzip.tcl
-
 # The next two rules are used to support the "threadtest" target. Building
 # threadtest runs a few thread-safety tests that are implemented in C. This
 # target is invoked by the releasetest.tcl script.
@@ -1531,7 +1513,6 @@ clean:
 	rm -f LogEst$(TEXE) fts3view$(TEXE) rollback-test$(TEXE) showdb$(TEXE)
 	rm -f showjournal$(TEXE) showstat4$(TEXE) showwal$(TEXE) speedtest1$(TEXE)
 	rm -f wordcount$(TEXE) changeset$(TEXE)
-	rm -f version-info$(TEXT)
 	rm -f sqlite3.dll sqlite3.lib sqlite3.exp sqlite3.def
 	rm -f sqlite3.c
 	rm -f sqlite3rc.h
@@ -1595,10 +1576,3 @@ fiddle: sqlite3.c shell.c

 misspell: ./custom.rws
 	$(TCLSH_CMD) ./tool/spellsift.tcl ./src/*.c ./src/*.h ./src/*.in
-
-#
-# tool/version-info: a utility for emitting sqlite3 version info
-# in various forms.
-#
-version-info$(TEXE):	$(TOP)/tool/version-info.c Makefile sqlite3.h
-	$(LTLINK) $(ST_OPT) -o $@ $(TOP)/tool/version-info.c
@@ -22,6 +22,12 @@ TOP = ../sqlite
 BCC = gcc -g -O0
 #BCC = /opt/ancic/bin/c89 -0

+#### If the target operating system supports the "usleep()" system
+#    call, then define the HAVE_USLEEP macro for all C modules.
+#
+#USLEEP = 
+USLEEP = -DHAVE_USLEEP=1
+
 #### If you want the SQLite library to be safe for use within a 
 #    multi-threaded program, then define the following macro
 #    appropriately:
@@ -52,13 +52,6 @@ MINIMAL_AMALGAMATION = 0
 USE_STDCALL = 0
 !ENDIF

-# Set this non-0 to use structured exception handling (SEH) for WAL mode
-# in the core library.
-#
-!IFNDEF USE_SEH
-USE_SEH = 1
-!ENDIF
-
 # Set this non-0 to have the shell executable link against the core dynamic
 # link library.
 #
@@ -225,12 +218,6 @@ WIN32HEAP = 0
 OSTRACE = 0
 !ENDIF

-# enable address sanitizer using ASAN=1 on the command-line.
-#
-!IFNDEF ASAN
-ASAN = 0
-!ENDIF
-
 # Set this to one of the following values to enable various debugging
 # features.  Each level includes the debugging options from the previous
 # levels.  Currently, the recognized values for DEBUG are:
@@ -402,13 +389,6 @@ OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_ENABLE_MATH_FUNCTIONS
 OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_ENABLE_RBU=1
 !ENDIF

-# Should structured exception handling (SEH) be enabled for WAL mode in
-# the core library?
-#
-!IF $(USE_SEH)!=0
-OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_USE_SEH=1
-!ENDIF
-
 # These are the "extended" SQLite compilation options used when compiling for
 # the Windows 10 platform.
 #
@@ -897,13 +877,6 @@ RCC = $(RCC) -DSQLITE_WIN32_MALLOC_VALIDATE=1
 !ENDIF
 !ENDIF

-
-# Address sanitizer if ASAN=1
-#
-!IF $(ASAN)>0
-TCC = $(TCC) /fsanitize=address
-!ENDIF
-
 # <<mark>>
 # The locations of the Tcl header and library files.  Also, the library that
 # non-stubs enabled programs using Tcl must link against.  These variables
@@ -2466,9 +2439,6 @@ extensiontest:	testfixture.exe testloadext.dll
 	@set PATH=$(LIBTCLPATH);$(PATH)
 	.\testfixture.exe $(TOP)\test\loadext.test $(TESTOPTS)

-tool-zip:	testfixture.exe sqlite3.exe sqldiff.exe sqlite3_analyzer.exe tool\mktoolzip.tcl
-	.\testfixture.exe $(TOP)\tool\mktoolzip.tcl
-
 coretestprogs:	$(TESTPROGS)

 testprogs:	coretestprogs srcck1.exe fuzzcheck.exe sessionfuzz.exe
@@ -2521,9 +2491,6 @@ testrunner:	testfixture.exe
 #
 devtest:	testfixture.exe fuzztest testrunner

-mdevtest:
-	$(TCLSH_CMD) $(TOP)\test\testrunner.tcl mdevtest
-
 # Testing for a release
 #
 releasetest: testfixture.exe fuzztest
@@ -41,10 +41,11 @@ email to drh at sqlite dot org.
 The SQLite source code is in the public domain.  See
 <https://sqlite.org/copyright.html> for details. 

-Because SQLite is in the public domain, we do not normally accept pull
-requests, because if we did take a pull request, the changes in that
-pull request might carry a copyright and the SQLite source code would
-then no longer be fully in the public domain.
+Because SQLite is in the public domain,
+we cannot accept pull requests, because
+if we did accept a pull request, the changes in that pull request would
+carry a copyright and the SQLite source code would no longer be fully in
+the public domain.

 ## Obtaining The SQLite Source Code

@@ -103,9 +104,9 @@ For example:
        mkdir bld                ;#  Build will occur in a sibling directory
        cd bld                   ;#  Change to the build directory
        ../sqlite/configure      ;#  Run the configure script
-        make                     ;#  Builds the "sqlite3" command-line tool
+        make                     ;#  Run the makefile.
        make sqlite3.c           ;#  Build the "amalgamation" source file
-        make devtest             ;#  Run some tests (requires Tcl)
+        make test                ;#  Run some tests (requires Tcl)

 See the makefile for additional targets.

@@ -115,33 +116,32 @@ script does not work out for you, there is a generic makefile named
 can copy and edit to suit your needs.  Comments on the generic makefile
 show what changes are needed.

-## Compiling for Windows Using MSVC
+## Using MSVC for Windows systems

 On Windows, all applicable build products can be compiled with MSVC.
-You will also need a working installation of TCL.
-See the [compile-for-windows.md](doc/compile-for-windows.md) document for
-additional information about how to install MSVC and TCL and configure your
-build environment.
+First open the command prompt window associated with the desired compiler
+version (e.g. "Developer Command Prompt for VS2013").  Next, use NMAKE
+with the provided "Makefile.msc" to build one of the supported targets.

-If you want to run tests, you need to let SQLite know the location of your
-TCL library, using a command like this:
+For example, from the parent directory of the source subtree named "sqlite":

-        set TCLDIR=c:\Tcl
+        mkdir bld
+        cd bld
+        nmake /f ..\sqlite\Makefile.msc TOP=..\sqlite
+        nmake /f ..\sqlite\Makefile.msc sqlite3.c TOP=..\sqlite
+        nmake /f ..\sqlite\Makefile.msc sqlite3.dll TOP=..\sqlite
+        nmake /f ..\sqlite\Makefile.msc sqlite3.exe TOP=..\sqlite
+        nmake /f ..\sqlite\Makefile.msc test TOP=..\sqlite

-SQLite uses "tclsh.exe" as part of the build process, and so that utility
-program will need to be somewhere on your %PATH%.  The finished SQLite library
-does not contain any TCL code, but it does use TCL to help with the build process
-and to run tests.
+There are several build options that can be set via the NMAKE command
+line.  For example, to build for WinRT, simply add "FOR_WINRT=1" argument
+to the "sqlite3.dll" command line above.  When debugging into the SQLite
+code, adding the "DEBUG=1" argument to one of the above command lines is
+recommended.

-Build using Makefile.msc.  Example:
-
-        nmake /f Makefile.msc
-        nmake /f Makefile.msc sqlite3.c
-        nmake /f Makefile.msc devtest
-        nmake /f Makefile.msc releasetest
- 
-There are many other makefile targets.  See comments in Makefile.msc for
-details.
+SQLite does not require [Tcl](http://www.tcl.tk/) to run, but a Tcl installation
+is required by the makefiles (including those for MSVC).  SQLite contains
+a lot of generated code and Tcl is used to do much of that code generation.

 ## Source Code Tour

@@ -1 +1 @@
-3.44.0
+3.43.0
@@ -9,7 +9,7 @@ sqlite3_SOURCES = shell.c sqlite3.h
 EXTRA_sqlite3_SOURCES = sqlite3.c
 sqlite3_LDADD = @EXTRA_SHELL_OBJ@ @READLINE_LIBS@
 sqlite3_DEPENDENCIES = @EXTRA_SHELL_OBJ@
-sqlite3_CFLAGS = $(AM_CFLAGS) -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_DQS=0 -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBSTAT_VTAB $(SHELL_CFLAGS)
+sqlite3_CFLAGS = $(AM_CFLAGS) -DSQLITE_ENABLE_EXPLAIN_COMMENTS -DSQLITE_ENABLE_DBPAGE_VTAB -DSQLITE_ENABLE_STMTVTAB -DSQLITE_ENABLE_DBSTAT_VTAB $(SHELL_CFLAGS)

 include_HEADERS = sqlite3.h sqlite3ext.h

@@ -52,13 +52,6 @@ MINIMAL_AMALGAMATION = 0
 USE_STDCALL = 0
 !ENDIF

-# Set this non-0 to use structured exception handling (SEH) for WAL mode
-# in the core library.
-#
-!IFNDEF USE_SEH
-USE_SEH = 1
-!ENDIF
-
 # Set this non-0 to have the shell executable link against the core dynamic
 # link library.
 #
@@ -187,12 +180,6 @@ WIN32HEAP = 0
 OSTRACE = 0
 !ENDIF

-# enable address sanitizer using ASAN=1 on the command-line.
-#
-!IFNDEF ASAN
-ASAN = 0
-!ENDIF
-
 # Set this to one of the following values to enable various debugging
 # features.  Each level includes the debugging options from the previous
 # levels.  Currently, the recognized values for DEBUG are:
@@ -324,13 +311,6 @@ OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_ENABLE_MATH_FUNCTIONS
 OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_ENABLE_RBU=1
 !ENDIF

-# Should structured exception handling (SEH) be enabled for WAL mode in
-# the core library?
-#
-!IF $(USE_SEH)!=0
-OPT_FEATURE_FLAGS = $(OPT_FEATURE_FLAGS) -DSQLITE_USE_SEH=1
-!ENDIF
-
 # These are the "extended" SQLite compilation options used when compiling for
 # the Windows 10 platform.
 #
@@ -738,13 +718,6 @@ RCC = $(RCC) -DSQLITE_WIN32_MALLOC_VALIDATE=1
 !ENDIF


-# Address sanitizer if ASAN=1
-#
-!IF $(ASAN)>0
-TCC = $(TCC) /fsanitize=address
-!ENDIF
-
-
 # Compiler options needed for programs that use the readline() library.
 #
 !IFNDEF READLINE_FLAGS
@@ -19,7 +19,7 @@ dnl	to configure the system for the local environment.
 # so that we create the export library with the dll.
 #-----------------------------------------------------------------------

-AC_INIT([sqlite],[3.44.0])
+AC_INIT([sqlite],[3.42.0])

 #--------------------------------------------------------------------
 # Call TEA_INIT as the first TEA_ macro to set up initial vars.
@@ -1,6 +1,6 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for sqlite 3.44.0.
+# Generated by GNU Autoconf 2.69 for sqlite 3.43.0.
 #
 #
 # Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
@@ -726,8 +726,8 @@ MAKEFLAGS=
 # Identity of this package.
 PACKAGE_NAME='sqlite'
 PACKAGE_TARNAME='sqlite'
-PACKAGE_VERSION='3.44.0'
-PACKAGE_STRING='sqlite 3.44.0'
+PACKAGE_VERSION='3.43.0'
+PACKAGE_STRING='sqlite 3.43.0'
 PACKAGE_BUGREPORT=''
 PACKAGE_URL=''

@@ -776,7 +776,6 @@ OPT_FEATURE_FLAGS
 HAVE_ZLIB
 USE_AMALGAMATION
 TARGET_DEBUG
-TARGET_HAVE_LINENOISE
 TARGET_HAVE_EDITLINE
 TARGET_HAVE_READLINE
 TARGET_READLINE_INC
@@ -904,7 +903,6 @@ enable_editline
 enable_readline
 with_readline_lib
 with_readline_inc
-with_linenoise
 enable_debug
 enable_amalgamation
 enable_load_extension
@@ -1472,7 +1470,7 @@ if test "$ac_init_help" = "long"; then
  # Omit some internal or obsolete options to make the list less imposing.
  # This message is too long to be a string in the A/UX 3.1 sh.
  cat <<_ACEOF
-\`configure' configures sqlite 3.44.0 to adapt to many kinds of systems.
+\`configure' configures sqlite 3.43.0 to adapt to many kinds of systems.

 Usage: $0 [OPTION]... [VAR=VALUE]...

@@ -1537,7 +1535,7 @@ fi

 if test -n "$ac_init_help"; then
  case $ac_init_help in
-     short | recursive ) echo "Configuration of sqlite 3.44.0:";;
+     short | recursive ) echo "Configuration of sqlite 3.43.0:";;
   esac
  cat <<\_ACEOF

@@ -1589,7 +1587,6 @@ Optional Packages:
                          (tclConfig.sh)
  --with-readline-lib     specify readline library
  --with-readline-inc     specify readline include paths
-  --with-linenoise=DIR    source directory for linenoise library

 Some influential environment variables:
  CC          C compiler command
@@ -1668,7 +1665,7 @@ fi
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
  cat <<\_ACEOF
-sqlite configure 3.44.0
+sqlite configure 3.43.0
 generated by GNU Autoconf 2.69

 Copyright (C) 2012 Free Software Foundation, Inc.
@@ -2087,7 +2084,7 @@ cat >config.log <<_ACEOF
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.

-It was created by sqlite $as_me 3.44.0, which was
+It was created by sqlite $as_me 3.43.0, which was
 generated by GNU Autoconf 2.69.  Invocation command line was

  $ $0 $@
@@ -3945,13 +3942,13 @@ if ${lt_cv_nm_interface+:} false; then :
 else
  lt_cv_nm_interface="BSD nm"
  echo "int some_variable = 0;" > conftest.$ac_ext
-  (eval echo "\"\$as_me:3948: $ac_compile\"" >&5)
+  (eval echo "\"\$as_me:3945: $ac_compile\"" >&5)
  (eval "$ac_compile" 2>conftest.err)
  cat conftest.err >&5
-  (eval echo "\"\$as_me:3951: $NM \\\"conftest.$ac_objext\\\"\"" >&5)
+  (eval echo "\"\$as_me:3948: $NM \\\"conftest.$ac_objext\\\"\"" >&5)
  (eval "$NM \"conftest.$ac_objext\"" 2>conftest.err > conftest.out)
  cat conftest.err >&5
-  (eval echo "\"\$as_me:3954: output\"" >&5)
+  (eval echo "\"\$as_me:3951: output\"" >&5)
  cat conftest.out >&5
  if $GREP 'External.*some_variable' conftest.out > /dev/null; then
    lt_cv_nm_interface="MS dumpbin"
@@ -5157,7 +5154,7 @@ ia64-*-hpux*)
  ;;
 *-*-irix6*)
  # Find out which ABI we are using.
-  echo '#line 5160 "configure"' > conftest.$ac_ext
+  echo '#line 5157 "configure"' > conftest.$ac_ext
  if { { eval echo "\"\$as_me\":${as_lineno-$LINENO}: \"$ac_compile\""; } >&5
  (eval $ac_compile) 2>&5
  ac_status=$?
@@ -6682,11 +6679,11 @@ else
   -e 's:.*FLAGS}\{0,1\} :&$lt_compiler_flag :; t' \
   -e 's: [^ ]*conftest\.: $lt_compiler_flag&:; t' \
   -e 's:$: $lt_compiler_flag:'`
-   (eval echo "\"\$as_me:6685: $lt_compile\"" >&5)
+   (eval echo "\"\$as_me:6682: $lt_compile\"" >&5)
   (eval "$lt_compile" 2>conftest.err)
   ac_status=$?
   cat conftest.err >&5
-   echo "$as_me:6689: \$? = $ac_status" >&5
+   echo "$as_me:6686: \$? = $ac_status" >&5
   if (exit $ac_status) && test -s "$ac_outfile"; then
     # The compiler can only warn and ignore the option if not recognized
     # So say no if there are warnings other than the usual output.
@@ -7021,11 +7018,11 @@ else
   -e 's:.*FLAGS}\{0,1\} :&$lt_compiler_flag :; t' \
   -e 's: [^ ]*conftest\.: $lt_compiler_flag&:; t' \
   -e 's:$: $lt_compiler_flag:'`
-   (eval echo "\"\$as_me:7024: $lt_compile\"" >&5)
+   (eval echo "\"\$as_me:7021: $lt_compile\"" >&5)
   (eval "$lt_compile" 2>conftest.err)
   ac_status=$?
   cat conftest.err >&5
-   echo "$as_me:7028: \$? = $ac_status" >&5
+   echo "$as_me:7025: \$? = $ac_status" >&5
   if (exit $ac_status) && test -s "$ac_outfile"; then
     # The compiler can only warn and ignore the option if not recognized
     # So say no if there are warnings other than the usual output.
@@ -7126,11 +7123,11 @@ else
   -e 's:.*FLAGS}\{0,1\} :&$lt_compiler_flag :; t' \
   -e 's: [^ ]*conftest\.: $lt_compiler_flag&:; t' \
   -e 's:$: $lt_compiler_flag:'`
-   (eval echo "\"\$as_me:7129: $lt_compile\"" >&5)
+   (eval echo "\"\$as_me:7126: $lt_compile\"" >&5)
   (eval "$lt_compile" 2>out/conftest.err)
   ac_status=$?
   cat out/conftest.err >&5
-   echo "$as_me:7133: \$? = $ac_status" >&5
+   echo "$as_me:7130: \$? = $ac_status" >&5
   if (exit $ac_status) && test -s out/conftest2.$ac_objext
   then
     # The compiler can only warn and ignore the option if not recognized
@@ -7181,11 +7178,11 @@ else
   -e 's:.*FLAGS}\{0,1\} :&$lt_compiler_flag :; t' \
   -e 's: [^ ]*conftest\.: $lt_compiler_flag&:; t' \
   -e 's:$: $lt_compiler_flag:'`
-   (eval echo "\"\$as_me:7184: $lt_compile\"" >&5)
+   (eval echo "\"\$as_me:7181: $lt_compile\"" >&5)
   (eval "$lt_compile" 2>out/conftest.err)
   ac_status=$?
   cat out/conftest.err >&5
-   echo "$as_me:7188: \$? = $ac_status" >&5
+   echo "$as_me:7185: \$? = $ac_status" >&5
   if (exit $ac_status) && test -s out/conftest2.$ac_objext
   then
     # The compiler can only warn and ignore the option if not recognized
@@ -9561,7 +9558,7 @@ else
  lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2
  lt_status=$lt_dlunknown
  cat > conftest.$ac_ext <<_LT_EOF
-#line 9564 "configure"
+#line 9561 "configure"
 #include "confdefs.h"

 #if HAVE_DLFCN_H
@@ -9657,7 +9654,7 @@ else
  lt_dlunknown=0; lt_dlno_uscore=1; lt_dlneed_uscore=2
  lt_status=$lt_dlunknown
  cat > conftest.$ac_ext <<_LT_EOF
-#line 9660 "configure"
+#line 9657 "configure"
 #include "confdefs.h"

 #if HAVE_DLFCN_H
@@ -11248,27 +11245,6 @@ fi
 	fi
 fi

-# Check whether --with-linenoise was given.
-if test "${with_linenoise+set}" = set; then :
-  withval=$with_linenoise; with_linenoise=$withval
-else
-  with_linenoise="no"
-fi
-
-if test "x$with_linenoise" != "xno"; then
-   TARGET_HAVE_READLINE=0
-   TARGET_HAVE_EDITLINE=0
-   TARGET_HAVE_LINENOISE=1
-   TARGET_READLINE_INC="-I${with_linenoise}"
-   TARGET_READLINE_LIBS="${with_linenoise}/linenoise.c"
-   echo "using linenoise source code at ${with_linenoise}"
-else
-   TARGET_HAVE_LINENOISE=0
-   echo "not using linenoise"
-fi
-
-
-



@@ -12481,7 +12457,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by sqlite $as_me 3.44.0, which was
+This file was extended by sqlite $as_me 3.43.0, which was
 generated by GNU Autoconf 2.69.  Invocation command line was

  CONFIG_FILES    = $CONFIG_FILES
@@ -12547,7 +12523,7 @@ _ACEOF
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
 ac_cs_version="\\
-sqlite config.status 3.44.0
+sqlite config.status 3.43.0
 configured by $0, generated by GNU Autoconf 2.69,
  with options \\"\$ac_cs_config\\"

@@ -598,28 +598,11 @@ if test x"$with_readline" != xno; then
 		TARGET_HAVE_READLINE=1
 	fi
 fi
-AC_ARG_WITH([linenoise],
-            [AS_HELP_STRING([--with-linenoise=DIR],[source directory for linenoise library])],
-            [with_linenoise=$withval],
-            [with_linenoise="no"])
-if test "x$with_linenoise" != "xno"; then
-   TARGET_HAVE_READLINE=0
-   TARGET_HAVE_EDITLINE=0
-   TARGET_HAVE_LINENOISE=1
-   TARGET_READLINE_INC="-I${with_linenoise}"
-   TARGET_READLINE_LIBS="${with_linenoise}/linenoise.c"
-   echo "using linenoise source code at ${with_linenoise}"
-else
-   TARGET_HAVE_LINENOISE=0
-   echo "not using linenoise"
-fi

 AC_SUBST(TARGET_READLINE_LIBS)
 AC_SUBST(TARGET_READLINE_INC)
 AC_SUBST(TARGET_HAVE_READLINE)
 AC_SUBST(TARGET_HAVE_EDITLINE)
-AC_SUBST(TARGET_HAVE_LINENOISE)
-

 ##########
 # Figure out what C libraries are required to compile programs
@@ -1,85 +0,0 @@
-# Notes On Compiling SQLite On Windows 11
-
-Here are step-by-step instructions on how to build SQLite from
-canonical source on a new Windows 11 PC, as of 2023-08-16:
-
-  1.  Install Microsoft Visual Studio. The free "community edition" 
-      will work fine.  Do a standard install for C++ development.
-      SQLite only needs the
-      "cl" compiler and the "nmake" build tool.
-
-  2.  Under the "Start" menu, find "All Apps" then go to "Visual Studio 20XX"
-      and find "x64 Native Tools Command Prompt for VS 20XX".  Pin that
-      application to your task bar, as you will use it a lot.  Bring up
-      an instance of this command prompt and do all of the subsequent steps
-      in that "x64 Native Tools" command prompt.  (Or use "x86" if you want
-      a 32-bit build.)  The subsequent steps will not work in a vanilla
-      DOS prompt.  Nor will they work in PowerShell.
-
-  3.  Install TCL development libraries.  This note assumes that you wil
-      install the TCL development libraries in the "`c:\Tcl`" directory.
-      Make adjustments
-      if you want TCL installed somewhere else.  SQLite needs both the
-      "tclsh.exe" command-line tool as part of the build process, and
-      the "tcl86.lib" library in order to run tests.  You will need
-      TCL version 8.6 or later.
-      <ol type="a">
-      <li>Get the TCL source archive, perhaps from
-      [https://www.tcl.tk/software/tcltk/download.html](https://www.tcl.tk/software/tcltk/download.html).
-      <li>Untar or unzip the source archive.  CD into the "win/" subfolder
-          of the source tree.
-      <li>Run: `nmake /f makefile.vc release`
-      <li>Run: `nmake /f makefile.vc INSTALLDIR=c:\Tcl install`
-      <li>CD to `c:\Tcl\lib`.  In that subfolder make a copy of the
-          "`tcl86t.lib`" file to the alternative name "`tcl86.lib`"
-          (omitting the second 't').  Leave the copy in the same directory
-          as the original.
-      <li>CD to `c:\Tcl\bin`.  Make a copy of the "`tclsh86t.exe`"
-          file into "`tclsh.exe`" (without the "86t") in the same directory.
-      <li>Add `c:\Tcl\bin` to your %PATH%.  To do this, go to Settings
-          and search for "path".  Select "edit environment variables for
-          your account" and modify your default PATH accordingly.
-          You will need to close and reopen your command prompts after
-          making this change.
-      </ol>
-
-  4.  Download the SQLite source tree and unpack it. CD into the
-      toplevel directory of the source tree.
-
-  5.  Set the TCLDIR environment variable to point to your TCL installation.
-      Like this:
-      <ul>
-      <li> `set TCLDIR=c:\Tcl`
-      </ul>
-
-  6.  Run the "`Makefile.msc`" makefile with an appropriate target.
-      Examples:
-      <ul>
-      <li>  `nmake /f makefile.msc`
-      <li>  `nmake /f makefile.msc sqlite3.c`
-      <li>  `nmake /f makefile.msc devtest`
-      <li>  `nmake /f makefile.msc releasetest`
-      </ul>
-
-## 32-bit Builds
-
-Doing a 32-bit build is just like doing a 64-bit build with the
-following minor changes:
-
-  1.  Use the "x86 Native Tools Command Prompt" instead of
-      "x64 Native Tools Command Prompt".  "**x86**" instead of "**x64**".
-
-  2.  Use a different installation directory for TCL.
-      The recommended directory is `c:\tcl32`.  Thus you end up
-      with two TCL builds:
-      <ul>
-      <li> `c:\tcl` &larr;  64-bit (the default)
-      <li> `c:\tcl32` &larr;  32-bit
-      </ul>
-
-  3.  Ensure that `c:\tcl32\bin` comes before `c:\tcl\bin` on
-      your PATH environment variable.  You can achieve this using
-      a command like:
-      <ul>
-      <li>  `set PATH=c:\tcl32\bin;%PATH%`
-      </ul>
@@ -1229,8 +1229,8 @@ first syntax error, of course, if there are no instances of the

 <p>Lemon was originally written by Richard Hipp sometime in the late
 1980s on a Sun4 Workstation using K&amp;R C.  
-There was a companion LL(1) parser generator program named "Lime".
-The Lime source code has been lost.</p>
+There was a companion LL(1) parser generator program named "Lime", the
+source code to which as been lost.</p>

 <p>The lemon.c source file was originally many separate files that were
 compiled together to generate the "lemon" executable.  Sometime in the
@@ -1,284 +0,0 @@
-
-
-# The testrunner.tcl Script
-
-# 1. Overview
-
-testrunner.tcl is a Tcl script used to run multiple SQLite tests using 
-multiple jobs. It supports the following types of tests:
-
-  *  Tcl test scripts.
-
-  *  Tests run with [make] commands. Specifically, at time of writing, 
-     [make fuzztest], [make mptest], [make sourcetest] and [make threadtest].
-
-testrunner.tcl pipes the output of all tests and builds run into log file
-**testrunner.log**, created in the cwd directory. Searching this file for
-"failed" is a good way to find the output of a failed test.
-
-testrunner.tcl also populates SQLite database **testrunner.db**. This database
-contains details of all tests run, running and to be run. A useful query
-might be:
-
-```
-  SELECT * FROM script WHERE state='failed'
-```
-
-Running the command:
-
-```
-  ./testfixture $(TESTDIR)/testrunner.tcl status
-```
-
-in the directory containing the testrunner.db database runs various queries
-to produce a succinct report on the state of a running testrunner.tcl script.
-Running:
-
-```
-  watch ./testfixture $(TESTDIR)/testrunner.tcl status
-```
-
-in another terminal is a good way to keep an eye on a long running test.
-
-Sometimes testrunner.tcl uses the [testfixture] binary that it is run with
-to run tests (see "Binary Tests" below). Sometimes it builds testfixture and
-other binaries in specific configurations to test (see "Source Tests").
-
-# 2. Binary Tests
-
-The commands described in this section all run various combinations of the Tcl
-test scripts using the [testfixture] binary used to run the testrunner.tcl
-script (i.e. they do not invoke the compiler to build new binaries, or the
-[make] command to run tests that are not Tcl scripts). The procedure to run
-these tests is therefore:
-
-  1. Build the "testfixture" (or "testfixture.exe" for windows) binary using
-     whatever method seems convenient.
-
-  2. Test the binary built in step 1 by running testrunner.tcl with it, 
-     perhaps with various options.
-
-The following sub-sections describe the various options that can be
-passed to testrunner.tcl to test binary testfixture builds.
-
-## 2.1. Organization of Tcl Tests
-
-Tcl tests are stored in files that match the pattern *\*.test*. They are
-found in both the $TOP/test/ directory, and in the various sub-directories
-of the $TOP/ext/ directory of the source tree. Not all *\*.test* files
-contain Tcl tests - a handful are Tcl scripts designed to invoke other
-*\*.test* files.
-
-The **veryquick** set of tests is a subset of all Tcl test scripts in the
-source tree. In includes most tests, but excludes some that are very slow.
-Almost all fault-injection tests (those that test the response of the library
-to OOM or IO errors) are excluded. It is defined in source file 
-*test/permutations.test*.
-
-The **full** set of tests includes all Tcl test scripts in the source tree.
-To run a "full" test is to run all Tcl test scripts that can be found in the
-source tree.
-
-File *permutations.test* defines various test "permutations". A permutation
-consists of:
-
-  *  A subset of Tcl test scripts, and 
-
-  *  Runtime configuration to apply before running each test script 
-     (e.g. enabling auto-vacuum, or disable lookaside).
-
-Running **all** tests is to run all tests in the full test set, plus a dozen
-or so permutations. The specific permutations that are run as part of "all"
-are defined in file *testrunner_data.tcl*.
-
-## 2.2. Commands to Run Tests
-
-To run the "veryquick" test set, use either of the following:
-
-```
-  ./testfixture $TESTDIR/testrunner.tcl
-  ./testfixture $TESTDIR/testrunner.tcl veryquick
-```
-
-To run the "full" test suite:
-
-```
-  ./testfixture $TESTDIR/testrunner.tcl full
-```
-
-To run the subset of the "full" test suite for which the test file name matches
-a specified pattern (e.g. all tests that start with "fts5"), either of:
-
-```
-  ./testfixture $TESTDIR/testrunner.tcl fts5%
-  ./testfixture $TESTDIR/testrunner.tcl 'fts5*'
-```
-
-To run "all" tests (full + permutations):
-
-```
-  ./testfixture $TESTDIR/testrunner.tcl all
-```
-
-<a name=binary_test_failures></a>
-## 2.3. Investigating Binary Test Failures
-
-If a test fails, testrunner.tcl reports name of the Tcl test script and, if
-applicable, the name of the permutation, to stdout. This information can also
-be retrieved from either *testrunner.log* or *testrunner.db*.
-
-If there is no permutation, the individual test script may be run with:
-
-```
-  ./testfixture $PATH_TO_SCRIPT
-```
-
-Or, if the failure occured as part of a permutation:
-
-```
-  ./testfixture $TESTDIR/testrunner.tcl $PERMUTATION $PATH_TO_SCRIPT
-```
-
-TODO: An example instead of "$PERMUTATION" and $PATH\_TO\_SCRIPT?
-
-# 3. Source Code Tests
-
-The commands described in this section invoke the C compiler to build 
-binaries from the source tree, then use those binaries to run Tcl and
-other tests. The advantages of this are that:
-
-  *  it is possible to test multiple build configurations with a single
-     command, and 
-
-  *  it ensures that tests are always run using binaries created with the
-     same set of compiler options.
-
-The testrunner.tcl commands described in this section may be run using
-either a *testfixture* (or testfixture.exe) build, or with any other Tcl
-shell that supports SQLite 3.31.1 or newer via "package require sqlite3".
-
-TODO: ./configure + Makefile.msc build systems.
-
-## Commands to Run SQLite Tests
-
-The **mdevtest** command is equivalent to running the veryquick tests and
-the [make fuzztest] target once for each of two --enable-all builds - one 
-with debugging enabled and one without:
-
-```
-  tclsh $TESTDIR/testrunner.tcl mdevtest
-```
-
-In other words, it is equivalent to running:
-
-```
-  $TOP/configure --enable-all --enable-debug
-  make fuzztest
-  make testfixture
-  ./testfixture $TOP/test/testrunner.tcl veryquick
-
-  # Then, after removing files created by the tests above:
-  $TOP/configure --enable-all OPTS="-O0"
-  make fuzztest
-  make testfixture
-  ./testfixture $TOP/test/testrunner.tcl veryquick
-```
-
-The **sdevtest** command is identical to the mdevtest command, except that the
-second of the two builds is a sanitizer build. Specifically, this means that
-OPTS="-fsanitize=address,undefined" is specified instead of OPTS="-O0":
-
-```
-  tclsh $TESTDIR/testrunner.tcl sdevtest
-```
-
-The **release** command runs lots of tests under lots of builds. It runs
-different combinations of builds and tests depending on whether it is run
-on Linux, Windows or OSX. Refer to *testrunner\_data.tcl* for the details
-of the specific tests run.
-
-```
-  tclsh $TESTDIR/testrunner.tcl release
-```
-
-## Running ZipVFS Tests
-
-testrunner.tcl can build a zipvfs-enabled testfixture and use it to run
-tests from the Zipvfs project with the following command:
-
-```
-  tclsh $TESTDIR/testrunner.tcl --zipvfs $PATH_TO_ZIPVFS
-```
-
-This can be combined with any of "mdevtest", "sdevtest" or "release" to
-test both SQLite and Zipvfs with a single command:
-
-```
-  tclsh $TESTDIR/testrunner.tcl --zipvfs $PATH_TO_ZIPVFS mdevtest
-```
-
-## Investigating Source Code Test Failures
-
-Investigating a test failure that occurs during source code testing is a
-two step process:
-
-  1. Recreating the build configuration in which the test failed, and
-
-  2. Re-running the actual test.
-
-To recreate a build configuration, use the testrunner.tcl **script** command
-to create a build script. A build script is a bash script on Linux or OSX, or
-a dos \*.bat file on windows. For example:
-
-```
-  # Create a script that recreates build configuration "Device-One" on 
-  # Linux or OSX:
-  tclsh $TESTDIR/testrunner.tcl script Device-One > make.sh 
-
-  # Create a script that recreates build configuration "Have-Not" on Windows:
-  tclsh $TESTDIR/testrunner.tcl script Have-Not > make.bat 
-```
-
-The generated bash or \*.bat file script accepts a single argument - a makefile
-target to build. This may be used either to run a [make] command test directly,
-or else to build a testfixture (or testfixture.exe) binary with which to
-run a Tcl test script, as <a href=#binary_test_failures>described above</a>.
-
-
-
-# 4. Controlling CPU Core Utilization
-
-When running either binary or source code tests, testrunner.tcl reports the
-number of jobs it intends to use to stdout. e.g.
-
-```
-  $ ./testfixture $TESTDIR/testrunner.tcl
-  splitting work across 16 jobs
-  ... more output ...
-```
-
-By default, testfixture.tcl attempts to set the number of jobs to the number 
-of real cores on the machine. This can be overridden using the "--jobs" (or -j)
-switch:
-
-```
-  $ ./testfixture $TESTDIR/testrunner.tcl --jobs 8
-  splitting work across 8 jobs
-  ... more output ...
-```
-
-The number of jobs may also be changed while an instance of testrunner.tcl is
-running by exucuting the following command from the directory containing the
-testrunner.log and testrunner.db files:
-
-```
-  $ ./testfixture $TESTDIR/testrunner.tcl njob $NEW_NUMBER_OF_JOBS
-```
-
-
-
-
-
-
-
-
@@ -3980,32 +3980,8 @@ static int fts3ShadowName(const char *zName){
  return 0;
 }

-/*
-** Implementation of the xIntegrity() method on the FTS3/FTS4 virtual
-** table.
-*/
-static int fts3Integrity(sqlite3_vtab *pVtab, char **pzErr){
-  Fts3Table *p = (Fts3Table*)pVtab;
-  char *zSql;
-  int rc;
-
-  zSql = sqlite3_mprintf(
-            "INSERT INTO \"%w\".\"%w\"(\"%w\") VALUES('integrity-check');",
-            p->zDb, p->zName, p->zName);
-  rc = sqlite3_exec(p->db, zSql, 0, 0, 0);
-  sqlite3_free(zSql);
-  if( (rc&0xff)==SQLITE_CORRUPT ){
-    *pzErr = sqlite3_mprintf("malformed inverted index for FTS%d table %s.%s",
-                p->bFts4 ? 4 : 3, p->zDb, p->zName);
-    rc = SQLITE_OK;
-  }
-  return rc;
-}
-
-
-
 static const sqlite3_module fts3Module = {
-  /* iVersion      */ 4,
+  /* iVersion      */ 3,
  /* xCreate       */ fts3CreateMethod,
  /* xConnect      */ fts3ConnectMethod,
  /* xBestIndex    */ fts3BestIndexMethod,
@@ -4029,7 +4005,6 @@ static const sqlite3_module fts3Module = {
  /* xRelease      */ fts3ReleaseMethod,
  /* xRollbackTo   */ fts3RollbackToMethod,
  /* xShadowName   */ fts3ShadowName,
-  /* xIntegrity    */ fts3Integrity,
 };

 /*
@@ -5218,7 +5218,7 @@ static u64 fts3ChecksumIndex(
  int rc;
  u64 cksum = 0;

-  if( *pRc ) return 0;
+  assert( *pRc==SQLITE_OK );

  memset(&filter, 0, sizeof(filter));
  memset(&csr, 0, sizeof(csr));
@@ -263,7 +263,7 @@ struct Fts5PhraseIter {
 **   See xPhraseFirstColumn above.
 */
 struct Fts5ExtensionApi {
-  int iVersion;                   /* Currently always set to 2 */
+  int iVersion;                   /* Currently always set to 3 */

  void *(*xUserData)(Fts5Context*);

@@ -492,8 +492,8 @@ struct Fts5ExtensionApi {
 **   as separate queries of the FTS index are required for each synonym.
 **
 **   When using methods (2) or (3), it is important that the tokenizer only
-**   provide synonyms when tokenizing document text (method (3)) or query
-**   text (method (2)), not both. Doing so will not cause any errors, but is
+**   provide synonyms when tokenizing document text (method (2)) or query
+**   text (method (3)), not both. Doing so will not cause any errors, but is
 **   inefficient.
 */
 typedef struct Fts5Tokenizer Fts5Tokenizer;
@@ -541,7 +541,7 @@ struct fts5_api {
  int (*xCreateTokenizer)(
    fts5_api *pApi,
    const char *zName,
-    void *pUserData,
+    void *pContext,
    fts5_tokenizer *pTokenizer,
    void (*xDestroy)(void*)
  );
@@ -550,7 +550,7 @@ struct fts5_api {
  int (*xFindTokenizer)(
    fts5_api *pApi,
    const char *zName,
-    void **ppUserData,
+    void **ppContext,
    fts5_tokenizer *pTokenizer
  );

@@ -558,7 +558,7 @@ struct fts5_api {
  int (*xCreateFunction)(
    fts5_api *pApi,
    const char *zName,
-    void *pUserData,
+    void *pContext,
    fts5_extension_function xFunction,
    void (*xDestroy)(void*)
  );
@@ -2583,8 +2583,6 @@ static char *fts5ExprPrintTcl(
      if( zRet==0 ) return 0;
    }

-  }else if( pExpr->eType==0 ){
-    zRet = sqlite3_mprintf("{}");
  }else{
    char const *zOp = 0;
    int i;
@@ -3272,7 +3272,7 @@ static Fts5Iter *fts5MultiIterAlloc(
  int nSeg
 ){
  Fts5Iter *pNew;
-  i64 nSlot;                      /* Power of two >= nSeg */
+  int nSlot;                      /* Power of two >= nSeg */

  for(nSlot=2; nSlot<nSeg; nSlot=nSlot*2);
  pNew = fts5IdxMalloc(p, 
@@ -4752,7 +4752,7 @@ static int fts5IndexFindDeleteMerge(Fts5Index *p, Fts5Structure *pStruct){
        nEntry += pLvl->aSeg[iSeg].nEntry;
        nTomb += pLvl->aSeg[iSeg].nEntryTombstone;
      }
-      assert_nc( nEntry>0 || pLvl->nSeg==0 );
+      assert( nEntry>0 || pLvl->nSeg==0 );
      if( nEntry>0 ){
        int nPercent = (nTomb * 100) / nEntry;
        if( nPercent>=pConfig->nDeleteMerge && nPercent>nBest ){
@@ -5048,6 +5048,7 @@ static void fts5DoSecureDelete(
  int iPgIdx = pSeg->pLeaf->szLeaf;

  u64 iDelta = 0;
+  u64 iNextDelta = 0;
  int iNextOff = 0;
  int iOff = 0;
  int nIdx = 0;
@@ -5055,6 +5056,8 @@ static void fts5DoSecureDelete(
  int bLastInDoclist = 0;
  int iIdx = 0;
  int iStart = 0;
+  int iKeyOff = 0;
+  int iPrevKeyOff = 0;
  int iDelKeyOff = 0;       /* Offset of deleted key, if any */

  nIdx = nPg-iPgIdx;
@@ -5079,21 +5082,10 @@ static void fts5DoSecureDelete(
  ** This block sets the following variables:
  **
  **   iStart:
-  **     The offset of the first byte of the rowid or delta-rowid
-  **     value for the doclist entry being removed.
-  **
  **   iDelta:
-  **     The value of the rowid or delta-rowid value for the doclist
-  **     entry being removed.
-  **
-  **   iNextOff:
-  **     The offset of the next entry following the position list
-  **     for the one being removed. If the position list for this
-  **     entry overflows onto the next leaf page, this value will be
-  **     greater than pLeaf->szLeaf.
  */
  {
-    int iSOP;                     /* Start-Of-Position-list */
+    int iSOP;
    if( pSeg->iLeafPgno==pSeg->iTermLeafPgno ){
      iStart = pSeg->iTermLeafOffset;
    }else{
@@ -5129,20 +5121,14 @@ static void fts5DoSecureDelete(
  }

  iOff = iStart;
-
-  /* Set variable bLastInDoclist to true if this entry happens to be
-  ** the last rowid in the doclist for its term.  */
  if( iNextOff>=iPgIdx ){
    int pgno = pSeg->iLeafPgno+1;
    fts5SecureDeleteOverflow(p, pSeg->pSeg, pgno, &bLastInDoclist);
    iNextOff = iPgIdx;
  }else{
-    /* Loop through the page-footer. If iNextOff (offset of the
-    ** entry following the one we are removing) is equal to the 
-    ** offset of a key on this page, then the entry is the last 
+    /* Set bLastInDoclist to true if the entry being removed is the last
    ** in its doclist.  */
-    int iKeyOff = 0;
-    for(iIdx=0; iIdx<nIdx; /* no-op */){
+    for(iIdx=0, iKeyOff=0; iIdx<nIdx; /* no-op */){
      u32 iVal = 0;
      iIdx += fts5GetVarint32(&aIdx[iIdx], iVal);
      iKeyOff += iVal;
@@ -5152,47 +5138,30 @@ static void fts5DoSecureDelete(
    }
  }

-  /* If this is (a) the first rowid on a page and (b) is not followed by
-  ** another position list on the same page, set the "first-rowid" field
-  ** of the header to 0.  */
-  if( fts5GetU16(&aPg[0])==iStart && (bLastInDoclist || iNextOff==iPgIdx) ){
+  if( fts5GetU16(&aPg[0])==iStart && (bLastInDoclist||iNextOff==iPgIdx) ){
    fts5PutU16(&aPg[0], 0);
  }

  if( bLastInDoclist==0 ){
    if( iNextOff!=iPgIdx ){
-      u64 iNextDelta = 0;
      iNextOff += fts5GetVarint(&aPg[iNextOff], &iNextDelta);
      iOff += sqlite3Fts5PutVarint(&aPg[iOff], iDelta + iNextDelta);
    }
  }else if( 
-      pSeg->iLeafPgno==pSeg->iTermLeafPgno 
-   && iStart==pSeg->iTermLeafOffset 
+      iStart==pSeg->iTermLeafOffset && pSeg->iLeafPgno==pSeg->iTermLeafPgno 
  ){
    /* The entry being removed was the only position list in its
    ** doclist. Therefore the term needs to be removed as well. */
    int iKey = 0;
-    int iKeyOff = 0;
-
-    /* Set iKeyOff to the offset of the term that will be removed - the
-    ** last offset in the footer that is not greater than iStart. */
-    for(iIdx=0; iIdx<nIdx; iKey++){
+    for(iIdx=0, iKeyOff=0; iIdx<nIdx; iKey++){
      u32 iVal = 0;
      iIdx += fts5GetVarint32(&aIdx[iIdx], iVal);
      if( (iKeyOff+iVal)>(u32)iStart ) break;
      iKeyOff += iVal;
    }
-    assert_nc( iKey>=1 );

-    /* Set iDelKeyOff to the value of the footer entry to remove from 
-    ** the page. */
    iDelKeyOff = iOff = iKeyOff;
-
    if( iNextOff!=iPgIdx ){
-      /* This is the only position-list associated with the term, and there
-      ** is another term following it on this page. So the subsequent term
-      ** needs to be moved to replace the term associated with the entry
-      ** being removed. */
      int nPrefix = 0;
      int nSuffix = 0;
      int nPrefix2 = 0;
@@ -5229,79 +5198,80 @@ static void fts5DoSecureDelete(
      }
    }
  }else if( iStart==4 ){
-    int iPgno;
+      int iPgno;

-    assert_nc( pSeg->iLeafPgno>pSeg->iTermLeafPgno );
-    /* The entry being removed may be the only position list in
-    ** its doclist. */
-    for(iPgno=pSeg->iLeafPgno-1; iPgno>pSeg->iTermLeafPgno; iPgno-- ){
-      Fts5Data *pPg = fts5DataRead(p, FTS5_SEGMENT_ROWID(iSegid, iPgno));
-      int bEmpty = (pPg && pPg->nn==4);
-      fts5DataRelease(pPg);
-      if( bEmpty==0 ) break;
-    }
-
-    if( iPgno==pSeg->iTermLeafPgno ){
-      i64 iId = FTS5_SEGMENT_ROWID(iSegid, pSeg->iTermLeafPgno);
-      Fts5Data *pTerm = fts5DataRead(p, iId);
-      if( pTerm && pTerm->szLeaf==pSeg->iTermLeafOffset ){
-        u8 *aTermIdx = &pTerm->p[pTerm->szLeaf];
-        int nTermIdx = pTerm->nn - pTerm->szLeaf;
-        int iTermIdx = 0;
-        int iTermOff = 0;
-
-        while( 1 ){
-          u32 iVal = 0;
-          int nByte = fts5GetVarint32(&aTermIdx[iTermIdx], iVal);
-          iTermOff += iVal;
-          if( (iTermIdx+nByte)>=nTermIdx ) break;
-          iTermIdx += nByte;
-        }
-        nTermIdx = iTermIdx;
-
-        memmove(&pTerm->p[iTermOff], &pTerm->p[pTerm->szLeaf], nTermIdx);
-        fts5PutU16(&pTerm->p[2], iTermOff);
-
-        fts5DataWrite(p, iId, pTerm->p, iTermOff+nTermIdx);
-        if( nTermIdx==0 ){
-          fts5SecureDeleteIdxEntry(p, iSegid, pSeg->iTermLeafPgno);
-        }
+      assert_nc( pSeg->iLeafPgno>pSeg->iTermLeafPgno );
+      /* The entry being removed may be the only position list in
+      ** its doclist. */
+      for(iPgno=pSeg->iLeafPgno-1; iPgno>pSeg->iTermLeafPgno; iPgno-- ){
+        Fts5Data *pPg = fts5DataRead(p, FTS5_SEGMENT_ROWID(iSegid, iPgno));
+        int bEmpty = (pPg && pPg->nn==4);
+        fts5DataRelease(pPg);
+        if( bEmpty==0 ) break;
      }
-      fts5DataRelease(pTerm);
-    }
-  }

-  if( p->rc==SQLITE_OK ){
-    const int nMove = nPg - iNextOff;     /* Number of bytes to move */
-    int nShift = iNextOff - iOff;         /* Distance to move them */
+      if( iPgno==pSeg->iTermLeafPgno ){
+        i64 iId = FTS5_SEGMENT_ROWID(iSegid, pSeg->iTermLeafPgno);
+        Fts5Data *pTerm = fts5DataRead(p, iId);
+        if( pTerm && pTerm->szLeaf==pSeg->iTermLeafOffset ){
+          u8 *aTermIdx = &pTerm->p[pTerm->szLeaf];
+          int nTermIdx = pTerm->nn - pTerm->szLeaf;
+          int iTermIdx = 0;
+          int iTermOff = 0;

-    int iPrevKeyOut = 0;
-    int iKeyIn = 0;
+          while( 1 ){
+            u32 iVal = 0;
+            int nByte = fts5GetVarint32(&aTermIdx[iTermIdx], iVal);
+            iTermOff += iVal;
+            if( (iTermIdx+nByte)>=nTermIdx ) break;
+            iTermIdx += nByte;
+          }
+          nTermIdx = iTermIdx;

-    memmove(&aPg[iOff], &aPg[iNextOff], nMove);
-    iPgIdx -= nShift;
-    nPg = iPgIdx;
-    fts5PutU16(&aPg[2], iPgIdx);
+          memmove(&pTerm->p[iTermOff], &pTerm->p[pTerm->szLeaf], nTermIdx);
+          fts5PutU16(&pTerm->p[2], iTermOff);

-    for(iIdx=0; iIdx<nIdx; /* no-op */){
-      u32 iVal = 0;
-      iIdx += fts5GetVarint32(&aIdx[iIdx], iVal);
-      iKeyIn += iVal;
-      if( iKeyIn!=iDelKeyOff ){
-        int iKeyOut = (iKeyIn - (iKeyIn>iOff ? nShift : 0));
-        nPg += sqlite3Fts5PutVarint(&aPg[nPg], iKeyOut - iPrevKeyOut);
-        iPrevKeyOut = iKeyOut;
+          fts5DataWrite(p, iId, pTerm->p, iTermOff+nTermIdx);
+          if( nTermIdx==0 ){
+            fts5SecureDeleteIdxEntry(p, iSegid, pSeg->iTermLeafPgno);
+          }
+        }
+        fts5DataRelease(pTerm);
      }
    }

-    if( iPgIdx==nPg && nIdx>0 && pSeg->iLeafPgno!=1 ){
-      fts5SecureDeleteIdxEntry(p, iSegid, pSeg->iLeafPgno);
-    }
+    if( p->rc==SQLITE_OK ){
+      const int nMove = nPg - iNextOff;
+      int nShift = 0;

-    assert_nc( nPg>4 || fts5GetU16(aPg)==0 );
-    fts5DataWrite(p, FTS5_SEGMENT_ROWID(iSegid,pSeg->iLeafPgno), aPg, nPg);
-  }
-  sqlite3_free(aIdx);
+      memmove(&aPg[iOff], &aPg[iNextOff], nMove);
+      iPgIdx -= (iNextOff - iOff);
+      nPg = iPgIdx;
+      fts5PutU16(&aPg[2], iPgIdx);
+
+      nShift = iNextOff - iOff;
+      for(iIdx=0, iKeyOff=0, iPrevKeyOff=0; iIdx<nIdx; /* no-op */){
+        u32 iVal = 0;
+        iIdx += fts5GetVarint32(&aIdx[iIdx], iVal);
+        iKeyOff += iVal;
+        if( iKeyOff!=iDelKeyOff ){
+          if( iKeyOff>iOff ){
+            iKeyOff -= nShift;
+            nShift = 0;
+          }
+          nPg += sqlite3Fts5PutVarint(&aPg[nPg], iKeyOff - iPrevKeyOff);
+          iPrevKeyOff = iKeyOff;
+        }
+      }
+
+      if( iPgIdx==nPg && nIdx>0 && pSeg->iLeafPgno!=1 ){
+        fts5SecureDeleteIdxEntry(p, iSegid, pSeg->iLeafPgno);
+      }
+
+      assert_nc( nPg>4 || fts5GetU16(aPg)==0 );
+      fts5DataWrite(p, FTS5_SEGMENT_ROWID(iSegid,pSeg->iLeafPgno), aPg,nPg);
+    }
+    sqlite3_free(aIdx);
 }

 /*
@@ -5451,8 +5421,7 @@ static void fts5FlushOneHash(Fts5Index *p){
              writer.bFirstRowidInPage = 0;
              fts5WriteDlidxAppend(p, &writer, iRowid);
            }else{
-              u64 iRowidDelta = (u64)iRowid - (u64)iPrev;
-              pBuf->n += sqlite3Fts5PutVarint(&pBuf->p[pBuf->n], iRowidDelta);
+              pBuf->n += sqlite3Fts5PutVarint(&pBuf->p[pBuf->n], iRowid-iPrev);
            }
            if( p->rc!=SQLITE_OK ) break;
            assert( pBuf->n<=pBuf->nSpace );
@@ -7846,7 +7815,7 @@ static void fts5DecodeFunction(
    fts5DecodeRowidList(&rc, &s, &a[4], iTermOff-4);

    iOff = iTermOff;
-    while( iOff<szLeaf && rc==SQLITE_OK ){
+    while( iOff<szLeaf ){
      int nAppend;

      /* Read the term data for the next term*/
@@ -7866,11 +7835,8 @@ static void fts5DecodeFunction(
      }else{
        iTermOff = szLeaf;
      }
-      if( iTermOff>szLeaf ){
-        rc = FTS5_CORRUPT;
-      }else{
-        fts5DecodeRowidList(&rc, &s, &a[iOff], iTermOff-iOff);
-      }
+
+      fts5DecodeRowidList(&rc, &s, &a[iOff], iTermOff-iOff);
      iOff = iTermOff;
      if( iOff<szLeaf ){
        iOff += fts5GetVarint32(&a[iOff], nKeep);
@@ -8126,16 +8092,15 @@ static int fts5structCloseMethod(sqlite3_vtab_cursor *cur){
 */
 static int fts5structNextMethod(sqlite3_vtab_cursor *cur){
  Fts5StructVcsr *pCsr = (Fts5StructVcsr*)cur;
-  Fts5Structure *p = pCsr->pStruct;

  assert( pCsr->pStruct );
  pCsr->iSeg++;
  pCsr->iRowid++;
-  while( pCsr->iLevel<p->nLevel && pCsr->iSeg>=p->aLevel[pCsr->iLevel].nSeg ){
+  while( pCsr->iSeg>=pCsr->pStruct->aLevel[pCsr->iLevel].nSeg ){
    pCsr->iLevel++;
    pCsr->iSeg = 0;
  }
-  if( pCsr->iLevel>=p->nLevel ){
+  if( pCsr->iLevel>=pCsr->pStruct->nLevel ){
    fts5StructureRelease(pCsr->pStruct);
    pCsr->pStruct = 0;
  }
@@ -1329,9 +1329,6 @@ static int fts5FilterMethod(
    pCsr->iFirstRowid = fts5GetRowidLimit(pRowidGe, SMALLEST_INT64);
  }

-  rc = sqlite3Fts5IndexLoadConfig(pTab->p.pIndex);
-  if( rc!=SQLITE_OK ) goto filter_out;
-
  if( pTab->pSortCsr ){
    /* If pSortCsr is non-NULL, then this call is being made as part of 
    ** processing for a "... MATCH <expr> ORDER BY rank" query (ePlan is
@@ -1354,7 +1351,6 @@ static int fts5FilterMethod(
    pCsr->pExpr = pTab->pSortCsr->pExpr;
    rc = fts5CursorFirst(pTab, pCsr, bDesc);
  }else if( pCsr->pExpr ){
-    assert( rc==SQLITE_OK );
    rc = fts5CursorParseRank(pConfig, pCsr, pRank);
    if( rc==SQLITE_OK ){
      if( bOrderByRank ){
@@ -1693,7 +1689,7 @@ static int fts5UpdateMethod(
    ** VIRTUAL TABLE statement contained "contentless_delete=1". */
    if( eType0==SQLITE_INTEGER 
     && pConfig->eContent==FTS5_CONTENT_NONE 
-     && pConfig->bContentlessDelete==0
+     && (nArg>1 || pConfig->bContentlessDelete==0)
    ){
      pTab->p.base.zErrMsg = sqlite3_mprintf(
          "cannot %s contentless fts5 table: %s", 
@@ -2548,12 +2544,6 @@ static int fts5ColumnMethod(
      sqlite3_result_value(pCtx, sqlite3_column_value(pCsr->pStmt, iCol+1));
    }
    pConfig->pzErrmsg = 0;
-  }else if( pConfig->bContentlessDelete && sqlite3_vtab_nochange(pCtx) ){
-    char *zErr = sqlite3_mprintf("cannot UPDATE a subset of "
-        "columns on fts5 contentless-delete table: %s", pConfig->zName
-    );
-    sqlite3_result_error(pCtx, zErr, -1);
-    sqlite3_free(zErr);
  }
  return rc;
 }
@@ -2854,33 +2844,9 @@ static int fts5ShadowName(const char *zName){
  return 0;
 }

-/*
-** Run an integrity check on the FTS5 data structures.  Return a string
-** if anything is found amiss.  Return a NULL pointer if everything is
-** OK.
-*/
-static int fts5Integrity(sqlite3_vtab *pVtab, char **pzErr){
-  Fts5FullTable *pTab = (Fts5FullTable*)pVtab;
-  Fts5Config *pConfig = pTab->p.pConfig;
-  char *zSql;
-  int rc;
-  zSql = sqlite3_mprintf(
-            "INSERT INTO \"%w\".\"%w\"(\"%w\") VALUES('integrity-check');",
-            pConfig->zDb, pConfig->zName, pConfig->zName);
-  rc = sqlite3_exec(pConfig->db, zSql, 0, 0, 0);
-  sqlite3_free(zSql);
-  if( (rc&0xff)==SQLITE_CORRUPT ){
-    *pzErr = sqlite3_mprintf("malformed inverted index for FTS5 table %s.%s",
-                pConfig->zDb, pConfig->zName);
-    rc = SQLITE_OK;
-  }
-  return rc;
-
-}
-
 static int fts5Init(sqlite3 *db){
  static const sqlite3_module fts5Mod = {
-    /* iVersion      */ 4,
+    /* iVersion      */ 3,
    /* xCreate       */ fts5CreateMethod,
    /* xConnect      */ fts5ConnectMethod,
    /* xBestIndex    */ fts5BestIndexMethod,
@@ -2903,8 +2869,7 @@ static int fts5Init(sqlite3 *db){
    /* xSavepoint    */ fts5SavepointMethod,
    /* xRelease      */ fts5ReleaseMethod,
    /* xRollbackTo   */ fts5RollbackToMethod,
-    /* xShadowName   */ fts5ShadowName,
-    /* xIntegrity    */ fts5Integrity
+    /* xShadowName   */ fts5ShadowName
  };

  int rc;
@@ -65,9 +65,7 @@ foreach w {a b c d e f} {

 do_execsql_test 2.4 {
  INSERT INTO t1(t1) VALUES('integrity-check');
-  PRAGMA integrity_check;
-  PRAGMA integrity_check(t1);
-} {ok ok}
+}


 #-------------------------------------------------------------------------
@@ -90,7 +88,6 @@ foreach {i x y} {
 } {
  do_execsql_test 3.$i.1 { INSERT INTO t1 VALUES($x, $y) }
  do_execsql_test 3.$i.2 { INSERT INTO t1(t1) VALUES('integrity-check') }
-  do_execsql_test 3.$i.3 { PRAGMA integrity_check(t1) } ok
  if {[set_test_counter errors]} break
 }

@@ -138,7 +135,7 @@ foreach {i x y} {
   10 {ddd abcde dddd dd c} {dddd c c d abcde}
 } {
  do_execsql_test 5.$i.1 { INSERT INTO t1 VALUES($x, $y) }
-  do_execsql_test 5.$i.2 { PRAGMA integrity_check(t1) } ok
+  do_execsql_test 5.$i.2 { INSERT INTO t1(t1) VALUES('integrity-check') }
  if {[set_test_counter errors]} break
 }

@@ -308,3 +308,4 @@ do_catchsql_test 10.1.4 {
 } {1 {unable to use function firstcol in the requested context}}

 finish_test
+
@@ -294,3 +294,4 @@ do_catchsql_test 7.2.5 {
 } {1 {recursively defined fts5 content table}}

 finish_test
+
@@ -188,11 +188,11 @@ do_execsql_test 5.2 {

 do_catchsql_test 5.3 {
  UPDATE ft SET x='four six' WHERE rowid=3
-} {0 {}}
+} {1 {cannot UPDATE contentless fts5 table: ft}}

 do_execsql_test 5.4 {
  SELECT rowid FROM ft('one');
-} {1 4 5}
+} {1 3 4 5}

 do_execsql_test 5.5 {
  REPLACE INTO ft(rowid, x) VALUES(3, 'four six');
@@ -268,3 +268,4 @@ do_execsql_test 8.2 {
 } {}

 finish_test
+
@@ -205,3 +205,4 @@ foreach {tn step} {


 finish_test
+
@@ -193,3 +193,4 @@ do_execsql_test 3.7 {


 finish_test
+
@@ -245,3 +245,4 @@ do_execsql_test 4.3 {
 }

 finish_test
+
@@ -1,58 +0,0 @@
-# 2023 August 7
-#
-# The author disclaims copyright to this source code.  In place of
-# a legal notice, here is a blessing:
-#
-#    May you do good and not evil.
-#    May you find forgiveness for yourself and forgive others.
-#    May you share freely, never taking more than you give.
-#
-#***********************************************************************
-#
-# This file contains tests for the content= and content_rowid= options.
-#
-
-source [file join [file dirname [info script]] fts5_common.tcl]
-set testprefix fts5contentless5
-
-# If SQLITE_ENABLE_FTS5 is defined, omit this file.
-ifcapable !fts5 {
-  finish_test
-  return
-}
-
-do_execsql_test 1.0 {
-  CREATE VIRTUAL TABLE t1 USING fts5(a, b, c, content='', contentless_delete=1);
-  INSERT INTO t1 VALUES('A', 'B', 'C');
-  INSERT INTO t1 VALUES('D', 'E', 'F');
-  INSERT INTO t1 VALUES('G', 'H', 'I');
-}
-
-do_execsql_test 1.01 {
-  CREATE TABLE t2(x, y);
-  INSERT INTO t2 VALUES('x', 'y');
-}
-
-# explain_i "UPDATE t1 SET a='a' WHERE t1.rowid=1"    
-breakpoint
-explain_i "UPDATE t1 SET a='a' FROM t2 WHERE t1.rowid=1 AND b IS NULL"     
-
-#breakpoint
-#explain_i "UPDATE t1 SET a='a' WHERE b IS NULL AND rowid=?"
-
-foreach {tn up err} {
-  1   "UPDATE t1 SET a='a', b='b', c='c' WHERE rowid=1"                  0
-  2   "UPDATE t1 SET a='a', b='b'        WHERE rowid=1"                  1
-  3   "UPDATE t1 SET        b='b', c='c' WHERE rowid=1"                  1
-  4   "UPDATE t1 SET a='a',        c='c' WHERE rowid=1"                  1
-  5   "UPDATE t1 SET a='a',        c='c' WHERE t1.rowid=1 AND b IS NULL" 1
-  6   "UPDATE t1 SET a='a' FROM t2 WHERE t1.rowid=1"                     1
-  7   "UPDATE t1 SET a='a', b='b', c='c' FROM t2 WHERE t1.rowid=1"       0
-} {
-
-  set res(0) {0 {}}
-  set res(1) {1 {cannot UPDATE a subset of columns on fts5 contentless-delete table: t1}}
-  do_catchsql_test 1.$tn $up $res($err)
-}
-
-finish_test
@@ -48,10 +48,6 @@ do_test 1.3 {
  }
  catchsql { INSERT INTO t1(t1) VALUES('integrity-check') }
 } {1 {database disk image is malformed}}
-do_execsql_test 1.3b {
-  PRAGMA integrity_check(t1);
-} {{malformed inverted index for FTS5 table main.t1}}
-

 do_test 1.4 {
  db_restore_and_reopen
@@ -167,9 +167,6 @@ foreach {tn hdr} {
      do_test 3.$tn.$tn2.2 {
        catchsql { INSERT INTO x3(x3) VALUES('integrity-check') }
      } {1 {database disk image is malformed}}
-      do_execsql_test 3.$tn.$tn2.3 {
-        PRAGMA integrity_check(x3);
-      } {{malformed inverted index for FTS5 table main.x3}}
    }

    execsql ROLLBACK
@@ -95,9 +95,6 @@ do_execsql_test 3.3 {
  SELECT rowid, bm25(e1) FROM e1 WHERE e1 MATCH '"/" OR "just"' ORDER BY rank;
 } {1 -1e-06}

-do_execsql_test 3.4 "
-  SELECT fts5_expr_tcl('e AND \" \"');
-" {{AND [nearset -- {e}] [{}]}}


 finish_test
@@ -44,12 +44,12 @@ do_catchsql_test 1.2.2 {

 do_catchsql_test 1.3.1 { 
  SELECT highlight(t1, 4, '<b>', '</b>') FROM t1('*reads'); 
-} {1 {no such cursor: 2}}
+} {1 {no such cursor: 1}}

 do_catchsql_test 1.3.2 {
  SELECT a FROM t1
    WHERE rank = (SELECT highlight(t1, 4, '<b>', '</b>') FROM t1('*reads'));
-} {1 {no such cursor: 2}}
+} {1 {no such cursor: 1}}

 db close
 sqlite3 db test.db
@@ -9,7 +9,7 @@
 #
 #***********************************************************************
 #
-# TESTRUNNER: superslow
+# TESTRUNNER: slow
 #

 source [file join [file dirname [info script]] fts5_common.tcl]
@@ -42,4 +42,23 @@ do_execsql_test 1.2 {
  SELECT count(*) FROM t1('mno')
 } $nLoop

+do_execsql_test 2.0 {
+  CREATE VIRTUAL TABLE t2 USING fts5(x);
+  INSERT INTO t2(t2, rank) VALUES('pgsz', 32);
+}
+
+do_test 2.1 {
+  for {set ii 0} {$ii < $nLoop} {incr ii} {
+    execsql {
+      INSERT INTO t2 VALUES('abc def ghi');
+      INSERT INTO t2 VALUES('jkl mno pqr');
+      INSERT INTO t2(t2, rank) VALUES('merge', -1);
+    }
+  }
+} {}
+
+do_execsql_test 2.2 {
+  SELECT count(*) FROM t2('mno')
+} $nLoop
+
 finish_test
@@ -1,45 +0,0 @@
-# 2023 Aug 27
-#
-# The author disclaims copyright to this source code.  In place of
-# a legal notice, here is a blessing:
-#
-#    May you do good and not evil.
-#    May you find forgiveness for yourself and forgive others.
-#    May you share freely, never taking more than you give.
-#
-#***********************************************************************
-#
-# TESTRUNNER: superslow
-#
-
-source [file join [file dirname [info script]] fts5_common.tcl]
-set testprefix fts5optimize2
-
-# If SQLITE_ENABLE_FTS5 is defined, omit this file.
-ifcapable !fts5 {
-  finish_test
-  return
-}
-
-set nLoop 2500
-
-do_execsql_test 1.0 {
-  CREATE VIRTUAL TABLE t2 USING fts5(x);
-  INSERT INTO t2(t2, rank) VALUES('pgsz', 32);
-}
-
-do_test 1.1 {
-  for {set ii 0} {$ii < $nLoop} {incr ii} {
-    execsql {
-      INSERT INTO t2 VALUES('abc def ghi');
-      INSERT INTO t2 VALUES('jkl mno pqr');
-      INSERT INTO t2(t2, rank) VALUES('merge', -1);
-    }
-  }
-} {}
-
-do_execsql_test 1.2 {
-  SELECT count(*) FROM t2('mno')
-} $nLoop
-
-finish_test
@@ -180,28 +180,4 @@ do_execsql_test 6.1 {
  {table table table} {the table names.} {rank on an fts5 table}
 }

-
-#-------------------------------------------------------------------------
-# forum post: https://sqlite.org/forum/forumpost/a2dd636330
-#
-reset_db
-do_execsql_test 1.0 {
-  CREATE VIRTUAL TABLE t USING fts5 (a, b);  
-  INSERT INTO t (a, b) VALUES ('data1', 'sentence1'), ('data2', 'sentence2'); 
-  INSERT INTO t(t, rank) VALUES ('rank', 'bm25(10.0,1.0)');
-}
-
-sqlite3 db2 test.db 
-do_execsql_test -db db2 1.1 {
-  SELECT *, rank<0.0 FROM t('data*') ORDER BY RANK;
-} {data1 sentence1 1 data2 sentence2 1}
-
-do_execsql_test 1.2 {
-  INSERT INTO t(t, rank) VALUES ('rank', 'bm25(10.0,1.0)');
-}
-do_execsql_test -db db2 1.3 {
-  SELECT *, rank<0.0 FROM t('data*') ORDER BY RANK;
-} {data1 sentence1 1 data2 sentence2 1}
-db2 close
-
 finish_test
@@ -273,76 +273,6 @@ do_execsql_test 5.3 {
 do_execsql_test 5.4 { SELECT rowid FROM t1('abc'); } 2
 do_execsql_test 5.5 { SELECT rowid FROM t1('aa'); } 2

-#-------------------------------------------------------------------------
-# Tests for the bug fixed by https://sqlite.org/src/info/4b60a1c3
-#
-reset_db
-do_execsql_test 6.0 {
-  CREATE VIRTUAL TABLE fts USING fts5(content);
-  INSERT INTO fts(fts, rank) VALUES ('secure-delete', 1);
-  INSERT INTO fts(rowid, content) VALUES
-    (3407, 'profile profile profile profile profile profile profile profile pull pulling pulling really');
-  DELETE FROM fts WHERE rowid IS 3407;
-  INSERT INTO fts(fts) VALUES ('integrity-check');
-}
-
-foreach {tn detail} {
-  1 full
-  2 column
-  3 none
-} {
-  do_execsql_test 6.1.$detail "
-    DROP TABLE IF EXISTS t1;
-    CREATE VIRTUAL TABLE t1 USING fts5(x, detail=$detail);
-  "
-
-  do_execsql_test 6.2.$detail {
-    INSERT INTO t1(t1, rank) VALUES('secure-delete', 1);
-  }
-
-  for {set ii 1} {$ii < 100} {incr ii} {
-    do_execsql_test 6.3.$detail.$ii.1 {
-      BEGIN;
-        INSERT INTO t1(rowid, x) VALUES(10, 'word1');
-        WITH s(i) AS (
-          SELECT 1 UNION ALL SELECT i+1 FROM s WHERE i<CAST($ii AS integer)
-        )
-        INSERT INTO t1(x) SELECT 'word3' FROM s;
-      COMMIT;
-      INSERT INTO t1(t1) VALUES('optimize');
-    }
-
-    do_execsql_test 6.3.$detail.$ii.2 {
-      DELETE FROM t1 WHERE rowid=10;
-      INSERT INTO t1(t1) VALUES ('integrity-check');
-    }
-
-    do_execsql_test 6.3.$detail.$ii.3 {
-      DELETE FROM t1;
-    }
-
-    do_execsql_test 6.3.$detail.$ii.4 {
-      BEGIN;
-        INSERT INTO t1(rowid, x) VALUES(10, 'tokenA');
-        WITH s(i) AS (
-          SELECT 1 UNION ALL SELECT i+1 FROM s WHERE i<CAST($ii AS integer)
-        )
-        INSERT INTO t1(x) SELECT group_concat('tokenB ') FROM s;
-      COMMIT;
-      INSERT INTO t1(t1) VALUES('optimize');
-    }
-
-    do_execsql_test 6.3.$detail.$ii.5 {
-      DELETE FROM t1 WHERE rowid=10;
-      INSERT INTO t1(t1) VALUES ('integrity-check');
-    }
-
-    do_execsql_test 6.3.$detail.$ii.6 {
-      DELETE FROM t1;
-    }
-  }
-}
-

 finish_test

@@ -50,46 +50,6 @@ do_test 1.3 {
  expr $phc(1)*5 < $phc(2)
 } {1}

-#-------------------------------------------------------------------------
-reset_db
-
-do_execsql_test 2.0 {
-  CREATE VIRTUAL TABLE t1 USING fts5(x);
-  INSERT INTO t1(t1, rank) VALUES('secure-delete', $sd) 
-}
-
-do_execsql_test 2.1 {
-  BEGIN;
-    INSERT INTO t1(rowid, x) VALUES(-100000, 'abc def ghi');
-    INSERT INTO t1(rowid, x) VALUES(-99999, 'abc def ghi');
-    INSERT INTO t1(rowid, x) VALUES(9223372036854775800, 'abc def ghi');
-  COMMIT;
-}
-
-do_execsql_test 2.2 {
-  SELECT rowid FROM t1('def')
-} {-100000 -99999 9223372036854775800}
-
-#-------------------------------------------------------------------------
-reset_db
-
-do_execsql_test 2.0 {
-  CREATE VIRTUAL TABLE t1 USING fts5(x);
-  INSERT INTO t1(t1, rank) VALUES('secure-delete', $sd) 
-}
-
-do_execsql_test 2.1 {
-  BEGIN;
-    INSERT INTO t1(rowid, x) 
-      VALUES(51869, 'when whenever where weress what turn'), 
-            (51871, 'to were');
-  COMMIT;
-}
-
-do_execsql_test 3.2 {
-  DELETE FROM t1 WHERE rowid=51871;
-  INSERT INTO t1(t1) VALUES('integrity-check');
-}

 finish_test

@@ -1,116 +0,0 @@
-# 2023 Feb 17
-#
-# The author disclaims copyright to this source code.  In place of
-# a legal notice, here is a blessing:
-#
-#    May you do good and not evil.
-#    May you find forgiveness for yourself and forgive others.
-#    May you share freely, never taking more than you give.
-#
-#*************************************************************************
-#
-# TESTRUNNER: slow
-#
-
-source [file join [file dirname [info script]] fts5_common.tcl]
-ifcapable !fts5 { finish_test ; return }
-set ::testprefix fts5secure7
-
-
-set NVOCAB 500
-set NDOC [expr 1000]
-
-set NREP 100
-set nDeletePerRep [expr 5]
-
-set VOCAB [list]
-
-proc select_one {list} {
-  set n [llength $list]
-  lindex $list [expr {abs(int(rand()*$n))}]
-}
-
-proc init_vocab {} {
-  set L [split "abcdefghijklmnopqrstuvwxyz" {}]
-  set nL [llength $L]
-  for {set i 0} {$i < $::NVOCAB} {incr i} {
-    set n [expr {6 + int(rand()*8)}]
-    set word ""
-    for {set j 0} {$j < $n} {incr j} {
-      append word [select_one $L]
-    }
-    lappend ::VOCAB $word
-  }
-}
-
-proc get_word {} {
-  select_one $::VOCAB
-}
-
-proc get_document {nWord} {
-  set ret [list]
-  for {set i 0} {$i < $nWord} {incr i} {
-    lappend ret [get_word]
-  }
-  return $ret
-}
-
-init_vocab
-
-db func document [list get_document 12]
-
-do_execsql_test 1.0 {
-  CREATE VIRTUAL TABLE t1 USING fts5(body);
-  INSERT INTO t1(t1, rank) VALUES('secure-delete', 1);
-}
-do_execsql_test 1.1 {
-  WITH s(i) AS (
-    SELECT 1 UNION ALL SELECT i+1 FROM s WHERE i<$NDOC
-  )
-  INSERT INTO t1 SELECT document() FROM s;
-}
-
-for {set iRep 0} {$iRep < $NREP} {incr iRep} {
-  set lRowid [db eval {SELECT rowid FROM t1}]
-  for {set iDel 0} {$iDel < $nDeletePerRep} {incr iDel} {
-    set idx [select_one $lRowid]
-    db eval {
-      DELETE FROM t1 WHERE rowid=$idx
-    }
-  }
-  db eval {
-    WITH s(i) AS (
-      SELECT 1 UNION ALL SELECT i+1 FROM s WHERE i<$nDeletePerRep
-    )
-    INSERT INTO t1 SELECT document() FROM s;
-  }
-  do_execsql_test 1.2.$iRep {
-    INSERT INTO t1(t1) VALUES('integrity-check');
-  }
-}
-
-reset_db
-db func document [list get_document 12]
-do_execsql_test 2.0 {
-  CREATE VIRTUAL TABLE t1 USING fts5(body);
-  INSERT INTO t1(t1, rank) VALUES('secure-delete', 1);
-  INSERT INTO t1(t1, rank) VALUES('pgsz', 128);
-}
-do_execsql_test 2.1 {
-  WITH s(i) AS (
-    SELECT 1 UNION ALL SELECT i+1 FROM s WHERE i<$NDOC
-  )
-  INSERT INTO t1 SELECT document() FROM s;
-}
-for {set ii 0} {$ii < $NDOC} {incr ii} {
-  set lRowid [db eval {SELECT rowid FROM t1}]
-  set idx [select_one $lRowid]
-  db eval { DELETE FROM t1 WHERE rowid=$idx }
-  do_execsql_test 2.2.$ii {
-    INSERT INTO t1(t1) VALUES('integrity-check');
-  }
-}
-
-finish_test
-
-
@@ -122,9 +122,6 @@ foreach {tn expr} {
  4.1 "NEAR(one two, 2)"
  4.2 "NEAR(one two three, 2)"
  4.3 "NEAR(eight nine, 1) OR NEAR(six seven, 1)"
-
-  5.1 "one + two"
-  5.2 "1 + two"
 } {
  if {[fts5_expr_ok $expr ss]==0} {
    do_test 1.$tok.$tn.OMITTED { list } [list]
@@ -1,470 +0,0 @@
-# Quick-and-dirty makefile to bootstrap the sqlite3-jni project.  This
-# build assumes a Linux-like system.
-default: all
-
-JAVA_HOME ?= $(HOME)/jdk/current
-# e.g. /usr/lib/jvm/default-javajava-19-openjdk-amd64
-JDK_HOME ?= $(JAVA_HOME)
-# ^^^ JDK_HOME is not as widely used as JAVA_HOME
-bin.jar     := $(JDK_HOME)/bin/jar
-bin.java    := $(JDK_HOME)/bin/java
-bin.javac   := $(JDK_HOME)/bin/javac
-bin.javadoc := $(JDK_HOME)/bin/javadoc
-ifeq (,$(wildcard $(JDK_HOME)))
-$(error set JDK_HOME to the top-most dir of your JDK installation.)
-endif
-MAKEFILE := $(lastword $(MAKEFILE_LIST))
-$(MAKEFILE):
-
-package.jar := sqlite3-jni.jar
-
-dir.top     := ../..
-dir.tool    := ../../tool
-dir.jni     := $(patsubst %/,%,$(dir $(MAKEFILE)))
-dir.src     := $(dir.jni)/src
-dir.src.c   := $(dir.src)/c
-dir.bld     := $(dir.jni)/bld
-dir.bld.c   := $(dir.bld)
-dir.src.jni := $(dir.src)/org/sqlite/jni
-dir.src.jni.tester := $(dir.src.jni)/tester
-dir.src.fts5 := $(dir.src.jni)/fts5
-mkdir       ?= mkdir -p
-$(dir.bld.c):
-	$(mkdir) $@
-
-javac.flags ?= -Xlint:unchecked -Xlint:deprecation
-java.flags ?=
-jnicheck ?= 1
-ifeq (1,$(jnicheck))
-  java.flags += -Xcheck:jni
-endif
-
-classpath := $(dir.src)
-CLEAN_FILES := $(package.jar)
-DISTCLEAN_FILES := $(dir.jni)/*~ $(dir.src.c)/*~ $(dir.src.jni)/*~
-
-sqlite3-jni.h := $(dir.src.c)/sqlite3-jni.h
-.NOTPARALLEL: $(sqlite3-jni.h)
-SQLite3Jni.java := src/org/sqlite/jni/SQLite3Jni.java
-SQLTester.java := src/org/sqlite/jni/tester/SQLTester.java
-SQLite3Jni.class := $(SQLite3Jni.java:.java=.class)
-SQLTester.class := $(SQLTester.java:.java=.class)
-
-########################################################################
-# The future of FTS5 customization in this API is as yet unclear.
-# The pieces are all in place, and are all thin proxies so not much
-# complexity, but some semantic changes were required in porting
-# which are largely untested.
-#
-# Reminder: this flag influences the contents of $(sqlite3-jni.h),
-# which is checked in. Please do not check in changes to that file in
-# which the fts5 APIs have been stripped unless that feature is
-# intended to be stripped for good.
-enable.fts5 ?= 0
-# If enable.tester is 0, the org/sqlite/jni/tester/* bits are elided.
-enable.tester ?= $(if $(wildcard $(dir.src.jni.tester)/SQLTester.java),1,0)
-
-# bin.version-info = binary to output various sqlite3 version info
-# building the distribution zip file.
-bin.version-info := $(dir.top)/version-info
-.NOTPARALLEL: $(bin.version-info)
-$(bin.version-info): $(dir.tool)/version-info.c $(sqlite3.h) $(dir.top)/Makefile
-	$(MAKE) -C $(dir.top) version-info
-
-# Be explicit about which Java files to compile so that we can work on
-# in-progress files without requiring them to be in a compilable statae.
-JAVA_FILES.main := $(patsubst %,$(dir.src.jni)/%,\
-  annotation/Canonical.java \
-  annotation/NotNull.java \
-  annotation/Nullable.java \
-  AbstractCollationCallback.java \
-  AggregateFunction.java \
-  AuthorizerCallback.java \
-  AutoExtensionCallback.java \
-  BusyHandlerCallback.java \
-  CollationCallback.java \
-  CollationNeededCallback.java \
-  CommitHookCallback.java \
-  ConfigLogCallback.java \
-  ConfigSqllogCallback.java \
-  NativePointerHolder.java \
-  OutputPointer.java \
-  PrepareMultiCallback.java \
-  PreupdateHookCallback.java \
-  ProgressHandlerCallback.java \
-  ResultCode.java \
-  RollbackHookCallback.java \
-  ScalarFunction.java \
-  SQLFunction.java \
-  CallbackProxy.java \
-  SQLite3Jni.java \
-  TableColumnMetadata.java \
-  TraceV2Callback.java \
-  UpdateHookCallback.java \
-  WindowFunction.java \
-  XDestroyCallback.java \
-  sqlite3.java \
-  sqlite3_context.java \
-  sqlite3_stmt.java \
-  sqlite3_value.java \
-)
-JAVA_FILES.unittest := $(patsubst %,$(dir.src.jni)/%,\
-  Tester1.java \
-)
-ifeq (1,$(enable.fts5))
-  JAVA_FILES.main += $(patsubst %,$(dir.src.fts5)/%,\
-    fts5_api.java \
-    fts5_extension_function.java \
-    fts5_tokenizer.java \
-    Fts5.java \
-    Fts5Context.java \
-    Fts5ExtensionApi.java \
-    Fts5PhraseIter.java \
-    Fts5Tokenizer.java \
-    TesterFts5.java \
-  )
-endif
-JAVA_FILES.tester := $(dir.src.jni.tester)/SQLTester.java
-JAVA_FILES.package.info := \
-  $(dir.src.jni)/package-info.java \
-  $(dir.src.jni)/annotation/package-info.java
-
-CLASS_FILES.main := $(JAVA_FILES.main:.java=.class)
-CLASS_FILES.unittest := $(JAVA_FILES.unittest:.java=.class)
-CLASS_FILES.tester := $(JAVA_FILES.tester:.java=.class)
-
-JAVA_FILES += $(JAVA_FILES.main) $(JAVA_FILES.unittest)
-ifeq (1,$(enable.tester))
-  JAVA_FILES += $(JAVA_FILES.tester)
-endif
-
-CLASS_FILES :=
-define CLASSFILE_DEPS
-all: $(1).class
-CLASS_FILES += $(1).class
-endef
-$(foreach B,$(basename \
-  $(JAVA_FILES.main) $(JAVA_FILES.unittest) $(JAVA_FILES.tester)),\
-  $(eval $(call CLASSFILE_DEPS,$(B))))
-$(CLASS_FILES): $(JAVA_FILES) $(MAKEFILE)
-	$(bin.javac) $(javac.flags) -h $(dir.bld.c) -cp $(classpath) $(JAVA_FILES)
-
-#.PHONY: classfiles
-
-########################################################################
-# Set up sqlite3.c and sqlite3.h...
-#
-# To build with SEE (https://sqlite.org/see), either put sqlite3-see.c
-# in the top of this build tree or pass
-# sqlite3.c=PATH_TO_sqlite3-see.c to the build. Note that only
-# encryption modules with no 3rd-party dependencies will currently
-# work here: AES256-OFB, AES128-OFB, and AES128-CCM. Not
-# coincidentally, those 3 modules are included in the sqlite3-see.c
-# bundle.
-#
-# A custom sqlite3.c must not have any spaces in its name.
-# $(sqlite3.canonical.c) must point to the sqlite3.c in
-# the sqlite3 canonical source tree, as that source file
-# is required for certain utility and test code.
-sqlite3.canonical.c := $(firstword $(wildcard $(dir.src.c)/sqlite3.c) $(dir.top)/sqlite3.c)
-sqlite3.canonical.h := $(firstword $(wildcard $(dir.src.c)/sqlite3.h) $(dir.top)/sqlite3.h)
-sqlite3.c := $(sqlite3.canonical.c)
-sqlite3.h := $(sqlite3.canonical.h)
-#ifeq (,$(shell grep sqlite3_activate_see $(sqlite3.c) 2>/dev/null))
-#  SQLITE_C_IS_SEE := 0
-#else
-#  SQLITE_C_IS_SEE := 1
-#  $(info This is an SEE build.)
-#endif
-
-.NOTPARALLEL: $(sqlite3.h)
-$(sqlite3.h):
-	$(MAKE) -C $(dir.top) sqlite3.c
-$(sqlite3.c): $(sqlite3.h)
-
-opt.threadsafe ?= 1
-opt.fatal-oom ?= 1
-opt.debug ?= 1
-opt.metrics ?= 1
-SQLITE_OPT = \
-  -DSQLITE_ENABLE_RTREE \
-  -DSQLITE_ENABLE_EXPLAIN_COMMENTS \
-  -DSQLITE_ENABLE_STMTVTAB \
-  -DSQLITE_ENABLE_DBPAGE_VTAB \
-  -DSQLITE_ENABLE_DBSTAT_VTAB \
-  -DSQLITE_ENABLE_BYTECODE_VTAB \
-  -DSQLITE_ENABLE_OFFSET_SQL_FUNC \
-  -DSQLITE_ENABLE_PREUPDATE_HOOK \
-  -DSQLITE_ENABLE_SQLLOG \
-  -DSQLITE_OMIT_LOAD_EXTENSION \
-  -DSQLITE_OMIT_DEPRECATED \
-  -DSQLITE_OMIT_SHARED_CACHE \
-  -DSQLITE_THREADSAFE=$(opt.threadsafe) \
-  -DSQLITE_TEMP_STORE=2 \
-  -DSQLITE_USE_URI=1 \
-  -DSQLITE_C=$(sqlite3.c) \
-  -DSQLITE_JNI_FATAL_OOM=$(opt.fatal-oom) \
-  -DSQLITE_JNI_ENABLE_METRICS=$(opt.metrics)
-
-ifeq (1,$(opt.debug))
-  SQLITE_OPT += -DSQLITE_DEBUG -g -DDEBUG -UNDEBUG
-else
-  SQLITE_OPT += -O2
-endif
-
-ifeq (1,$(enable.fts5))
-  SQLITE_OPT += -DSQLITE_ENABLE_FTS5
-endif
-
-sqlite3-jni.c := $(dir.src.c)/sqlite3-jni.c
-sqlite3-jni.o := $(dir.bld.c)/sqlite3-jni.o
-sqlite3-jni.h   := $(dir.src.c)/sqlite3-jni.h
-package.dll := $(dir.bld.c)/libsqlite3-jni.so
-# All javac-generated .h files must be listed in $(sqlite3-jni.h.in):
-sqlite3-jni.h.in :=
-# $(java.with.jni) lists all Java files which contain JNI decls:
-java.with.jni :=
-define ADD_JNI_H
-sqlite3-jni.h.in += $$(dir.bld.c)/org_sqlite_jni$(3)_$(2).h
-java.with.jni += $(1)/$(2).java
-$$(dir.bld.c)/org_sqlite_jni$(3)_$(2).h: $(1)/$(2).java
-endef
-# Invoke ADD_JNI_H once for each Java file which includes JNI
-# declarations:
-$(eval $(call ADD_JNI_H,$(dir.src.jni),SQLite3Jni,))
-ifeq (1,$(enable.fts5))
- $(eval $(call ADD_JNI_H,$(dir.src.fts5),Fts5ExtensionApi,_fts5))
- $(eval $(call ADD_JNI_H,$(dir.src.fts5),fts5_api,_fts5))
- $(eval $(call ADD_JNI_H,$(dir.src.fts5),fts5_tokenizer,_fts5))
-endif
-ifeq (1,$(enable.tester))
-  $(eval $(call ADD_JNI_H,$(dir.src.jni.tester),SQLTester,_tester))
-endif
-$(sqlite3-jni.h.in): $(dir.bld.c)
-
-#package.dll.cfiles :=
-package.dll.cflags = \
-  -fPIC \
-  -I. \
-  -I$(dir $(sqlite3.h)) \
-  -I$(dir.src.c) \
-  -I$(JDK_HOME)/include \
-  $(patsubst %,-I%,$(patsubst %.h,,$(wildcard $(JDK_HOME)/include/*))) \
-  -Wall
-# Using (-Wall -Wextra) triggers an untennable number of
-# gcc warnings from sqlite3.c for mundane things like
-# unused parameters.
-#
-# The gross $(patsubst...) above is to include the platform-specific
-# subdir which lives under $(JDK_HOME)/include and is a required
-# include path for client-level code.
-########################################################################
-ifeq (1,$(enable.tester))
-  package.dll.cflags += -DSQLITE_JNI_ENABLE_SQLTester
-endif
-$(sqlite3-jni.h): $(sqlite3-jni.h.in) $(MAKEFILE)
-	@cat $(sqlite3-jni.h.in) > $@.tmp
-	@if cmp $@ $@.tmp >/dev/null; then \
-		rm -f $@.tmp; \
-		echo "$@ not modified"; \
-	else \
-		mv $@.tmp $@; \
-		echo "Updated $@"; \
-	fi
-	@if [ x1 != x$(enable.fts5) ]; then \
-		echo "*** REMINDER:"; \
-		echo "*** enable.fts5=0, so please do not check in changes to $@."; \
-	fi
-
-$(package.dll): $(sqlite3-jni.h) $(sqlite3.c) $(sqlite3.h)
-$(package.dll): $(sqlite3-jni.c) $(MAKEFILE)
-	$(CC) $(package.dll.cflags) $(SQLITE_OPT) \
-			$(sqlite3-jni.c) -shared -o $@
-all: $(package.dll)
-
-.PHONY: test test-one
-test.flags ?=
-test.main.flags = -ea -Djava.library.path=$(dir.bld.c) \
-                  $(java.flags) -cp $(classpath) \
-                  org.sqlite.jni.Tester1
-test.deps := $(CLASS_FILES) $(package.dll)
-test-one: $(test.deps)
-	$(bin.java) $(test.main.flags) $(test.flags)
-test-sqllog: $(test.deps)
-	@echo "Testing with -sqllog..."
-	$(bin.java) $(test.main.flags) -sqllog
-test-mt: $(test.deps)
-	@echo "Testing in multi-threaded mode:";
-	$(bin.java) $(test.main.flags) -t 7 -r 50 -shuffle $(test.flags)
-
-test: test-one test-mt
-tests: test test-sqllog
-
-tester.scripts := $(sort $(wildcard $(dir.src)/tests/*.test))
-tester.flags ?= # --verbose
-.PHONY: tester tester-local tester-ext
-ifeq (1,$(enable.tester))
-tester-local: $(CLASS_FILES.tester) $(package.dll)
-	$(bin.java) -ea -Djava.library.path=$(dir.bld.c) \
-		$(java.flags) -cp $(classpath) \
-		org.sqlite.jni.tester.SQLTester $(tester.flags) $(tester.scripts)
-tester: tester-local
-else
-tester:
-	@echo "SQLTester support is disabled. Build with enable.tester=1 to enable it."
-endif
-
-tester.extdir.default := src/tests/ext
-tester.extdir ?= $(tester.extdir.default)
-tester.extern-scripts := $(wildcard $(tester.extdir)/*.test)
-ifneq (,$(tester.extern-scripts))
-tester-ext:
-	$(bin.java) -ea -Djava.library.path=$(dir.bld.c) \
-		$(java.flags) -cp $(classpath) \
-		org.sqlite.jni.tester.SQLTester $(tester.flags) $(tester.extern-scripts)
-else
-tester-ext:
-	@echo "******************************************************"; \
-		echo "*** Include the out-of-tree test suite in the 'tester'"; \
-		echo "*** target by either symlinking its directory to"; \
-		echo "*** $(tester.extdir.default) or passing it to make"; \
-		echo "*** as tester.extdir=/path/to/that/dir."; \
-		echo "******************************************************";
-endif
-
-tester-ext: tester-local
-tester: tester-ext
-tests: tester
-########################################################################
-# Build each SQLITE_THREADMODE variant and run all tests against them.
-multitest: clean
-define MULTIOPT
-multitest: multitest-$(1)
-multitest-$(1):
-	$$(MAKE) opt.debug=$$(opt.debug) $(patsubst %,opt.%,$(2)) \
-		tests clean enable.fts5=1
-endef
-
-$(eval $(call MULTIOPT,01,threadsafe=0 oom=1))
-$(eval $(call MULTIOPT,00,threadsafe=0 oom=0))
-$(eval $(call MULTIOPT,11,threadsafe=1 oom=1))
-$(eval $(call MULTIOPT,10,threadsafe=1 oom=0))
-$(eval $(call MULTIOPT,21,threadsafe=2 oom=1))
-$(eval $(call MULTIOPT,20,threadsafe=2 oom=0))
-
-
-########################################################################
-# jar bundle...
-package.jar.in := $(abspath $(dir.src)/jar.in)
-CLEAN_FILES += $(package.jar.in)
-JAVA_FILES.jar := $(JAVA_FILES.main) $(JAVA_FILES.unittest) $(JAVA_FILES.package.info)
-CLASS_FILES.jar := $(filter-out %/package-info.class,$(JAVA_FILES.jar:.java=.class))
-$(package.jar.in): $(package.dll) $(MAKEFILE)
-	ls -1 \
-		$(dir.src.jni)/*.java $(dir.src.jni)/*.class \
-		$(dir.src.jni)/annotation/*.java $(dir.src.jni)/annotation/*.class \
-	| sed -e 's,^$(dir.src)/,,' | sort > $@
-
-$(package.jar): $(CLASS_FILES.jar) $(MAKEFILE) $(package.jar.in)
-	@rm -f $(dir.src)/c/*~ $(dir.src.jni)/*~
-	cd $(dir.src); $(bin.jar) -cfe ../$@ org.sqlite.jni.Tester1 @$(package.jar.in)
-	@ls -la $@
-	@echo "To use this jar you will need the -Djava.library.path=DIR/CONTAINING/libsqlite3-jni.so flag."
-	@echo "e.g. java -Djava.library.path=bld -jar $@"
-
-jar: $(package.jar)
-run-jar: $(package.jar) $(package.dll)
-	$(bin.java) -Djava.library.path=$(dir.bld) -jar $(package.jar) $(run-jar.flags)
-
-########################################################################
-# javadoc...
-dir.doc   := $(dir.jni)/javadoc
-doc.index := $(dir.doc)/index.html
-javadoc.exclude := -exclude org.sqlite.jni.tester
-ifneq (1,$(enable.fts5))
-  javadoc.exclude += -exclude org.sqlite.jni.fts5
-endif
-$(doc.index): $(JAVA_FILES.main) $(MAKEFILE)
-	@if [ -d $(dir.doc) ]; then rm -fr $(dir.doc)/*; fi
-	$(bin.javadoc) -cp $(classpath) -d $(dir.doc) -quiet \
-		-subpackages org.sqlite.jni $(javadoc.exclude)
-	@echo "javadoc output is in $@"
-
-.PHONY: doc javadoc docserve
-.FORCE: doc
-doc: $(doc.index)
-javadoc: $(doc.index)
-# Force rebild of docs
-redoc:
-	@rm -f $(doc.index)
-	@$(MAKE) doc
-docserve: $(doc.index)
-	cd $(dir.doc) && althttpd -max-age 1 -page index.html
-########################################################################
-# Clean up...
-CLEAN_FILES += $(dir.bld.c)/* \
-  $(dir.src.jni)/*.class \
-  $(dir.src.jni.tester)/*.class \
-  $(package.dll) \
-  hs_err_pid*.log
-
-.PHONY: clean distclean
-clean:
-	-rm -f $(CLEAN_FILES)
-distclean: clean
-	-rm -f $(DISTCLEAN_FILES)
-	-rm -fr $(dir.bld.c) $(dir.doc)
-
-########################################################################
-# disttribution bundle rules...
-
-ifeq (,$(filter snapshot,$(MAKECMDGOALS)))
-dist-name-prefix := sqlite-jni
-else
-dist-name-prefix := sqlite-jni-snapshot-$(shell /usr/bin/date +%Y%m%d)
-endif
-dist-name := $(dist-name-prefix)-TEMP
-
-
-dist-dir.top := $(dist-name)
-dist-dir.src := $(dist-dir.top)/src
-dist.top.extras := \
-  README.md
-
-.PHONY: dist snapshot
-
-dist: \
-    $(bin.version-info) $(sqlite3.canonical.c) \
-    $(package.jar) $(MAKEFILE)
-	@echo "Making end-user deliverables..."
-	@echo "****************************************************************************"; \
-	echo  "*** WARNING: be sure to build this with JDK8 (javac 1.8) for compatibility."; \
-	echo  "*** reasons!"; $$($(bin.javac) -version); \
-	echo  "****************************************************************************"
-	@rm -fr $(dist-dir.top)
-	@mkdir -p $(dist-dir.src)
-	@cp -p $(dist.top.extras) $(dist-dir.top)/.
-	@cp -p jar-dist.make $(dist-dir.top)/Makefile
-	@cp -p $(dir.src.c)/*.[ch] $(dist-dir.src)/.
-	@cp -p $(sqlite3.canonical.c) $(sqlite3.canonical.h) $(dist-dir.src)/.
-	@set -e; \
-		vnum=$$($(bin.version-info) --download-version); \
-		vjar=$$($(bin.version-info) --version); \
-		vdir=$(dist-name-prefix)-$$vnum; \
-		arczip=$$vdir.zip; \
-		cp -p $(package.jar) $(dist-dir.top)/sqlite3-jni-$${vjar}.jar; \
-		echo "Making $$arczip ..."; \
-		rm -fr $$arczip $$vdir; \
-		mv $(dist-dir.top) $$vdir; \
-		zip -qr $$arczip $$vdir; \
-		rm -fr $$vdir; \
-		ls -la $$arczip; \
-		set +e; \
-		unzip -lv $$arczip || echo "Missing unzip app? Not fatal."
-
-snapshot: dist
-
-.PHONY: dist-clean
-clean: dist-clean
-dist-clean:
-	rm -fr $(dist-name) $(wildcard sqlite-jni-*.zip)
@@ -1,313 +0,0 @@
-SQLite3 via JNI
-========================================================================
-
-This directory houses a Java Native Interface (JNI) binding for the
-sqlite3 API. If you are reading this from the distribution ZIP file,
-links to resources in the canonical source tree will note work. The
-canonical copy of this file can be browsed at:
-
-  <https://sqlite.org/src/doc/trunk/ext/jni/README.md>
-
-Technical support is available in the forum:
-
-  <https://sqlite.org/forum>
-
-
-> **FOREWARNING:** this subproject is very much in development and
-  subject to any number of changes. Please do not rely on any
-  information about its API until this disclaimer is removed.  The JNI
-  bindings released with version 3.43 are a "tech preview" and 3.44
-  will be "final," at which point strong backward compatibility
-  guarantees will apply.
-
-Project goals/requirements:
-
- A [1-to-1(-ish) mapping of the C API](#1to1ish) to Java via JNI,
-  insofar as cross-language semantics allow for. A closely-related
-  goal is that [the C documentation](https://sqlite.org/c3ref/intro.html)
-  should be usable as-is, insofar as possible, for the JNI binding.
-
- Support Java as far back as version 8 (2014).
-
- Environment-independent. Should work everywhere both Java
-  and SQLite3 do.
-
- No 3rd-party dependencies beyond the JDK. That includes no
-  build-level dependencies for specific IDEs and toolchains.  We
-  welcome the addition of build files for arbitrary environments
-  insofar as they neither interfere with each other nor become
-  a maintenance burden for the sqlite developers.
-
-Non-goals:
-
- Creation of high-level OO wrapper APIs. Clients are free to create
-  them off of the C-style API.
-
- Support for mixed-mode operation, where client code accesses SQLite
-  both via the Java-side API and the C API via their own native
-  code. In such cases, proxy functionalities (primarily callback
-  handler wrappers of all sorts) may fail because the C-side use of
-  the SQLite APIs will bypass those proxies.
-
-
-Hello World
-----------------------------------------------------------------------
-
-```java
-import org.sqlite.jni.*;
-import static org.sqlite.jni.SQLite3Jni.*;
-
-...
-
-final sqlite3 db = sqlite3_open(":memory:");
-try {
-  final int rc = sqlite3_errcode(db);
-  if( 0 != rc ){
-    if( null != db ){
-      System.out.print("Error opening db: "+sqlite3_errmsg(db));
-    }else{
-      System.out.print("Error opening db: rc="+rc);
-    }
-    ... handle error ...
-  }
-  // ... else use the db ...
-}finally{
-  // ALWAYS close databases using sqlite3_close() or sqlite3_close_v2()
-  // when done with them. All of their active statement handles must
-  // first have been passed to sqlite3_finalize().
-  sqlite3_close_v2(db);
-}
-```
-
-
-Building
-========================================================================
-
-The canonical builds assumes a Linux-like environment and requires:
-
- GNU Make
- A JDK supporting Java 8 or higher
- A modern C compiler. gcc and clang should both work.
-
-Put simply:
-
-```console
-$ export JAVA_HOME=/path/to/jdk/root
-$ make
-$ make test
-$ make clean
-```
-
-The jar distribution can be created with `make jar`, but note that it
-does not contain the binary DLL file. A different DLL is needed for
-each target platform.
-
-
-<a id='1to1ish'></a>
-One-to-One(-ish) Mapping to C
-========================================================================
-
-This JNI binding aims to provide as close to a 1-to-1 experience with
-the C API as cross-language semantics allow. Interface changes are
-necessarily made where cross-language semantics do not allow a 1-to-1,
-and judiciously made where a 1-to-1 mapping would be unduly cumbersome
-to use in Java. In all cases, this binding makes every effort to
-provide semantics compatible with the C API documentation even if the
-interface to those semantics is slightly different.  Any cases which
-deviate from those semantics (either removing or adding semantics) are
-clearly documented.
-
-Where it makes sense to do so for usability, Java-side overloads are
-provided which accept or return data in alternative forms or provide
-sensible default argument values. In all such cases they are thin
-proxies around the corresponding C APIs and do not introduce new
-semantics.
-
-In some very few cases, Java-specific capabilities have been added in
-new APIs, all of which have "_java" somewhere in their names.
-Examples include:
-
- `sqlite3_result_java_object()`
- `sqlite3_column_java_object()`
- `sqlite3_column_java_casted()`
- `sqlite3_value_java_object()`
- `sqlite3_value_java_casted()`
-
-which, as one might surmise, collectively enable the passing of
-arbitrary Java objects from user-defined SQL functions through to the
-caller.
-
-
-Golden Rule: Garbage Collection Cannot Free SQLite Resources
------------------------------------------------------------------------
-
-It is important that all databases and prepared statement handles get
-cleaned up by client code. A database cannot be closed if it has open
-statement handles. `sqlite3_close()` fails if the db cannot be closed
-whereas `sqlite3_close_v2()` recognizes that case and marks the db as
-a "zombie," pending finalization when the library detects that all
-pending statements have been closed. Be aware that Java garbage
-collection _cannot_ close a database or finalize a prepared statement.
-Those things require explicit API calls.
-
-
-Golden Rule #2: _Never_ Throw from Callbacks (Unless...)
------------------------------------------------------------------------
-
-All routines in this API, barring explicitly documented exceptions,
-retain C-like semantics. For example, they are not permitted to throw
-or propagate exceptions and must return error information (if any) via
-result codes or `null`. The only cases where the C-style APIs may
-throw is through client-side misuse, e.g. passing in a null where it
-shouldn't be used. The APIs clearly mark function parameters which
-should not be null, but does not actively defend itself against such
-misuse. Some C-style APIs explicitly accept `null` as a no-op for
-usability's sake, and some of the JNI APIs deliberately return an
-error code, instead of segfaulting, when passed a `null`.
-
-Client-defined callbacks _must never throw exceptions_ unless _very
-explicitly documented_ as being throw-safe. Exceptions are generally
-reserved for higher-level bindings which are constructed to
-specifically deal with them and ensure that they do not leak C-level
-resources. In some cases, callback handlers are permitted to throw, in
-which cases they get translated to C-level result codes and/or
-messages. If a callback which is not permitted to throw throws, its
-exception may trigger debug output but will otherwise be suppressed.
-
-The reason some callbacks are permitted to throw and others not is
-because all such callbacks act as proxies for C function callback
-interfaces and some of those interfaces have no error-reporting
-mechanism. Those which are capable of propagating errors back through
-the library convert exceptions from callbacks into corresponding
-C-level error information. Those which cannot propagate errors
-necessarily suppress any exceptions in order to maintain the C-style
-semantics of the APIs.
-
-
-Unwieldy Constructs are Re-mapped
------------------------------------------------------------------------
-
-Some constructs, when modelled 1-to-1 from C to Java, are unduly
-clumsy to work with in Java because they try to shoehorn C's way of
-doing certain things into Java's wildly different ways. The following
-subsections cover those, starting with a verbose explanation and
-demonstration of where such changes are "really necessary"...
-
-### Custom Collations
-
-A prime example of where interface changes for Java are necessary for
-usability is [registration of a custom
-collation](https://sqlite.org/c3ref/create_collation.html):
-
-```c
-// C:
-int sqlite3_create_collation(sqlite3 * db, const char * name, int eTextRep,
-                             void *pUserData,
-                             int (*xCompare)(void*,int,void const *,int,void const *));
-
-int sqlite3_create_collation_v2(sqlite3 * db, const char * name, int eTextRep,
-                                void *pUserData,
-                                int (*xCompare)(void*,int,void const *,int,void const *),
-                                void (*xDestroy)(void*));
-```
-
-The `pUserData` object is optional client-defined state for the
-`xCompare()` and/or `xDestroy()` callback functions, both of which are
-passed that object as their first argument. That data is passed around
-"externally" in C because that's how C models the world. If we were to
-bind that part as-is to Java, the result would be awkward to use (^Yes,
-we tried this.):
-
-```java
-// Java:
-int sqlite3_create_collation(sqlite3 db, String name, int eTextRep,
-                             Object pUserData, xCompareType xCompare);
-
-int sqlite3_create_collation_v2(sqlite3 db, String name, int eTextRep,
-                                Object pUserData,
-                                xCompareType xCompare, xDestroyType xDestroy);
-```
-
-The awkwardness comes from (A) having two distinctly different objects
-for callbacks and (B) having their internal state provided separately,
-which is ill-fitting in Java. For the sake of usability, C APIs which
-follow that pattern use a slightly different Java interface:
-
-```java
-int sqlite3_create_collation(sqlite3 db, String name, int eTextRep,
-                             SomeCallbackType collation);
-```
-
-Where the `Collation` class has an abstract `call()` method and
-no-op `xDestroy()` method which can be overridden if needed, leading to
-a much more Java-esque usage:
-
-```java
-int rc = sqlite3_create_collation(db, "mycollation", SQLITE_UTF8, new SomeCallbackType(){
-
-  // Required comparison function:
-  @Override public int call(byte[] lhs, byte[] rhs){ ... }
-
-  // Optional finalizer function:
-  @Override public void xDestroy(){ ... }
-
-  // Optional local state:
-  private String localState1 =
-    "This is local state. There are many like it, but this one is mine.";
-  private MyStateType localState2 = new MyStateType();
-  ...
-});
-```
-
-Noting that:
-
- It is possible to bind in call-scope-local state via closures, if
-  desired, as opposed to packing it into the Collation object.
-
- No capabilities of the C API are lost or unduly obscured via the
-  above API reshaping, so power users need not make any compromises.
-
- In the specific example above, `sqlite3_create_collation_v2()`
-  becomes superfluous because the provided interface effectively
-  provides both the v1 and v2 interfaces, the difference being that
-  overriding the `xDestroy()` method effectively gives it v2
-  semantics.
-
-
-### User-defined SQL Functions (a.k.a. UDFs)
-
-The [`sqlite3_create_function()`](https://sqlite.org/c3ref/create_function.html)
-family of APIs make heavy use of function pointers to provide
-client-defined callbacks, necessitating interface changes in the JNI
-binding. The Java API has only one core function-registration function:
-
-```java
-int sqlite3_create_function(sqlite3 db, String funcName, int nArgs,
-                            int encoding, SQLFunction func);
-```
-
-> Design question: does the encoding argument serve any purpose in
-  Java? That's as-yet undetermined. If not, it will be removed.
-
-`SQLFunction` is not used directly, but is instead instantiated via
-one of its three subclasses:
-
- `SQLFunction.Scalar` implements simple scalar functions using but a
-  single callback.
- `SQLFunction.Aggregate` implements aggregate functions using two
-  callbacks.
- `SQLFunction.Window` implements window functions using four
-  callbacks.
-
-Search [`Tester1.java`](/file/ext/jni/src/org/sqlite/jni/Tester1.java) for
-`SQLFunction` for how it's used.
-
-Reminder: see the disclaimer at the top of this document regarding the
-in-flux nature of this API.
-
-### And so on...
-
-Various APIs which accept callbacks, e.g. `sqlite3_trace_v2()` and
-`sqlite3_update_hook()`, use interfaces similar to those shown above.
-Despite the changes in signature, the JNI layer makes every effort to
-provide the same semantics as the C API documentation suggests.
@@ -1,60 +0,0 @@
-#!/this/is/make
-#^^^^ help emacs out
-#
-# This is a POSIX-make-compatible makefile for building the sqlite3
-# JNI library from "dist" zip file. It must be edited to set the
-# proper top-level JDK directory and, depending on the platform, add a
-# platform-specific -I directory. It should build as-is with any
-# 2020s-era version of gcc or clang. It requires JDK version 8 or
-# higher and that JAVA_HOME points to the top-most installation
-# directory of that JDK. On Ubuntu-style systems the JDK is typically
-# installed under /usr/lib/jvm/java-VERSION-PLATFORM.
-
-default: all
-
-JAVA_HOME = /usr/lib/jvm/java-1.8.0-openjdk-amd64
-CFLAGS = \
-  -fPIC \
-  -Isrc \
-  -I$(JAVA_HOME)/include \
-  -I$(JAVA_HOME)/include/linux \
-  -I$(JAVA_HOME)/include/apple \
-  -I$(JAVA_HOME)/include/bsd \
-  -Wall
-
-SQLITE_OPT = \
-  -DSQLITE_ENABLE_RTREE \
-  -DSQLITE_ENABLE_EXPLAIN_COMMENTS \
-  -DSQLITE_ENABLE_STMTVTAB \
-  -DSQLITE_ENABLE_DBPAGE_VTAB \
-  -DSQLITE_ENABLE_DBSTAT_VTAB \
-  -DSQLITE_ENABLE_BYTECODE_VTAB \
-  -DSQLITE_ENABLE_OFFSET_SQL_FUNC \
-  -DSQLITE_OMIT_LOAD_EXTENSION \
-  -DSQLITE_OMIT_DEPRECATED \
-  -DSQLITE_OMIT_SHARED_CACHE \
-  -DSQLITE_THREADSAFE=1 \
-  -DSQLITE_TEMP_STORE=2 \
-  -DSQLITE_USE_URI=1 \
-  -DSQLITE_ENABLE_FTS5 \
-  -DSQLITE_DEBUG
-
-sqlite3-jni.dll = libsqlite3-jni.so
-$(sqlite3-jni.dll):
-	@echo "************************************************************************"; \
-	echo  "*** If this fails to build, be sure to edit this makefile            ***"; \
-	echo  "*** to configure it for your system.                                 ***"; \
-	echo  "************************************************************************"
-	$(CC) $(CFLAGS) $(SQLITE_OPT) \
-		src/sqlite3-jni.c -shared -o $@
-	@echo "Now try running it with: make test"
-
-test.flags = -Djava.library.path=. sqlite3-jni-*.jar
-test: $(sqlite3-jni.dll)
-	java -jar $(test.flags)
-	java -jar $(test.flags) -t 7 -r 10 -shuffle
-
-clean:
-	-rm -f $(sqlite3-jni.dll)
-
-all: $(sqlite3-jni.dll)
@@ -1,34 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-import org.sqlite.jni.annotation.NotNull;
-
-/**
-   An implementation of {@link CollationCallback} which provides a
-   no-op xDestroy() method.
-*/
-public abstract class AbstractCollationCallback
-  implements CollationCallback, XDestroyCallback {
-  /**
-     Must compare the given byte arrays and return the result using
-     {@code memcmp()} semantics.
-  */
-  public abstract int call(@NotNull byte[] lhs, @NotNull byte[] rhs);
-
-  /**
-     Optionally override to be notified when the UDF is finalized by
-     SQLite. This implementation does nothing.
-  */
-  public void xDestroy(){}
-}
@@ -1,72 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-
-/**
-   A SQLFunction implementation for aggregate functions.  Its T is the
-   data type of its "accumulator" state, an instance of which is
-   intended to be be managed using the getAggregateState() and
-   takeAggregateState() methods.
-*/
-public abstract class AggregateFunction<T> implements SQLFunction {
-
-  /**
-     As for the xStep() argument of the C API's
-     sqlite3_create_function().  If this function throws, the
-     exception is not propagated and a warning might be emitted to a
-     debugging channel.
-  */
-  public abstract void xStep(sqlite3_context cx, sqlite3_value[] args);
-
-  /**
-     As for the xFinal() argument of the C API's sqlite3_create_function().
-     If this function throws, it is translated into an sqlite3_result_error().
-  */
-  public abstract void xFinal(sqlite3_context cx);
-
-  /**
-     Optionally override to be notified when the UDF is finalized by
-     SQLite.
-  */
-  public void xDestroy() {}
-
-  /** Per-invocation state for the UDF. */
-  private final SQLFunction.PerContextState<T> map =
-    new SQLFunction.PerContextState<>();
-
-  /**
-     To be called from the implementation's xStep() method, as well
-     as the xValue() and xInverse() methods of the {@link WindowFunction}
-     subclass, to fetch the current per-call UDF state. On the
-     first call to this method for any given sqlite3_context
-     argument, the context is set to the given initial value. On all other
-     calls, the 2nd argument is ignored.
-
-     @see SQLFunction.PerContextState#getAggregateState
-  */
-  protected final ValueHolder<T> getAggregateState(sqlite3_context cx, T initialValue){
-    return map.getAggregateState(cx, initialValue);
-  }
-
-  /**
-     To be called from the implementation's xFinal() method to fetch
-     the final state of the UDF and remove its mapping.
-
-     see SQLFunction.PerContextState#takeAggregateState
-  */
-  protected final T takeAggregateState(sqlite3_context cx){
-    return map.takeAggregateState(cx);
-  }
-}
@@ -1,28 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-import org.sqlite.jni.annotation.*;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_set_authorizer}.
-*/
-public interface AuthorizerCallback extends CallbackProxy {
-  /**
-     Must function as described for the C-level
-     sqlite3_set_authorizer() callback.
-  */
-  int call(int opId, @Nullable String s1, @Nullable String s2,
-           @Nullable String s3, @Nullable String s4);
-
-}
@@ -1,40 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with the {@link SQLite3Jni#sqlite3_auto_extension}
-   family of APIs.
-*/
-public interface AutoExtensionCallback extends CallbackProxy {
-  /**
-     Must function as described for a C-level
-     sqlite3_auto_extension() callback.
-
-     <p>This callback may throw and the exception's error message will
-     be set as the db's error string.
-
-     <p>Tips for implementations:
-
-     <p>- Opening a database from an auto-extension handler will lead to
-     an endless recursion of the auto-handler triggering itself
-     indirectly for each newly-opened database.
-
-     <p>- If this routine is stateful, it may be useful to make the
-     overridden method synchronized.
-
-     <p>- Results are undefined if the given db is closed by an auto-extension.
-  */
-  int call(sqlite3 db);
-}
@@ -1,26 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_busy_handler}.
-*/
-public interface BusyHandlerCallback extends CallbackProxy {
-  /**
-     Must function as documented for the C-level
-     sqlite3_busy_handler() callback argument, minus the (void*)
-     argument the C-level function requires.
-  */
-  int call(int n);
-}
@@ -1,44 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-/**
-   This marker interface exists soley for use as a documentation and
-   class-grouping tool. It should be applied to interfaces or
-   classes which have a call() method implementing some specific
-   callback interface on behalf of the C library.
-
-   <p>Unless very explicitely documented otherwise, callbacks must
-   never throw. Any which do throw but should not might trigger debug
-   output regarding the error, but the exception will not be
-   propagated.  For callback interfaces which support returning error
-   info to the core, the JNI binding will convert any exceptions to
-   C-level error information. For callback interfaces which do not
-   support, all exceptions will necessarily be suppressed in order to
-   retain the C-style no-throw semantics.
-
-   <p>Callbacks of this style follow a common naming convention:
-
-   <p>1) They use the UpperCamelCase form of the C function they're
-   proxying for, minus the {@code sqlite3_} prefix, plus a {@code
-   Callback} suffix. e.g. {@code sqlite3_busy_handler()}'s callback is
-   named {@code BusyHandlerCallback}. Exceptions are made where that
-   would potentially be ambiguous, e.g. {@link ConfigSqllogCallback}
-   instead of {@code ConfigCallback} because the {@code
-   sqlite3_config()} interface may need to support more callback types
-   in the future.
-
-   <p>2) They all have a {@code call()} method but its signature is
-   callback-specific.
-*/
-public interface CallbackProxy {}
@@ -1,35 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-import org.sqlite.jni.annotation.NotNull;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_create_collation}.
-
-   @see AbstractCollationCallback
-*/
-public interface CollationCallback
-  extends CallbackProxy, XDestroyCallback {
-  /**
-     Must compare the given byte arrays and return the result using
-     {@code memcmp()} semantics.
-  */
-  int call(@NotNull byte[] lhs, @NotNull byte[] rhs);
-
-  /**
-     Called by SQLite when the collation is destroyed. If a collation
-     requires custom cleanup, override this method.
-  */
-  void xDestroy();
-}
@@ -1,28 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_collation_needed}.
-*/
-public interface CollationNeededCallback extends CallbackProxy {
-  /**
-     Has the same semantics as the C-level sqlite3_create_collation()
-     callback.
-
-     <p>If it throws, the exception message is passed on to the db and
-     the exception is suppressed.
-  */
-  int call(sqlite3 db, int eTextRep, String collationName);
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_commit_hook}.
-*/
-public interface CommitHookCallback extends CallbackProxy {
-  /**
-     Works as documented for the C-level sqlite3_commit_hook()
-     callback.  Must not throw.
-  */
-  int call();
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-08-23
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A callback for use with sqlite3_config().
-*/
-public interface ConfigLogCallback {
-  /**
-     Must function as described for a C-level callback for
-     {@link SQLite3Jni#sqlite3_config(ConfigLogCallback)}, with the slight signature change.
-  */
-  void call(int errCode, String msg);
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-08-23
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A callback for use with sqlite3_config().
-*/
-public interface ConfigSqllogCallback {
-  /**
-     Must function as described for a C-level callback for
-     {@link SQLite3Jni#sqlite3_config(ConfigSqllogCallback)}, with the slight signature change.
-  */
-  void call(sqlite3 db, String msg, int msgType );
-}
@@ -1,33 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A helper for passing pointers between JNI C code and Java, in
-   particular for output pointers of high-level object types in the
-   sqlite3 C API, e.g. (sqlite3**) and (sqlite3_stmt**).  This is
-   intended to be subclassed and the ContextType is intended to be the
-   class which is doing the subclassing. The intent of the ContextType
-   is strictly to provide some level of type safety by avoiding that
-   NativePointerHolder is not inadvertently passed to an incompatible
-   function signature.
-
-   These objects do not own the pointer they refer to.  They are
-   intended simply to communicate that pointer between C and Java.
-*/
-public class NativePointerHolder<ContextType> {
-  //! Only set from JNI, where access permissions don't matter.
-  private volatile long nativePointer = 0;
-  public final long getNativePointer(){ return nativePointer; }
-}
@@ -1,231 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Helper classes for handling JNI output pointers.
-
-   <p>We do not use a generic OutputPointer<T> because working with those
-   from the native JNI code is unduly quirky due to a lack of
-   autoboxing at that level.
-
-   <p>The usage is similar for all of thes types:
-
-   <pre>{@code
-   OutputPointer.sqlite3 out = new OutputPointer.sqlite3();
-   assert( null==out.get() );
-   int rc = sqlite3_open(":memory:", out);
-   if( 0!=rc ) ... error;
-   assert( null!=out.get() );
-   sqlite3 db = out.take();
-   assert( null==out.get() );
-   }</pre>
-
-   <p>With the minor exception that the primitive types permit direct
-   access to the object's value via the `value` property, whereas the
-   JNI-level opaque types do not permit client-level code to set that
-   property.
-
-   <p>Warning: do not share instances of these classes across
-   threads. Doing so may lead to corrupting sqlite3-internal state.
-*/
-public final class OutputPointer {
-
-  /**
-     Output pointer for use with routines, such as sqlite3_open(),
-     which return a database handle via an output pointer. These
-     pointers can only be set by the JNI layer, not by client-level
-     code.
-  */
-  public static final class sqlite3 {
-    private org.sqlite.jni.sqlite3 value;
-    /** Initializes with a null value. */
-    public sqlite3(){value = null;}
-    /** Sets the current value to null. */
-    public void clear(){value = null;}
-    /** Returns the current value. */
-    public final org.sqlite.jni.sqlite3 get(){return value;}
-    /** Equivalent to calling get() then clear(). */
-    public final org.sqlite.jni.sqlite3 take(){
-      final org.sqlite.jni.sqlite3 v = value;
-      value = null;
-      return v;
-    }
-  }
-
-  /**
-     Output pointer for sqlite3_blob_open(). These
-     pointers can only be set by the JNI layer, not by client-level
-     code.
-  */
-  public static final class sqlite3_blob {
-    private org.sqlite.jni.sqlite3_blob value;
-    /** Initializes with a null value. */
-    public sqlite3_blob(){value = null;}
-    /** Sets the current value to null. */
-    public void clear(){value = null;}
-    /** Returns the current value. */
-    public final org.sqlite.jni.sqlite3_blob get(){return value;}
-    /** Equivalent to calling get() then clear(). */
-    public final org.sqlite.jni.sqlite3_blob take(){
-      final org.sqlite.jni.sqlite3_blob v = value;
-      value = null;
-      return v;
-    }
-  }
-
-  /**
-     Output pointer for use with routines, such as sqlite3_prepare(),
-     which return a statement handle via an output pointer. These
-     pointers can only be set by the JNI layer, not by client-level
-     code.
-  */
-  public static final class sqlite3_stmt {
-    private org.sqlite.jni.sqlite3_stmt value;
-    /** Initializes with a null value. */
-    public sqlite3_stmt(){value = null;}
-    /** Sets the current value to null. */
-    public void clear(){value = null;}
-    /** Returns the current value. */
-    public final org.sqlite.jni.sqlite3_stmt get(){return value;}
-    /** Equivalent to calling get() then clear(). */
-    public final org.sqlite.jni.sqlite3_stmt take(){
-      final org.sqlite.jni.sqlite3_stmt v = value;
-      value = null;
-      return v;
-    }
-  }
-
-  /**
-     Output pointer for use with routines, such as sqlite3_prepupdate_new(),
-     which return a sqlite3_value handle via an output pointer. These
-     pointers can only be set by the JNI layer, not by client-level
-     code.
-  */
-  public static final class sqlite3_value {
-    private org.sqlite.jni.sqlite3_value value;
-    /** Initializes with a null value. */
-    public sqlite3_value(){value = null;}
-    /** Sets the current value to null. */
-    public void clear(){value = null;}
-    /** Returns the current value. */
-    public final org.sqlite.jni.sqlite3_value get(){return value;}
-    /** Equivalent to calling get() then clear(). */
-    public final org.sqlite.jni.sqlite3_value take(){
-      final org.sqlite.jni.sqlite3_value v = value;
-      value = null;
-      return v;
-    }
-  }
-
-  /**
-     Output pointer for use with native routines which return booleans
-     via integer output pointers.
-  */
-  public static final class Bool {
-    /**
-       This is public for ease of use. Accessors are provided for
-       consistency with the higher-level types.
-    */
-    public boolean value;
-    /** Initializes with the value 0. */
-    public Bool(){this(false);}
-    /** Initializes with the value v. */
-    public Bool(boolean v){value = v;}
-    /** Returns the current value. */
-    public final boolean get(){return value;}
-    /** Sets the current value to v. */
-    public final void set(boolean v){value = v;}
-  }
-
-  /**
-     Output pointer for use with native routines which return integers via
-     output pointers.
-  */
-  public static final class Int32 {
-    /**
-       This is public for ease of use. Accessors are provided for
-       consistency with the higher-level types.
-    */
-    public int value;
-    /** Initializes with the value 0. */
-    public Int32(){this(0);}
-    /** Initializes with the value v. */
-    public Int32(int v){value = v;}
-    /** Returns the current value. */
-    public final int get(){return value;}
-    /** Sets the current value to v. */
-    public final void set(int v){value = v;}
-  }
-
-  /**
-     Output pointer for use with native routines which return 64-bit integers
-     via output pointers.
-  */
-  public static final class Int64 {
-    /**
-       This is public for ease of use. Accessors are provided for
-       consistency with the higher-level types.
-    */
-    public long value;
-    /** Initializes with the value 0. */
-    public Int64(){this(0);}
-    /** Initializes with the value v. */
-    public Int64(long v){value = v;}
-    /** Returns the current value. */
-    public final long get(){return value;}
-    /** Sets the current value. */
-    public final void set(long v){value = v;}
-  }
-
-  /**
-     Output pointer for use with native routines which return strings via
-     output pointers.
-  */
-  public static final class String {
-    /**
-       This is public for ease of use. Accessors are provided for
-       consistency with the higher-level types.
-    */
-    public java.lang.String value;
-    /** Initializes with a null value. */
-    public String(){this(null);}
-    /** Initializes with the value v. */
-    public String(java.lang.String v){value = v;}
-    /** Returns the current value. */
-    public final java.lang.String get(){return value;}
-    /** Sets the current value. */
-    public final void set(java.lang.String v){value = v;}
-  }
-
-  /**
-     Output pointer for use with native routines which return byte
-     arrays via output pointers.
-  */
-  public static final class ByteArray {
-    /**
-       This is public for ease of use. Accessors are provided for
-       consistency with the higher-level types.
-    */
-    public byte[] value;
-    /** Initializes with the value null. */
-    public ByteArray(){this(null);}
-    /** Initializes with the value v. */
-    public ByteArray(byte[] v){value = v;}
-    /** Returns the current value. */
-    public final byte[] get(){return value;}
-    /** Sets the current value. */
-    public final void set(byte[] v){value = v;}
-  }
-}
@@ -1,78 +0,0 @@
-/*
-** 2023-09-13
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_prepare_multi}.
-*/
-public interface PrepareMultiCallback extends CallbackProxy {
-
-  /**
-     Gets passed a sqlite3_stmt which it may handle in arbitrary ways,
-     transfering ownership of it to this function.
-
-     sqlite3_prepare_multi() will _not_ finalize st - it is up
-     to the call() implementation how st is handled.
-
-     Must return 0 on success or an SQLITE_... code on error.
-
-     See the {@link Finalize} class for a wrapper which finalizes the
-     statement after calling a proxy PrepareMultiCallback.
-  */
-  int call(sqlite3_stmt st);
-
-  /**
-     A PrepareMultiCallback impl which wraps a separate impl and finalizes
-     any sqlite3_stmt passed to its callback.
-  */
-  public static final class Finalize implements PrepareMultiCallback {
-    private PrepareMultiCallback p;
-    /**
-       p is the proxy to call() when this.call() is called.
-    */
-    public Finalize( PrepareMultiCallback p ){
-      this.p = p;
-    }
-    /**
-       Calls the call() method of the proxied callback and either returns its
-       result or propagates an exception. Either way, it passes its argument to
-       sqlite3_finalize() before returning.
-    */
-    @Override public int call(sqlite3_stmt st){
-      try {
-        return this.p.call(st);
-      }finally{
-        SQLite3Jni.sqlite3_finalize(st);
-      }
-    }
-  }
-
-  /**
-     A PrepareMultiCallback impl which steps entirely through a result set,
-     ignoring all non-error results.
-  */
-  public static final class StepAll implements PrepareMultiCallback {
-    public StepAll(){}
-    /**
-       Calls sqlite3_step() on st until it returns something other than
-       SQLITE_ROW. If the final result is SQLITE_DONE then 0 is returned,
-       else the result of the final step is returned.
-    */
-    @Override public int call(sqlite3_stmt st){
-      int rc = SQLite3Jni.SQLITE_DONE;
-      while( SQLite3Jni.SQLITE_ROW == (rc = SQLite3Jni.sqlite3_step(st)) ){}
-      return SQLite3Jni.SQLITE_DONE==rc ? 0 : rc;
-    }
-  }
-}
@@ -1,26 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_preupdate_hook}.
-*/
-public interface PreupdateHookCallback extends CallbackProxy {
-  /**
-     Must function as described for the C-level sqlite3_preupdate_hook()
-     callback.
-  */
-  void call(sqlite3 db, int op, String dbName, String dbTable,
-            long iKey1, long iKey2 );
-}
@@ -1,27 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_progress_handler}.
-*/
-public interface ProgressHandlerCallback extends CallbackProxy {
-  /**
-     Works as documented for the C-level sqlite3_progress_handler() callback.
-
-     <p>If it throws, the exception message is passed on to the db and
-     the exception is suppressed.
-  */
-  int call();
-}
@@ -1,155 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   This enum contains all of the core and "extended" result codes used
-   by the sqlite3 library. It is provided not for use with the C-style
-   API (with which it won't work) but for higher-level code which may
-   find it useful to map SQLite result codes to human-readable names.
-*/
-public enum ResultCode {
-  SQLITE_OK(SQLite3Jni.SQLITE_OK),
-  SQLITE_ERROR(SQLite3Jni.SQLITE_ERROR),
-  SQLITE_INTERNAL(SQLite3Jni.SQLITE_INTERNAL),
-  SQLITE_PERM(SQLite3Jni.SQLITE_PERM),
-  SQLITE_ABORT(SQLite3Jni.SQLITE_ABORT),
-  SQLITE_BUSY(SQLite3Jni.SQLITE_BUSY),
-  SQLITE_LOCKED(SQLite3Jni.SQLITE_LOCKED),
-  SQLITE_NOMEM(SQLite3Jni.SQLITE_NOMEM),
-  SQLITE_READONLY(SQLite3Jni.SQLITE_READONLY),
-  SQLITE_INTERRUPT(SQLite3Jni.SQLITE_INTERRUPT),
-  SQLITE_IOERR(SQLite3Jni.SQLITE_IOERR),
-  SQLITE_CORRUPT(SQLite3Jni.SQLITE_CORRUPT),
-  SQLITE_NOTFOUND(SQLite3Jni.SQLITE_NOTFOUND),
-  SQLITE_FULL(SQLite3Jni.SQLITE_FULL),
-  SQLITE_CANTOPEN(SQLite3Jni.SQLITE_CANTOPEN),
-  SQLITE_PROTOCOL(SQLite3Jni.SQLITE_PROTOCOL),
-  SQLITE_EMPTY(SQLite3Jni.SQLITE_EMPTY),
-  SQLITE_SCHEMA(SQLite3Jni.SQLITE_SCHEMA),
-  SQLITE_TOOBIG(SQLite3Jni.SQLITE_TOOBIG),
-  SQLITE_CONSTRAINT(SQLite3Jni.SQLITE_CONSTRAINT),
-  SQLITE_MISMATCH(SQLite3Jni.SQLITE_MISMATCH),
-  SQLITE_MISUSE(SQLite3Jni.SQLITE_MISUSE),
-  SQLITE_NOLFS(SQLite3Jni.SQLITE_NOLFS),
-  SQLITE_AUTH(SQLite3Jni.SQLITE_AUTH),
-  SQLITE_FORMAT(SQLite3Jni.SQLITE_FORMAT),
-  SQLITE_RANGE(SQLite3Jni.SQLITE_RANGE),
-  SQLITE_NOTADB(SQLite3Jni.SQLITE_NOTADB),
-  SQLITE_NOTICE(SQLite3Jni.SQLITE_NOTICE),
-  SQLITE_WARNING(SQLite3Jni.SQLITE_WARNING),
-  SQLITE_ROW(SQLite3Jni.SQLITE_ROW),
-  SQLITE_DONE(SQLite3Jni.SQLITE_DONE),
-  SQLITE_ERROR_MISSING_COLLSEQ(SQLite3Jni.SQLITE_ERROR_MISSING_COLLSEQ),
-  SQLITE_ERROR_RETRY(SQLite3Jni.SQLITE_ERROR_RETRY),
-  SQLITE_ERROR_SNAPSHOT(SQLite3Jni.SQLITE_ERROR_SNAPSHOT),
-  SQLITE_IOERR_READ(SQLite3Jni.SQLITE_IOERR_READ),
-  SQLITE_IOERR_SHORT_READ(SQLite3Jni.SQLITE_IOERR_SHORT_READ),
-  SQLITE_IOERR_WRITE(SQLite3Jni.SQLITE_IOERR_WRITE),
-  SQLITE_IOERR_FSYNC(SQLite3Jni.SQLITE_IOERR_FSYNC),
-  SQLITE_IOERR_DIR_FSYNC(SQLite3Jni.SQLITE_IOERR_DIR_FSYNC),
-  SQLITE_IOERR_TRUNCATE(SQLite3Jni.SQLITE_IOERR_TRUNCATE),
-  SQLITE_IOERR_FSTAT(SQLite3Jni.SQLITE_IOERR_FSTAT),
-  SQLITE_IOERR_UNLOCK(SQLite3Jni.SQLITE_IOERR_UNLOCK),
-  SQLITE_IOERR_RDLOCK(SQLite3Jni.SQLITE_IOERR_RDLOCK),
-  SQLITE_IOERR_DELETE(SQLite3Jni.SQLITE_IOERR_DELETE),
-  SQLITE_IOERR_BLOCKED(SQLite3Jni.SQLITE_IOERR_BLOCKED),
-  SQLITE_IOERR_NOMEM(SQLite3Jni.SQLITE_IOERR_NOMEM),
-  SQLITE_IOERR_ACCESS(SQLite3Jni.SQLITE_IOERR_ACCESS),
-  SQLITE_IOERR_CHECKRESERVEDLOCK(SQLite3Jni.SQLITE_IOERR_CHECKRESERVEDLOCK),
-  SQLITE_IOERR_LOCK(SQLite3Jni.SQLITE_IOERR_LOCK),
-  SQLITE_IOERR_CLOSE(SQLite3Jni.SQLITE_IOERR_CLOSE),
-  SQLITE_IOERR_DIR_CLOSE(SQLite3Jni.SQLITE_IOERR_DIR_CLOSE),
-  SQLITE_IOERR_SHMOPEN(SQLite3Jni.SQLITE_IOERR_SHMOPEN),
-  SQLITE_IOERR_SHMSIZE(SQLite3Jni.SQLITE_IOERR_SHMSIZE),
-  SQLITE_IOERR_SHMLOCK(SQLite3Jni.SQLITE_IOERR_SHMLOCK),
-  SQLITE_IOERR_SHMMAP(SQLite3Jni.SQLITE_IOERR_SHMMAP),
-  SQLITE_IOERR_SEEK(SQLite3Jni.SQLITE_IOERR_SEEK),
-  SQLITE_IOERR_DELETE_NOENT(SQLite3Jni.SQLITE_IOERR_DELETE_NOENT),
-  SQLITE_IOERR_MMAP(SQLite3Jni.SQLITE_IOERR_MMAP),
-  SQLITE_IOERR_GETTEMPPATH(SQLite3Jni.SQLITE_IOERR_GETTEMPPATH),
-  SQLITE_IOERR_CONVPATH(SQLite3Jni.SQLITE_IOERR_CONVPATH),
-  SQLITE_IOERR_VNODE(SQLite3Jni.SQLITE_IOERR_VNODE),
-  SQLITE_IOERR_AUTH(SQLite3Jni.SQLITE_IOERR_AUTH),
-  SQLITE_IOERR_BEGIN_ATOMIC(SQLite3Jni.SQLITE_IOERR_BEGIN_ATOMIC),
-  SQLITE_IOERR_COMMIT_ATOMIC(SQLite3Jni.SQLITE_IOERR_COMMIT_ATOMIC),
-  SQLITE_IOERR_ROLLBACK_ATOMIC(SQLite3Jni.SQLITE_IOERR_ROLLBACK_ATOMIC),
-  SQLITE_IOERR_DATA(SQLite3Jni.SQLITE_IOERR_DATA),
-  SQLITE_IOERR_CORRUPTFS(SQLite3Jni.SQLITE_IOERR_CORRUPTFS),
-  SQLITE_LOCKED_SHAREDCACHE(SQLite3Jni.SQLITE_LOCKED_SHAREDCACHE),
-  SQLITE_LOCKED_VTAB(SQLite3Jni.SQLITE_LOCKED_VTAB),
-  SQLITE_BUSY_RECOVERY(SQLite3Jni.SQLITE_BUSY_RECOVERY),
-  SQLITE_BUSY_SNAPSHOT(SQLite3Jni.SQLITE_BUSY_SNAPSHOT),
-  SQLITE_BUSY_TIMEOUT(SQLite3Jni.SQLITE_BUSY_TIMEOUT),
-  SQLITE_CANTOPEN_NOTEMPDIR(SQLite3Jni.SQLITE_CANTOPEN_NOTEMPDIR),
-  SQLITE_CANTOPEN_ISDIR(SQLite3Jni.SQLITE_CANTOPEN_ISDIR),
-  SQLITE_CANTOPEN_FULLPATH(SQLite3Jni.SQLITE_CANTOPEN_FULLPATH),
-  SQLITE_CANTOPEN_CONVPATH(SQLite3Jni.SQLITE_CANTOPEN_CONVPATH),
-  SQLITE_CANTOPEN_SYMLINK(SQLite3Jni.SQLITE_CANTOPEN_SYMLINK),
-  SQLITE_CORRUPT_VTAB(SQLite3Jni.SQLITE_CORRUPT_VTAB),
-  SQLITE_CORRUPT_SEQUENCE(SQLite3Jni.SQLITE_CORRUPT_SEQUENCE),
-  SQLITE_CORRUPT_INDEX(SQLite3Jni.SQLITE_CORRUPT_INDEX),
-  SQLITE_READONLY_RECOVERY(SQLite3Jni.SQLITE_READONLY_RECOVERY),
-  SQLITE_READONLY_CANTLOCK(SQLite3Jni.SQLITE_READONLY_CANTLOCK),
-  SQLITE_READONLY_ROLLBACK(SQLite3Jni.SQLITE_READONLY_ROLLBACK),
-  SQLITE_READONLY_DBMOVED(SQLite3Jni.SQLITE_READONLY_DBMOVED),
-  SQLITE_READONLY_CANTINIT(SQLite3Jni.SQLITE_READONLY_CANTINIT),
-  SQLITE_READONLY_DIRECTORY(SQLite3Jni.SQLITE_READONLY_DIRECTORY),
-  SQLITE_ABORT_ROLLBACK(SQLite3Jni.SQLITE_ABORT_ROLLBACK),
-  SQLITE_CONSTRAINT_CHECK(SQLite3Jni.SQLITE_CONSTRAINT_CHECK),
-  SQLITE_CONSTRAINT_COMMITHOOK(SQLite3Jni.SQLITE_CONSTRAINT_COMMITHOOK),
-  SQLITE_CONSTRAINT_FOREIGNKEY(SQLite3Jni.SQLITE_CONSTRAINT_FOREIGNKEY),
-  SQLITE_CONSTRAINT_FUNCTION(SQLite3Jni.SQLITE_CONSTRAINT_FUNCTION),
-  SQLITE_CONSTRAINT_NOTNULL(SQLite3Jni.SQLITE_CONSTRAINT_NOTNULL),
-  SQLITE_CONSTRAINT_PRIMARYKEY(SQLite3Jni.SQLITE_CONSTRAINT_PRIMARYKEY),
-  SQLITE_CONSTRAINT_TRIGGER(SQLite3Jni.SQLITE_CONSTRAINT_TRIGGER),
-  SQLITE_CONSTRAINT_UNIQUE(SQLite3Jni.SQLITE_CONSTRAINT_UNIQUE),
-  SQLITE_CONSTRAINT_VTAB(SQLite3Jni.SQLITE_CONSTRAINT_VTAB),
-  SQLITE_CONSTRAINT_ROWID(SQLite3Jni.SQLITE_CONSTRAINT_ROWID),
-  SQLITE_CONSTRAINT_PINNED(SQLite3Jni.SQLITE_CONSTRAINT_PINNED),
-  SQLITE_CONSTRAINT_DATATYPE(SQLite3Jni.SQLITE_CONSTRAINT_DATATYPE),
-  SQLITE_NOTICE_RECOVER_WAL(SQLite3Jni.SQLITE_NOTICE_RECOVER_WAL),
-  SQLITE_NOTICE_RECOVER_ROLLBACK(SQLite3Jni.SQLITE_NOTICE_RECOVER_ROLLBACK),
-  SQLITE_WARNING_AUTOINDEX(SQLite3Jni.SQLITE_WARNING_AUTOINDEX),
-  SQLITE_AUTH_USER(SQLite3Jni.SQLITE_AUTH_USER),
-  SQLITE_OK_LOAD_PERMANENTLY(SQLite3Jni.SQLITE_OK_LOAD_PERMANENTLY);
-
-  public final int value;
-
-  ResultCode(int rc){
-    value = rc;
-    ResultCodeMap.set(rc, this);
-  }
-
-  /**
-     Returns the entry from this enum for the given result code, or
-     null if no match is found.
-  */
-  public static ResultCode getEntryForInt(int rc){
-    return ResultCodeMap.get(rc);
-  }
-
-  /**
-     Internal level of indirection required because we cannot initialize
-     static enum members in an enum before the enum constructor is
-     invoked.
-  */
-  private static final class ResultCodeMap {
-    private static final java.util.Map<Integer,ResultCode> i2e
-      = new java.util.HashMap<>();
-    private static void set(int rc, ResultCode e){ i2e.put(rc, e); }
-    private static ResultCode get(int rc){ return i2e.get(rc); }
-  }
-
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_rollback_hook}.
-*/
-public interface RollbackHookCallback extends CallbackProxy {
-  /**
-     Works as documented for the C-level sqlite3_rollback_hook()
-     callback.
-  */
-  void call();
-}
@@ -1,103 +0,0 @@
-/*
-** 2023-07-22
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   SQLFunction is used in conjunction with the
-   sqlite3_create_function() JNI-bound API to give that native code
-   access to the callback functions needed in order to implement SQL
-   functions in Java.
-
-   <p>
-
-   This class is not used by itself, but is a marker base class. The
-   three UDF types are modelled by the inner classes Scalar,
-   Aggregate<T>, and Window<T>. Most simply, clients may subclass
-   those, or create anonymous classes from them, to implement
-   UDFs. Clients are free to create their own classes for use with
-   UDFs, so long as they conform to the public interfaces defined by
-   those three classes. The JNI layer only actively relies on the
-   SQLFunction base class and the method names and signatures used by
-   the UDF callback interfaces.
-*/
-public interface SQLFunction {
-
-  /**
-     PerContextState assists aggregate and window functions in
-     managing their accumulator state across calls to the UDF's
-     callbacks.
-
-     <p>T must be of a type which can be legally stored as a value in
-     java.util.HashMap<KeyType,T>.
-
-     <p>If a given aggregate or window function is called multiple times
-     in a single SQL statement, e.g. SELECT MYFUNC(A), MYFUNC(B)...,
-     then the clients need some way of knowing which call is which so
-     that they can map their state between their various UDF callbacks
-     and reset it via xFinal(). This class takes care of such
-     mappings.
-
-     <p>This class works by mapping
-     sqlite3_context.getAggregateContext() to a single piece of
-     state, of a client-defined type (the T part of this class), which
-     persists across a "matching set" of the UDF's callbacks.
-
-     <p>This class is a helper providing commonly-needed functionality
-     - it is not required for use with aggregate or window functions.
-     Client UDFs are free to perform such mappings using custom
-     approaches. The provided {@link AggregateFunction} and {@link
-     WindowFunction} classes use this.
-  */
-  public static final class PerContextState<T> {
-    private final java.util.Map<Long,ValueHolder<T>> map
-      = new java.util.HashMap<>();
-
-    /**
-       Should be called from a UDF's xStep(), xValue(), and xInverse()
-       methods, passing it that method's first argument and an initial
-       value for the persistent state. If there is currently no
-       mapping for the given context within the map, one is created
-       using the given initial value, else the existing one is used
-       and the 2nd argument is ignored.  It returns a ValueHolder<T>
-       which can be used to modify that state directly without
-       requiring that the client update the underlying map's entry.
-
-       <p>The caller is obligated to eventually call
-       takeAggregateState() to clear the mapping.
-    */
-    public ValueHolder<T> getAggregateState(sqlite3_context cx, T initialValue){
-      final Long key = cx.getAggregateContext(true);
-      ValueHolder<T> rc = null==key ? null : map.get(key);
-      if( null==rc ){
-        map.put(key, rc = new ValueHolder<>(initialValue));
-      }
-      return rc;
-    }
-
-    /**
-       Should be called from a UDF's xFinal() method and passed that
-       method's first argument. This function removes the value
-       associated with cx.getAggregateContext() from the map and
-       returns it, returning null if no other UDF method has been
-       called to set up such a mapping. The latter condition will be
-       the case if a UDF is used in a statement which has no result
-       rows.
-    */
-    public T takeAggregateState(sqlite3_context cx){
-      final ValueHolder<T> h = map.remove(cx.getAggregateContext(false));
-      return null==h ? null : h.value;
-    }
-  }
-
-}
@@ -1,33 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-
-/**
-   A SQLFunction implementation for scalar functions.
-*/
-public abstract class ScalarFunction implements SQLFunction {
-  /**
-     As for the xFunc() argument of the C API's
-     sqlite3_create_function(). If this function throws, it is
-     translated into an sqlite3_result_error().
-  */
-  public abstract void xFunc(sqlite3_context cx, sqlite3_value[] args);
-
-  /**
-     Optionally override to be notified when the UDF is finalized by
-     SQLite. This implementation does nothing.
-  */
-  public void xDestroy() {}
-}
@@ -1,35 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A wrapper object for use with sqlite3_table_column_metadata().
-   They are populated only via that interface.
-*/
-public final class TableColumnMetadata {
-  OutputPointer.Bool pNotNull = new OutputPointer.Bool();
-  OutputPointer.Bool pPrimaryKey = new OutputPointer.Bool();
-  OutputPointer.Bool pAutoinc = new OutputPointer.Bool();
-  OutputPointer.String pzCollSeq = new OutputPointer.String();
-  OutputPointer.String pzDataType = new OutputPointer.String();
-
-  public TableColumnMetadata(){
-  }
-
-  public String getDataType(){ return pzDataType.value; }
-  public String getCollation(){ return pzCollSeq.value; }
-  public boolean isNotNull(){ return pNotNull.value; }
-  public boolean isPrimaryKey(){ return pPrimaryKey.value; }
-  public boolean isAutoincrement(){ return pAutoinc.value; }
-}
@@ -1,50 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-import org.sqlite.jni.annotation.Nullable;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_trace_v2}.
-*/
-public interface TraceV2Callback extends CallbackProxy {
-  /**
-     Called by sqlite3 for various tracing operations, as per
-     sqlite3_trace_v2(). Note that this interface elides the 2nd
-     argument to the native trace callback, as that role is better
-     filled by instance-local state.
-
-     <p>These callbacks may throw, in which case their exceptions are
-     converted to C-level error information.
-
-     <p>The 2nd argument to this function, if non-null, will be a an
-     sqlite3 or sqlite3_stmt object, depending on the first argument
-     (see below).
-
-     <p>The final argument to this function is the "X" argument
-     documented for sqlite3_trace() and sqlite3_trace_v2(). Its type
-     depends on value of the first argument:
-
-     <p>- SQLITE_TRACE_STMT: pNative is a sqlite3_stmt. pX is a String
-     containing the prepared SQL.
-
-     <p>- SQLITE_TRACE_PROFILE: pNative is a sqlite3_stmt. pX is a Long
-     holding an approximate number of nanoseconds the statement took
-     to run.
-
-     <p>- SQLITE_TRACE_ROW: pNative is a sqlite3_stmt. pX is null.
-
-     <p>- SQLITE_TRACE_CLOSE: pNative is a sqlite3. pX is null.
-  */
-  int call(int traceFlag, Object pNative, @Nullable Object pX);
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for use with {@link SQLite3Jni#sqlite3_update_hook}.
-*/
-public interface UpdateHookCallback extends CallbackProxy {
-  /**
-     Must function as described for the C-level sqlite3_update_hook()
-     callback.
-  */
-  void call(int opId, String dbName, String tableName, long rowId);
-}
@@ -1,39 +0,0 @@
-/*
-** 2023-08-25
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-
-/**
-   A SQLFunction implementation for window functions.  Note that
-   WindowFunction inherits from {@link AggregateFunction} and each
-   instance is required to implement the inherited abstract methods
-   from that class. See {@link AggregateFunction} for information on
-   managing the UDF's invocation-specific state.
-*/
-public abstract class WindowFunction<T> extends AggregateFunction<T> {
-
-  /**
-     As for the xInverse() argument of the C API's
-     sqlite3_create_window_function(). If this function throws, the
-     exception is not propagated and a warning might be emitted
-     to a debugging channel.
-  */
-  public abstract void xInverse(sqlite3_context cx, sqlite3_value[] args);
-
-  /**
-     As for the xValue() argument of the C API's sqlite3_create_window_function().
-     See xInverse() for the fate of any exceptions this throws.
-  */
-  public abstract void xValue(sqlite3_context cx);
-}
@@ -1,37 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file declares JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   Callback for a hook called by SQLite when certain client-provided
-   state are destroyed. It gets its name from the pervasive use of
-   the symbol name xDestroy() for this purpose in the C API
-   documentation.
-*/
-public interface XDestroyCallback {
-  /**
-     Must perform any cleanup required by this object. Must not
-     throw. Must not call back into the sqlite3 API, else it might
-     invoke a deadlock.
-
-     WARNING: as a rule, it is never safe to register individual
-     instances with this interface multiple times in the
-     library. e.g., do not register the same CollationCallback with
-     multiple arities or names using sqlite3_create_collation().  If
-     this rule is violated, the library will eventually try to free
-     each individual reference, leading to memory corruption or a
-     crash via duplicate free().
-  */
-  public void xDestroy();
-}
@@ -1,35 +0,0 @@
-package org.sqlite.jni.annotation;
-
-/**
-   This annotation is for marking functions as "canonical", meaning
-   that they map directly to a function in the core sqlite3 C API. The
-   intent is to distinguish them from functions added specifically to
-   the Java API.
-
-   <p>Canonical functions, unless specifically documented, have the
-   same semantics as their counterparts in <a
-   href="https://sqlite.org/c3ref/intro.html">the C API
-   documentation</a>, despite their signatures perhaps differing
-   slightly. Canonical forms may be native or implemented in Java.
-   Sometimes multiple overloads are labeled as Canonical because one
-   or more of them are just type- or encoding-related conversion
-   wrappers but provide identical semantics (e.g. from a String to a
-   byte[]).  The Java API adds a number of convenience overloads to
-   simplify use, as well as a few Java-specific functions, and those
-   are never flagged as @Canonical.
-
-   <p>In some cases, the canonical version of a function is private
-   and exposed to Java via public overloads.
-
-   <p>The comment property can be used to add a comment.
-*/
-@java.lang.annotation.Documented
-@java.lang.annotation.Retention(java.lang.annotation.RetentionPolicy.RUNTIME)
-@java.lang.annotation.Target(java.lang.annotation.ElementType.METHOD)
-public @interface Canonical{
-  /**
-     Brief comments about the binding, e.g. noting any major
-     semantic differences.
-  */
-  String comment() default "";
-}
@@ -1,40 +0,0 @@
-package org.sqlite.jni.annotation;
-
-/**
-   This annotation is for flagging parameters which may not legally be
-   null or point to closed/finalized C-side resources.
-
-   <p>In the case of Java types which map directly to C struct types
-   (e.g. {@link org.sqlite.jni.sqlite3}, {@link
-   org.sqlite.jni.sqlite3_stmt}, and {@link
-   org.sqlite.jni.sqlite3_context}), a closed/finalized resource is
-   also considered to be null for purposes this annotation because the
-   C-side effect of passing such a handle is the same as if null is
-   passed.</p>
-
-   <p>When used in the context of Java interfaces which are called
-   from the C APIs, this annotation communicates that the C API will
-   never pass a null value to the callback for that parameter.</p>
-
-   <p>Passing a null, for this annotation's definition of null, for
-   any parameter marked with this annoation specifically invokes
-   undefined behavior.</p>
-
-   <p>Note that the C-style API does not throw any exceptions on its
-   own because it has a no-throw policy in order to retain its C-style
-   semantics, but it may trigger NullPointerExceptions (or similar) if
-   passed a null for a parameter flagged with this annotation.</p>
-
-   <p>This annotation is informational only. No policy is in place to
-   programmatically ensure that NotNull is conformed to in client
-   code.</p>
-
-   <p>This annotation is solely for the use by the classes in this
-   package but is made public so that javadoc will link to it from the
-   annotated functions. It is not part of the public API and
-   client-level code must not rely on it.</p>
-*/
-@java.lang.annotation.Documented
-@java.lang.annotation.Retention(java.lang.annotation.RetentionPolicy.SOURCE)
-@java.lang.annotation.Target(java.lang.annotation.ElementType.PARAMETER)
-public @interface NotNull{}
@@ -1,19 +0,0 @@
-package org.sqlite.jni.annotation;
-
-/**
-   This annotation is for flagging parameters which may legally be
-   null, noting that they may behave differently if passed null but
-   are prepared to expect null as a value. When used in the context of
-   callback methods which are called into from the C APIs, this
-   annotation communicates that the C API may pass a null value to the
-   callback.
-
-   <p>This annotation is solely for the use by the classes in this
-   package but is made public so that javadoc will link to it from the
-   annotated functions. It is not part of the public API and
-   client-level code must not rely on it.
-*/
-@java.lang.annotation.Documented
-@java.lang.annotation.Retention(java.lang.annotation.RetentionPolicy.SOURCE)
-@java.lang.annotation.Target(java.lang.annotation.ElementType.PARAMETER)
-public @interface Nullable{}
@@ -1,4 +0,0 @@
-/**
-   This package houses annotations specific  a JNI binding to the SQLite3 C API.
-*/
-package org.sqlite.jni.annotation;
@@ -1,38 +0,0 @@
-/*
-** 2023-08-05
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-
-/**
-   INCOMPLETE AND COMPLETELY UNTESTED.
-
-   A utility object for holding FTS5-specific types and constants
-   which are used by multiple FTS5 classes.
-*/
-public final class Fts5 {
-  /* Not used */
-  private Fts5(){}
-
-  /**
-     Callback type for use with xTokenize() variants
-  */
-  public static interface XTokenizeCallback {
-    int call(int tFlags, byte[] txt, int iStart, int iEnd);
-  }
-
-  public static final int FTS5_TOKENIZE_QUERY    = 0x0001;
-  public static final int FTS5_TOKENIZE_PREFIX   = 0x0002;
-  public static final int FTS5_TOKENIZE_DOCUMENT = 0x0004;
-  public static final int FTS5_TOKENIZE_AUX      = 0x0008;
-  public static final int FTS5_TOKEN_COLOCATED   = 0x0001;
-}
@@ -1,24 +0,0 @@
-/*
-** 2023-08-04
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import org.sqlite.jni.*;
-
-/**
-   A wrapper for communicating C-level (Fts5Context*) instances with
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-*/
-public final class Fts5Context extends NativePointerHolder<Fts5Context> {
-}
@@ -1,120 +0,0 @@
-/*
-** 2023-08-04
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import java.nio.charset.StandardCharsets;
-import org.sqlite.jni.*;
-import org.sqlite.jni.annotation.*;
-
-/**
-   ALMOST COMPLETELY UNTESTED.
-
-   FAR FROM COMPLETE and the feasibility of binding this to Java
-   is still undetermined. This might be removed.
-*/
-public final class Fts5ExtensionApi extends NativePointerHolder<Fts5ExtensionApi> {
-  //! Only called from JNI
-  private Fts5ExtensionApi(){}
-  private final int iVersion = 2;
-
-  /* Callback type for used by xQueryPhrase(). */
-  public static interface XQueryPhraseCallback {
-    int call(Fts5ExtensionApi fapi, Fts5Context cx);
-  }
-
-  /**
-     Returns the singleton instance of this class.
-  */
-  public static native Fts5ExtensionApi getInstance();
-
-  @Canonical
-  public native int xColumnCount(@NotNull Fts5Context fcx);
-
-  @Canonical
-  public native int xColumnSize(@NotNull Fts5Context cx, int iCol,
-                                @NotNull OutputPointer.Int32 pnToken);
-
-  @Canonical
-  public native int xColumnText(@NotNull Fts5Context cx, int iCol,
-                                @NotNull OutputPointer.String txt);
-
-  @Canonical
-  public native int xColumnTotalSize(@NotNull Fts5Context fcx, int iCol,
-                                     @NotNull OutputPointer.Int64 pnToken);
-
-  @Canonical
-  public native Object xGetAuxdata(@NotNull Fts5Context cx, boolean clearIt);
-
-  @Canonical
-  public native int xInst(@NotNull Fts5Context cx, int iIdx,
-                          @NotNull OutputPointer.Int32 piPhrase,
-                          @NotNull OutputPointer.Int32 piCol,
-                          @NotNull OutputPointer.Int32 piOff);
-
-  @Canonical
-  public native int xInstCount(@NotNull Fts5Context fcx,
-                               @NotNull OutputPointer.Int32 pnInst);
-
-  @Canonical
-  public native int xPhraseCount(@NotNull Fts5Context fcx);
-
-  @Canonical
-  public native int xPhraseFirst(@NotNull Fts5Context cx, int iPhrase,
-                                 @NotNull Fts5PhraseIter iter,
-                                 @NotNull OutputPointer.Int32 iCol,
-                                 @NotNull OutputPointer.Int32 iOff);
-
-  @Canonical
-  public native int xPhraseFirstColumn(@NotNull Fts5Context cx, int iPhrase,
-                                       @NotNull Fts5PhraseIter iter,
-                                       @NotNull OutputPointer.Int32 iCol);
-  @Canonical
-  public native void xPhraseNext(@NotNull Fts5Context cx,
-                                 @NotNull Fts5PhraseIter iter,
-                                 @NotNull OutputPointer.Int32 iCol,
-                                 @NotNull OutputPointer.Int32 iOff);
-  @Canonical
-  public native void xPhraseNextColumn(@NotNull Fts5Context cx,
-                                       @NotNull Fts5PhraseIter iter,
-                                       @NotNull OutputPointer.Int32 iCol);
-  @Canonical
-  public native int xPhraseSize(@NotNull Fts5Context fcx, int iPhrase);
-
-  @Canonical
-  public native int xQueryPhrase(@NotNull Fts5Context cx, int iPhrase,
-                                 @NotNull XQueryPhraseCallback callback);
-  @Canonical
-  public native int xRowCount(@NotNull Fts5Context fcx,
-                              @NotNull OutputPointer.Int64 nRow);
-
-  @Canonical
-  public native long xRowid(@NotNull Fts5Context cx);
-  /* Note that the JNI binding lacks the C version's xDelete()
-     callback argument. Instead, if pAux has an xDestroy() method, it
-     is called if the FTS5 API finalizes the aux state (including if
-     allocation of storage for the auxdata fails). Any reference to
-     pAux held by the JNI layer will be relinquished regardless of
-     whether pAux has an xDestroy() method. */
-
-  @Canonical
-  public native int xSetAuxdata(@NotNull Fts5Context cx, @Nullable Object pAux);
-
-  @Canonical
-  public native int xTokenize(@NotNull Fts5Context cx, @NotNull byte[] pText,
-                              @NotNull Fts5.XTokenizeCallback callback);
-
-  @Canonical
-  public native Object xUserData(Fts5Context cx);
-  //^^^ returns the pointer passed as the 3rd arg to the C-level
-  // fts5_api::xCreateFunction().
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-08-04
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import org.sqlite.jni.NativePointerHolder;
-
-/**
-   A wrapper for C-level Fts5PhraseIter. They are only modified and
-   inspected by native-level code.
-*/
-public final class Fts5PhraseIter extends NativePointerHolder<Fts5PhraseIter> {
-  //! Updated and used only by native code.
-  private long a;
-  private long b;
-}
@@ -1,31 +0,0 @@
-/*
-** 2023-08-05x
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import org.sqlite.jni.NativePointerHolder;
-
-/**
-   INCOMPLETE AND COMPLETELY UNTESTED.
-
-   A wrapper for communicating C-level (Fts5Tokenizer*) instances with
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-
-   At the C level, the Fts5Tokenizer type is essentially a void
-   pointer used specifically for tokenizers.
-*/
-public final class Fts5Tokenizer extends NativePointerHolder<Fts5Tokenizer> {
-  //! Only called from JNI.
-  private Fts5Tokenizer(){}
-}
@@ -1,86 +0,0 @@
-/*
-** 2023-08-04
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file contains a set of tests for the sqlite3 JNI bindings.
-*/
-package org.sqlite.jni.fts5;
-import static org.sqlite.jni.SQLite3Jni.*;
-import static org.sqlite.jni.Tester1.*;
-import org.sqlite.jni.*;
-
-public class TesterFts5 {
-
-  private static void test1(){
-    final Fts5ExtensionApi fea = Fts5ExtensionApi.getInstance();
-    affirm( null != fea );
-    affirm( fea.getNativePointer() != 0 );
-    affirm( fea == Fts5ExtensionApi.getInstance() )/*singleton*/;
-
-    sqlite3 db = createNewDb();
-    fts5_api fApi = fts5_api.getInstanceForDb(db);
-    affirm( fApi != null );
-    affirm( fApi == fts5_api.getInstanceForDb(db) /* singleton per db */ );
-
-    execSql(db, new String[] {
-        "CREATE VIRTUAL TABLE ft USING fts5(a, b);",
-        "INSERT INTO ft(rowid, a, b) VALUES(1, 'X Y', 'Y Z');",
-        "INSERT INTO ft(rowid, a, b) VALUES(2, 'A Z', 'Y Y');"
-      });
-
-    final String pUserData = "This is pUserData";
-    final int outputs[] = {0, 0};
-    final fts5_extension_function func = new fts5_extension_function(){
-        @Override public void call(Fts5ExtensionApi ext, Fts5Context fCx,
-                                   sqlite3_context pCx, sqlite3_value argv[]){
-          final int nCols = ext.xColumnCount(fCx);
-          affirm( 2 == nCols );
-          affirm( nCols == argv.length );
-          affirm( ext.xUserData(fCx) == pUserData );
-          final OutputPointer.String op = new OutputPointer.String();
-          final OutputPointer.Int32 colsz = new OutputPointer.Int32();
-          final OutputPointer.Int64 colTotalSz = new OutputPointer.Int64();
-          for(int i = 0; i < nCols; ++i ){
-            int rc = ext.xColumnText(fCx, i, op);
-            affirm( 0 == rc );
-            final String val = op.value;
-            affirm( val.equals(sqlite3_value_text16(argv[i])) );
-            rc = ext.xColumnSize(fCx, i, colsz);
-            affirm( 0==rc );
-            affirm( 3==sqlite3_value_bytes(argv[i]) );
-            rc = ext.xColumnTotalSize(fCx, i, colTotalSz);
-            affirm( 0==rc );
-          }
-          ++outputs[0];
-        }
-        public void xDestroy(){
-          outputs[1] = 1;
-        }
-      };
-
-    int rc = fApi.xCreateFunction("myaux", pUserData, func);
-    affirm( 0==rc );
-
-    affirm( 0==outputs[0] );
-    execSql(db, "select myaux(ft,a,b) from ft;");
-    affirm( 2==outputs[0] );
-    affirm( 0==outputs[1] );
-    sqlite3_close_v2(db);
-    affirm( 1==outputs[1] );
-  }
-
-  private static synchronized void runTests(){
-    test1();
-  }
-
-  public TesterFts5(){
-    runTests();
-  }
-}
@@ -1,79 +0,0 @@
-/*
-** 2023-08-05
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import org.sqlite.jni.annotation.*;
-import org.sqlite.jni.*;
-
-/**
-   INCOMPLETE AND COMPLETELY UNTESTED.
-
-   A wrapper for communicating C-level (fts5_api*) instances with
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-*/
-public final class fts5_api extends NativePointerHolder<fts5_api> {
-  /* Only invoked from JNI */
-  private fts5_api(){}
-
-  public static final int iVersion = 2;
-
-  /**
-     Returns the fts5_api instance associated with the given db, or
-     null if something goes horribly wrong.
-  */
-  public static synchronized native fts5_api getInstanceForDb(@NotNull sqlite3 db);
-
-  @Canonical
-  public synchronized native int xCreateFunction(@NotNull String name,
-                                                 @Nullable Object userData,
-                                                 @NotNull fts5_extension_function xFunction);
-
-  /**
-     Convenience overload which passes null as the 2nd argument to the
-     3-parameter form.
-  */
-  public int xCreateFunction(@NotNull String name,
-                             @NotNull fts5_extension_function xFunction){
-    return xCreateFunction(name, null, xFunction);
-  }
-
-  // /* Create a new auxiliary function */
-  // int (*xCreateFunction)(
-  //   fts5_api *pApi,
-  //   const char *zName,
-  //   void *pContext,
-  //   fts5_extension_function xFunction,
-  //   void (*xDestroy)(void*)
-  // );
-
-  // Still potentially todo:
-
-  // int (*xCreateTokenizer)(
-  //   fts5_api *pApi,
-  //   const char *zName,
-  //   void *pContext,
-  //   fts5_tokenizer *pTokenizer,
-  //   void (*xDestroy)(void*)
-  // );
-
-  // /* Find an existing tokenizer */
-  // int (*xFindTokenizer)(
-  //   fts5_api *pApi,
-  //   const char *zName,
-  //   void **ppContext,
-  //   fts5_tokenizer *pTokenizer
-  // );
-
-}
@@ -1,47 +0,0 @@
-/*
-** 2023-08-05
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import org.sqlite.jni.sqlite3_context;
-import org.sqlite.jni.sqlite3_value;
-
-/**
-   JNI-level wrapper for C's fts5_extension_function type.
-*/
-public interface fts5_extension_function {
-  // typedef void (*fts5_extension_function)(
-  //   const Fts5ExtensionApi *pApi,   /* API offered by current FTS version */
-  //   Fts5Context *pFts,              /* First arg to pass to pApi functions */
-  //   sqlite3_context *pCtx,          /* Context for returning result/error */
-  //   int nVal,                       /* Number of values in apVal[] array */
-  //   sqlite3_value **apVal           /* Array of trailing arguments */
-  // );
-
-  /**
-     The callback implementation, corresponding to the xFunction
-     argument of C's fts5_api::xCreateFunction().
-  */
-  void call(Fts5ExtensionApi ext, Fts5Context fCx,
-            sqlite3_context pCx, sqlite3_value argv[]);
-  /**
-     Is called when this function is destroyed by sqlite3. Typically
-     this function will be empty.
-  */
-  void xDestroy();
-
-  public static abstract class Abstract implements fts5_extension_function {
-    @Override public abstract void call(Fts5ExtensionApi ext, Fts5Context fCx,
-                                        sqlite3_context pCx, sqlite3_value argv[]);
-    @Override public void xDestroy(){}
-  }
-}
@@ -1,51 +0,0 @@
-/*
-** 2023-08-05
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni.fts5;
-import org.sqlite.jni.NativePointerHolder;
-import org.sqlite.jni.annotation.NotNull;
-
-/**
-   INCOMPLETE AND COMPLETELY UNTESTED.
-
-   A wrapper for communicating C-level (fts5_tokenizer*) instances with
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-*/
-public final class fts5_tokenizer extends NativePointerHolder<fts5_tokenizer> {
-  /* Only invoked by JNI */
-  private fts5_tokenizer(){}
-
-  // int (*xCreate)(void*, const char **azArg, int nArg, Fts5Tokenizer **ppOut);
-  // void (*xDelete)(Fts5Tokenizer*);
-
-  public native int xTokenize(@NotNull Fts5Tokenizer t, int tokFlags,
-                              @NotNull byte pText[],
-                              @NotNull Fts5.XTokenizeCallback callback);
-
-
-  // int (*xTokenize)(Fts5Tokenizer*,
-  //     void *pCtx,
-  //     int flags,            /* Mask of FTS5_TOKENIZE_* flags */
-  //     const char *pText, int nText,
-  //     int (*xToken)(
-  //       void *pCtx,         /* Copy of 2nd argument to xTokenize() */
-  //       int tflags,         /* Mask of FTS5_TOKEN_* flags */
-  //       const char *pToken, /* Pointer to buffer containing token */
-  //       int nToken,         /* Size of token in bytes */
-  //       int iStart,         /* Byte offset of token within input text */
-  //       int iEnd            /* Byte offset of end of token within input text */
-  //     )
-  // );
-}
@@ -1,89 +0,0 @@
-/**
-   This package houses a JNI binding to the SQLite3 C API.
-
-   <p>The primary interfaces are in {@link
-   org.sqlite.jni.SQLite3Jni}.</p>
-
-   <h1>API Goals and Requirements</h1>
-
-   <ul>
-
-     <li>A 1-to-1(-ish) mapping of the C API to Java via JNI, insofar
-     as cross-language semantics allow for. A closely-related goal is
-     that <a href='https://sqlite.org/c3ref/intro.html'>the C
-     documentation</a> should be usable as-is, insofar as possible,
-     for most of the JNI binding. As a rule, undocumented symbols in
-     the Java interface behave as documented for their C API
-     counterpart. Only semantic differences and Java-specific features
-     are documented here.</li>
-
-     <li>Support Java as far back as version 8 (2014).</li>
-
-     <li>Environment-independent. Should work everywhere both Java and
-     SQLite3 do.</li>
-
-     <li>No 3rd-party dependencies beyond the JDK. That includes no
-     build-level dependencies for specific IDEs and toolchains.  We
-     welcome the addition of build files for arbitrary environments
-     insofar as they neither interfere with each other nor become a
-     maintenance burden for the sqlite developers.</li>
-
-  </ul>
-
-  <h2>Non-Goals</h2>
-
-  <ul>
-
-    <li>Creation of high-level OO wrapper APIs. Clients are free to
-    create them off of the C-style API.</li>
-
-    <li>Support for mixed-mode operation, where client code accesses
-    SQLite both via the Java-side API and the C API via their own
-    native code. In such cases, proxy functionalities (primarily
-    callback handler wrappers of all sorts) may fail because the
-    C-side use of the SQLite APIs will bypass those proxies.</li>
-
-  </ul>
-
-   <h1>State of this API</h1>
-
-   <p>As of version 3.43, this software is in "tech preview" form. We
-   tentatively plan to stamp it as stable with the 3.44 release.</p>
-
-   <h1>Threading Considerations</h1>
-
-   <p>This API is, if built with SQLITE_THREADSAFE set to 1 or 2,
-   thread-safe, insofar as the C API guarantees, with some addenda:</p>
-
-   <ul>
-
-     <li>It is not legal to use Java-facing SQLite3 resource handles
-     (sqlite3, sqlite3_stmt, etc) from multiple threads concurrently,
-     nor to use any database-specific resources concurrently in a
-     thread separate from the one the database is currently in use
-     in. i.e. do not use a sqlite3_stmt in thread #2 when thread #1 is
-     using the database which prepared that handle.
-
-     <br>Violating this will eventually corrupt the JNI-level bindings
-     between Java's and C's view of the database. This is a limitation
-     of the JNI bindings, not the lower-level library.
-     </li>
-
-     <li>It is legal to use a given handle, and database-specific
-     resources, across threads, so long as no two threads pass
-     resources owned by the same database into the library
-     concurrently.
-     </li>
-
-   </ul>
-
-   <p>Any number of threads may, of course, create and use any number
-   of database handles they wish. Care only needs to be taken when
-   those handles or their associated resources cross threads, or...</p>
-
-   <p>When built with SQLITE_THREADSAFE=0 then no threading guarantees
-   are provided and multi-threaded use of the library will provoke
-   undefined behavior.</p>
-
-*/
-package org.sqlite.jni;
@@ -1,37 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A wrapper for communicating C-level (sqlite3*) instances with
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java
-   and C via JNI.
-*/
-public final class sqlite3 extends NativePointerHolder<sqlite3> {
-  // Only invoked from JNI
-  private sqlite3(){}
-
-  public String toString(){
-    long ptr = getNativePointer();
-    if( 0==ptr ){
-      return sqlite3.class.getSimpleName()+"@null";
-    }
-    String fn = SQLite3Jni.sqlite3_db_filename(this, "main");
-    return sqlite3.class.getSimpleName()
-      +"@"+String.format("0x%08x",ptr)
-      +"["+((null == fn) ? "<unnamed>" : fn)+"]"
-      ;
-  }
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-09-03
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A wrapper for passing C-level (sqlite3_backup*) instances around in
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-*/
-public final class sqlite3_backup extends NativePointerHolder<sqlite3_backup> {
-  // Only invoked from JNI.
-  private sqlite3_backup(){}
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-09-03
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A wrapper for passing C-level (sqlite3_blob*) instances around in
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-*/
-public final class sqlite3_blob extends NativePointerHolder<sqlite3_blob> {
-  // Only invoked from JNI.
-  private sqlite3_blob(){}
-}
@@ -1,79 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   sqlite3_context instances are used in conjunction with user-defined
-   SQL functions (a.k.a. UDFs).
-*/
-public final class sqlite3_context extends NativePointerHolder<sqlite3_context> {
-  private Long aggregateContext = null;
-
-  /**
-     getAggregateContext() corresponds to C's
-     sqlite3_aggregate_context(), with a slightly different interface
-     to account for cross-language differences. It serves the same
-     purposes in a slightly different way: it provides a key which is
-     stable across invocations of a UDF's callbacks, such that all
-     calls into those callbacks can determine which "set" of those
-     calls they belong to.
-
-     <p>Note that use of this method is not a requirement for proper use
-     of this class. sqlite3_aggregate_context() can also be used.
-
-     <p>If the argument is true and the aggregate context has not yet
-     been set up, it will be initialized and fetched on demand, else it
-     won't. The intent is that xStep(), xValue(), and xInverse()
-     methods pass true and xFinal() methods pass false.
-
-     <p>This function treats numeric 0 as null, always returning null instead
-     of 0.
-
-     <p>If this object is being used in the context of an aggregate or
-     window UDF, this function returns a non-0 value which is distinct
-     for each set of UDF callbacks from a single invocation of the
-     UDF, otherwise it returns 0. The returned value is only only
-     valid within the context of execution of a single SQL statement,
-     and must not be re-used by future invocations of the UDF in
-     different SQL statements.
-
-     <p>Consider this SQL, where MYFUNC is a user-defined aggregate function:
-
-     <pre>{@code
-     SELECT MYFUNC(A), MYFUNC(B) FROM T;
-     }</pre>
-
-     <p>The xStep() and xFinal() methods of the callback need to be able
-     to differentiate between those two invocations in order to
-     perform their work properly. The value returned by
-     getAggregateContext() will be distinct for each of those
-     invocations of MYFUNC() and is intended to be used as a lookup
-     key for mapping callback invocations to whatever client-defined
-     state is needed by the UDF.
-
-     <p>There is one case where this will return null in the context
-     of an aggregate or window function: if the result set has no
-     rows, the UDF's xFinal() will be called without any other x...()
-     members having been called. In that one case, no aggregate
-     context key will have been generated. xFinal() implementations
-     need to be prepared to accept that condition as legal.
-  */
-  public synchronized Long getAggregateContext(boolean initIfNeeded){
-      if( aggregateContext==null ){
-        aggregateContext = SQLite3Jni.sqlite3_aggregate_context(this, initIfNeeded);
-        if( !initIfNeeded && null==aggregateContext ) aggregateContext = 0L;
-      }
-      return (null==aggregateContext || 0!=aggregateContext) ? aggregateContext : null;
-  }
-}
@@ -1,25 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-/**
-   A wrapper for communicating C-level (sqlite3_stmt*) instances with
-   Java. These wrappers do not own their associated pointer, they
-   simply provide a type-safe way to communicate it between Java and C
-   via JNI.
-*/
-public final class sqlite3_stmt extends NativePointerHolder<sqlite3_stmt> {
-  // Only invoked from JNI.
-  private sqlite3_stmt(){}
-}
@@ -1,19 +0,0 @@
-/*
-** 2023-07-21
-**
-** The author disclaims copyright to this source code.  In place of
-** a legal notice, here is a blessing:
-**
-**    May you do good and not evil.
-**    May you find forgiveness for yourself and forgive others.
-**    May you share freely, never taking more than you give.
-**
-*************************************************************************
-** This file is part of the JNI bindings for the sqlite3 C API.
-*/
-package org.sqlite.jni;
-
-public final class sqlite3_value extends NativePointerHolder<sqlite3_value> {
-  //! Invoked only from JNI.
-  private sqlite3_value(){}
-}
@@ -1,269 +0,0 @@
-# Specifications For A Rudimentary SQLite Test Script Interpreter
-
-## Overview
-
-The purpose of the Test Script Interpreter is to read and interpret
-script files that contain SQL commands and desired results.  The
-interpreter will check results and report an discrepencies found.
-
-The test script files are ASCII text files.  The filename always ends with
-".test".  Each script is evaluated independently; context does not carry
-forward from one script to the next.  So, for example, the --null command
-run in one test script does not cause any changes in the behavior of
-subsequent test scripts.  All open database connections are closed
-at the end of each test script.  All database files created by a test
-script are deleted when the script finishes.
-
-## Parsing Rules:
-
-  1.   The test script is read line by line, where a line is a sequence of
-       characters that runs up to the next '\\n' (0x0a) character or until
-       the end of the file.  There is never a need to read ahead past the
-       end of the current line.
-
-  2.   If any line contains the string " MODULE_NAME:" (with a space before
-       the initial "M") or "MIXED_MODULE_NAME:" then that test script is
-       incompatible with this spec.  Processing of the test script should
-       end immediately.  There is no need to read any more of the file.
-       In verbose mode, the interpreter might choose to emit an informational
-       messages saying that the test script was abandoned due to an
-       incompatible module type.
-
-  3.   If any line contains the string "SCRIPT_MODULE_NAME:" then the input
-       script is known to be of the correct type for this specification and
-       processing may continue.  The "MODULE_NAME" checking in steps 2 and 3
-       may optionally be discontinued after sighting a "SCRIPT_MODULE_NAME".
-
-  4.   If any line contains "REQUIRED_PROPERTIES:" and that substring is followed
-       by any non-whitespace text, then the script is not compatible with this
-       spec.  Processing should stop immediately.  In verbose mode, the
-       interpreter might choose to emit an information message saying that the
-       test script was abandoned due to unsupported requirement properties.
-
-  5.   If any line begins with the "\|" (0x7c) character, that indicates that
-       the input script is not compatible with this specification.  Processing
-       of the script should stop immediately.  In verbose mode, the interpreter
-       might choose to emit an informational message indicating that the
-       test script was abandoned because it contained "a dbtotxt format database
-       specification".
-
-  6.   Any line that begins with "#" is a C-preprocessor line.  The interpreter
-       described by this spec does not know how to deal with C-preprocessor lines.
-       Hence, processing should be abandoned.  In verbose mode, the interpreter
-       might emit an informational message similar to
-       "script NAME abandoned due to C-preprocessor line: ..."
-
-  7.   If a line begins with exactly two minus signs followed by a
-       lowercase letter, that is a command.  Process commands as described
-       below.
-
-  8.   All other lines should be accumulated into the "input buffer".
-       The various commands will have access to this input buffer.
-       Some commands will reset the buffer.
-
-## Initialization
-
-The initial state of the interpreter at the start of processing each script
-is as if the following command sequence had been run:
-
-> ~~~
--close all
--db 0
--new test.db
--null nil
-~~~
-
-In words, all database connections are closed except for connection 0 (the
-default) which is open on an empty database named "test.db".  The string
-"nil" is displayed for NULL column values.
-
-The only context carried forward after the evaluation of one test script
-into the evaluation of the next test script is the count of the number of
-tests run and the number of failures seen.
-
-## Commands:
-
-Each command looks like an SQL comment.  The command begins at the left
-margin (no leading space) and starts with exactly 2 minus signs ("-").
-The command name consists of lowercase letters and maybe a "-" or two.
-Some commands have arguments.
-The arguments are separated from the command name by one or more spaces.
-
-Commands have access to the input buffer and might reset the input buffer.
-The command can also optionally read (and consume) additional text from
-script that comes after the command.
-
-Unknown or unrecognized commands indicate that the script contains features
-that are not (yet) supported by this specification.  Processing of the
-script should terminate immediately.  When this happens and when the
-interpreter is in a "verbose" mode, the interpreter might choose to emit
-an informational message along the lines of "test script NAME abandoned
-due to unsupported command: --whatever".
-
-The initial implemention will only recognize a few commands.  Other
-commands may be added later.  The following is the initial set of
-commands:
-
-### The --testcase command
-
-Every test case starts with a --testcase command.  The --testcase
-command resets both the "input buffer" and the "result buffer".  The
-argument to the --testcase command is the name of the test case.  That
-test case name is used for logging and debugging and when printing
-errors. The input buffer is set to the body of the test case.
-
-### The --result command
-
-The --result command tries to execute the text in the input buffer as SQL.
-For each row of result coming out of this SQL, the text of that result is
-appended to the "result buffer".  If a result row contains multiple columns,
-the columns are processed from left to right.  For each column, text is
-appended to the result buffer according to the following rules:
-
-  *   If the result buffer already contains some text, append a space.
-      (In this way, all column values and all row values are separated from
-      each other by a single space.)
-
-  *   If sqlite3_column_text() returns NULL, then append "nil" - or
-      some other text that is specified by the --null command - and skip
-      all subsequent rules.
-
-  *   If sqlite3_column_text() is an empty string, append `{}` to the
-      result buffer and skip all subsequent rules.
-
-  *   If sqlite3_column_text() does not contain any special
-      characters, append it to the result buffer without any
-      formatting and skip all subsequent rules. Special characters are:
-      0x00 to 0x20 (inclusive), double-quote (0x22), backslash (0x5c),
-      curly braces (0x7b and 0x7d).
-
-  *   If sqlite3_column_text() does not contains curly braces, then put
-      the text inside of `{...}` and append it and skip all subsequent rules.
-
-  *   Append the text within double-quotes (`"..."`) and within the text
-      escape '"' and '\\' by prepending a single '\\' and escape any
-      control characters (characters less than 0x20) using octal notation:
-      '\\NNN'.
-
-If an error is encountered while running the SQL, then append the
-symbolic C-preprocessor name for the error
-code (ex: "SQLITE_CONSTRAINT") as if it were a column value.  Then append
-the error message text as if it where a column value.  Then stop processing.
-
-After the SQL text has been run, compare the content of the result buffer
-against the argument to the --result command and report a testing error if
-there are any differences.
-
-The --result command resets the input buffer, but it does not reset
-the result buffer.  This distinction does not matter for the --result
-command itself, but it is important for related commands like --glob
-and --notglob.  Sometimes test cases will contains a bunch of SQL
-followed by multiple --glob and/or --notglob statements.  All of the
-globs should be evaluted agains the result buffer correct, but the SQL
-should only be run once.  This is accomplished by resetting the input
-buffer but not the result buffer.
-
-### The --glob command
-
-The --glob command works just like --result except that the argument to
--glob is interpreted as a TEST-GLOB pattern and the results are compared
-using that glob pattern rather than using strcmp().  Other than that,
-the two operate the same.
-
-The TEST-GLOB pattern is slightly different for a standard GLOB:
-
-   *    The '*' character matches zero or more characters.
-
-   *    The '?' character matches any single character
-
-   *    The '[...]' character sequence machines a single character
-        in between the brackets.
-
-   *    The '#' character matches one or more digits  (This is the main
-        difference between standard unix-glob and TEST-GLOB.  unix-glob
-        does not have this feature.  It was added to because it comes
-        up a lot during SQLite testing.)
-
-### The --notglob command
-
-The --notglob command works just like --glob except that it reports an
-error if the GLOB does match, rather than if the GLOB does not matches.
-
-### The --oom command
-
-This command is to be used for out-of-memory testing.  It means that
-OOM errors should be simulated to ensure that SQLite is able to deal with
-them.  This command can be silently ignored for now.  We might add support
-for this later.
-
-### The --tableresult command
-
-The --tableresult command works like --glob except that the GLOB pattern
-to be matched is taken from subsequent lines of the input script up to
-the next --end.  Every span of one or more whitespace characters in this
-pattern text is collapsed into a single space (0x20).
-Leading and trailing whitespace are removed from the pattern.
-The --end that ends the GLOB pattern is not part of the GLOB pattern, but
-the --end is consumed from the script input.
-
-### The --new and --open commands
-
-The --new and --open commands cause a database file to be opened.
-The name of the file is the argument to the command.  The --new command
-opens an initially empty database (it deletes the file before opening it)
-whereas the --open command opens an existing database if it already
-exists.
-
-### The --db command
-
-The script interpreter can have up to 7 different SQLite database
-connections open at a time.  The --db command is used to switch between
-them.  The argument to --db is an integer between 0 and 6 that selects
-which database connection to use moving forward.
-
-### The --close command
-
-The --close command causes an existing database connection to close.
-This command is a no-op if the database connection is not currently
-open.  There can be up to 7 different database connections, numbered 0
-through 6.  The number of the database connection to close is an
-argument to the --close command, which will fail if an out-of-range
-value is provided.  Or if the argument to --close is "all" then all
-open database connections are closed. If passed no argument, the
-currently-active database is assumed.
-
-### The --null command
-
-The NULL command changes the text that is used to represent SQL NULL
-values in the result buffer.
-
-### The --run command
-
-The --run command executes text in the input buffer as if it where SQL.
-However, nothing is added to the result buffer.  Any output from the SQL
-is silently ignored. Errors in the SQL are silently ignored.
-
-The --run command normally executes the SQL in the current database
-connection.  However, if --run has an argument that is an integer between
-0 and 6 then the SQL is run in the alternative database connection specified
-by that argument.
-
-### The --json and --json-block commands
-
-The --json and --json-block commands work like --result and --tableresult,
-respectively.  The difference is that column values are appended to the
-result buffer literally, without ever enclosing the values in `{...}` or
-`"..."` and without escaping any characters in the column value and comparison
-is always an exact strcmp() not a GLOB.
-
-### The --print command
-
-The --print command emits both its arguments and its body (if any) to
-stdout, indenting each line of output.
-
-### The --column-names command
-
-The --column-names command requires 0 or 1 as an argument, to disable
-resp.  enable it, and modifies SQL execution to include column names
-in output. When this option is on, each column value emitted gets
-prefixed by its column name, with a single space between them.
@@ -1,53 +0,0 @@
-/*
-** This is a comment. There are many like it but this one is mine.
-**
-** SCRIPT_MODULE_NAME:      sanity-check
-** xMIXED_MODULE_NAME:       mixed-module
-** xMODULE_NAME:             module-name
-** xREQUIRED_PROPERTIES:      small fast reliable
-** xREQUIRED_PROPERTIES:      RECURSIVE_TRIGGERS
-** xREQUIRED_PROPERTIES:      TEMPSTORE_FILE TEMPSTORE_MEM
-** xREQUIRED_PROPERTIES:      AUTOVACUUM INCRVACUUM
-**
-*/
--print starting up 😃
--close all
--oom
--db 0
--new my.db
--null zilch
--testcase 1.0
-SELECT 1, null;
--result 1 zilch
--glob *zil*
--notglob *ZIL*
-SELECT 1, 2;
-intentional error;
--run
--testcase json-1
-SELECT json_array(1,2,3)
--json [1,2,3]
--testcase tableresult-1
-  select 1, 'a';
-  select 2, 'b';
--tableresult
-  # [a-z]
-  2 b
--end
--testcase json-block-1
-  select json_array(1,2,3);
-  select json_object('a',1,'b',2);
--json-block
-  [1,2,3]
-  {"a":1,"b":2}
--end
--testcase col-names-on
--column-names 1
-  select 1 as 'a', 2 as 'b';
--result a 1 b 2
--testcase col-names-off
--column-names 0
-  select 1 as 'a', 2 as 'b';
--result 1 2
--close
--print reached the end 😃
@@ -1,9 +0,0 @@
-/*
-** This script must be marked as ignored because it contains
-** content which triggers that condition.
-**
-** SCRIPT_MODULE_NAME:        ignored
-**
-*/
-
-|
@@ -1,12 +0,0 @@
-/*
-** SCRIPT_MODULE_NAME:      fts5-sanity-checks
-** xREQUIRED_PROPERTIES:     FTS5
-**
-*/
-
--testcase 1.0
-CREATE VIRTUAL TABLE email USING fts5(sender, title, body);
-insert into email values('fred','Help!','Dear Sir...');
-insert into email values('barney','Assistance','Dear Madam...');
-select * from email where email match 'assistance';
--result barney Assistance {Dear Madam...}
@@ -642,7 +642,7 @@ static Decimal *decimalFromDouble(double r){

 /*
 ** SQL Function:   decimal(X)
-** OR:             decimal_exp(X)
+** OR:             decimal_sci(X)
 **
 ** Convert input X into decimal and then back into text.
 **
@@ -650,7 +650,7 @@ static Decimal *decimalFromDouble(double r){
 ** point value is done.  Or if X is an 8-byte blob, it is interpreted
 ** as a float and similarly expanded.
 **
-** The decimal_exp(X) function returns the result in exponential notation.
+** The decimal_sci(X) function returns the result in scientific notation.
 ** decimal(X) returns a complete decimal, without the e+NNN at the end.
 */
 static void decimalFunc(
@@ -853,7 +853,7 @@ int sqlite3_decimal_init(
    void (*xFunc)(sqlite3_context*,int,sqlite3_value**);
  } aFunc[] = {
    { "decimal",       1, 0,  decimalFunc        },
-    { "decimal_exp",   1, 1,  decimalFunc        },
+    { "decimal_sci",   1, 1,  decimalFunc        },
    { "decimal_cmp",   2, 0,  decimalCmpFunc     },
    { "decimal_add",   2, 0,  decimalAddFunc     },
    { "decimal_sub",   2, 0,  decimalSubFunc     },
@@ -475,20 +475,15 @@ struct RtreeMatchArg {
 ** -DSQLITE_RUNTIME_BYTEORDER=1 is set, then byte-order is determined
 ** at run-time.
 */
-#ifndef SQLITE_BYTEORDER /* Replicate changes at tag-20230904a */
-# if defined(__BYTE_ORDER__) && __BYTE_ORDER__==__ORDER_BIG_ENDIAN__
-#   define SQLITE_BYTEORDER 4321
-# elif defined(__BYTE_ORDER__) && __BYTE_ORDER__==__ORDER_LITTLE_ENDIAN__
-#   define SQLITE_BYTEORDER 1234
-# elif defined(__BIG_ENDIAN__) && __BIG_ENDIAN__==1
-#   define SQLITE_BYTEORDER 4321
-# elif defined(i386)    || defined(__i386__)      || defined(_M_IX86) ||    \
+#ifndef SQLITE_BYTEORDER
+# if defined(i386)      || defined(__i386__)      || defined(_M_IX86) ||    \
     defined(__x86_64)  || defined(__x86_64__)    || defined(_M_X64)  ||    \
     defined(_M_AMD64)  || defined(_M_ARM)        || defined(__x86)   ||    \
     defined(__ARMEL__) || defined(__AARCH64EL__) || defined(_M_ARM64)
-#   define SQLITE_BYTEORDER 1234
-# elif defined(sparc)   || defined(__ARMEB__)     || defined(__AARCH64EB__)
-#   define SQLITE_BYTEORDER 4321
+#   define SQLITE_BYTEORDER    1234
+# elif defined(sparc)     || defined(__ppc__) || \
+       defined(__ARMEB__) || defined(__AARCH64EB__)
+#   define SQLITE_BYTEORDER    4321
 # else
 #   define SQLITE_BYTEORDER 0
 # endif
@@ -1924,7 +1919,7 @@ static int rtreeFilter(
 #else
            p->u.rValue = (double)iVal;
            if( iVal>=((sqlite3_int64)1)<<48
-             || iVal<=-(((sqlite3_int64)1)<<48)
+             || -iVal>=((sqlite3_int64)1)<<48
            ){
              if( p->op==RTREE_LT ) p->op = RTREE_LE;
              if( p->op==RTREE_GT ) p->op = RTREE_GE;
@@ -3502,11 +3497,8 @@ static int rtreeShadowName(const char *zName){
  return 0;
 }

-/* Forward declaration */
-static int rtreeIntegrity(sqlite3_vtab*, char**);
-
 static sqlite3_module rtreeModule = {
-  4,                          /* iVersion */
+  3,                          /* iVersion */
  rtreeCreate,                /* xCreate - create a table */
  rtreeConnect,               /* xConnect - connect to an existing table */
  rtreeBestIndex,             /* xBestIndex - Determine search strategy */
@@ -3529,8 +3521,7 @@ static sqlite3_module rtreeModule = {
  rtreeSavepoint,             /* xSavepoint */
  0,                          /* xRelease */
  0,                          /* xRollbackTo */
-  rtreeShadowName,            /* xShadowName */
-  rtreeIntegrity              /* xIntegrity */
+  rtreeShadowName             /* xShadowName */
 };

 static int rtreeSqlInit(
@@ -4364,20 +4355,6 @@ static int rtreeCheckTable(
  return check.rc;
 }

-/*
-** Implementation of the xIntegrity method for Rtree.
-*/
-static int rtreeIntegrity(sqlite3_vtab *pVtab, char **pzErr){
-  Rtree *pRtree = (Rtree*)pVtab;
-  int rc;
-  rc = rtreeCheckTable(pRtree->db, pRtree->zDb, pRtree->zName, pzErr);
-  if( rc==SQLITE_OK && *pzErr ){
-    *pzErr = sqlite3_mprintf("In RTree %s.%s:\n%z",
-                 pRtree->zDb, pRtree->zName, *pzErr);
-  }
-  return rc;
-}
-
 /*
 ** Usage:
 **
@@ -192,6 +192,6 @@ proc rtree_treedump {db zTab} {
 }

 proc do_rtree_integrity_test {tn tbl} {
-  uplevel [list do_execsql_test $tn.1 "SELECT rtreecheck('$tbl')" ok]
-  uplevel [list do_execsql_test $tn.2 "PRAGMA integrity_check" ok]
+  uplevel [list do_execsql_test $tn "SELECT rtreecheck('$tbl')" ok]
 }
+
@@ -78,11 +78,6 @@ do_execsql_test 2.3 {
  SELECT rtreecheck('r1') 
 } {{Dimension 0 of cell 0 on node 1 is corrupt
 Dimension 1 of cell 3 on node 1 is corrupt}}
-do_execsql_test 2.3b { 
-  PRAGMA integrity_check;
-} {{In RTree main.r1:
-Dimension 0 of cell 0 on node 1 is corrupt
-Dimension 1 of cell 3 on node 1 is corrupt}}

 setup_simple_db
 do_execsql_test 2.4 {
@@ -90,21 +85,12 @@ do_execsql_test 2.4 {
  SELECT rtreecheck('r1') 
 } {{Mapping (3 -> 1) missing from %_rowid table
 Wrong number of entries in %_rowid table - expected 5, actual 4}}
-do_execsql_test 2.4b {
-  PRAGMA integrity_check
-} {{In RTree main.r1:
-Mapping (3 -> 1) missing from %_rowid table
-Wrong number of entries in %_rowid table - expected 5, actual 4}}

 setup_simple_db
 do_execsql_test 2.5 {
  UPDATE r1_rowid SET nodeno=2 WHERE rowid=3;
  SELECT rtreecheck('r1') 
 } {{Found (3 -> 2) in %_rowid table, expected (3 -> 1)}}
-do_execsql_test 2.5b {
-  PRAGMA integrity_check
-} {{In RTree main.r1:
-Found (3 -> 2) in %_rowid table, expected (3 -> 1)}}

 reset_db
 do_execsql_test 3.0 { 
@@ -118,16 +104,14 @@ do_execsql_test 3.0 {
  INSERT INTO r1 VALUES(7, 5, 0x00000080);
  INSERT INTO r1 VALUES(8, 5, 0x40490fdb);
  INSERT INTO r1 VALUES(9, 0x7f800000, 0x7f900000);
-  SELECT rtreecheck('r1');
-  PRAGMA integrity_check;
-} {ok ok}
+  SELECT rtreecheck('r1') 
+} {ok}

 do_execsql_test 3.1 { 
  CREATE VIRTUAL TABLE r2 USING rtree_i32(id, x1, x2);
  INSERT INTO r2 VALUES(2, -1*(1<<31), -1*(1<<31)+5);
-  SELECT rtreecheck('r2');
-  PRAGMA integrity_check;
-} {ok ok}
+  SELECT rtreecheck('r2') 
+} {ok}

 sqlite3_db_config db DEFENSIVE 0
 do_execsql_test 3.2 {
@@ -141,11 +125,6 @@ do_execsql_test 3.3 {
  UPDATE r2_node SET data = X'00001234';
  SELECT rtreecheck('r2')!='ok';
 } {1}
-do_execsql_test 3.4 {
-  PRAGMA integrity_check;
-} {{In RTree main.r2:
-Node 1 is too small for cell count of 4660 (4 bytes)
-Wrong number of entries in %_rowid table - expected 0, actual 1}}

 do_execsql_test 4.0 {
  CREATE TABLE notanrtree(i);
@@ -202,3 +181,4 @@ if {[permutation]=="inmemory_journal"} {
 }

 finish_test
+
@@ -3236,19 +3236,15 @@ static int sessionReadRecord(
        }
      }
      if( eType==SQLITE_INTEGER || eType==SQLITE_FLOAT ){
-        if( (pIn->nData-pIn->iNext)<8 ){
-          rc = SQLITE_CORRUPT_BKPT;
+        sqlite3_int64 v = sessionGetI64(aVal);
+        if( eType==SQLITE_INTEGER ){
+          sqlite3VdbeMemSetInt64(apOut[i], v);
        }else{
-          sqlite3_int64 v = sessionGetI64(aVal);
-          if( eType==SQLITE_INTEGER ){
-            sqlite3VdbeMemSetInt64(apOut[i], v);
-          }else{
-            double d;
-            memcpy(&d, &v, 8);
-            sqlite3VdbeMemSetDouble(apOut[i], d);
-          }
-          pIn->iNext += 8;
+          double d;
+          memcpy(&d, &v, 8);
+          sqlite3VdbeMemSetDouble(apOut[i], d);
        }
+        pIn->iNext += 8;
      }
    }
  }
--- a/Show More
+++ b/Show More
@@ -1 +1 @@
 .44.0
 .43.0