merge conflicts between 3.43.0 and 3.45.1
This commit is contained in:
parent
9ee89622ee
commit
b9988867a8
|
@ -1,2 +1,8 @@
|
|||
# $NetBSD: README,v 1.1 2016/03/30 21:31:44 christos Exp $
|
||||
To regenerate the man pages, build and run sqlite2mdoc < /usr/include/sqlite3.h
|
||||
# $NetBSD: README,v 1.2 2024/03/01 15:47:58 christos Exp $
|
||||
- Run cleantags to remove RCSID's
|
||||
- To regenerate the man pages, build and run:
|
||||
cd sqlite2man && make &
|
||||
cd man
|
||||
../sqlite2mdoc/sqlite2mdoc < ../dist/sqlite3.h
|
||||
sed -i -e 's/\$Mdocdate\$/Month DD, YYYY/g' *.3
|
||||
[add new man pages, fix sets]
|
||||
|
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
@ -1,4 +1,4 @@
|
|||
# $NetBSD: Makefile,v 1.6 2023/09/04 23:17:24 christos Exp $
|
||||
# $NetBSD: Makefile,v 1.7 2024/03/01 15:47:59 christos Exp $
|
||||
|
||||
.include <bsd.init.mk>
|
||||
|
||||
|
@ -119,6 +119,7 @@ sqlite3_filename_database.3 \
|
|||
sqlite3_finalize.3 \
|
||||
sqlite3_get_autocommit.3 \
|
||||
sqlite3_get_auxdata.3 \
|
||||
sqlite3_get_clientdata.3 \
|
||||
sqlite3_get_table.3 \
|
||||
sqlite3_index_info.3 \
|
||||
sqlite3_initialize.3 \
|
||||
|
@ -226,6 +227,7 @@ sqlite3changegroup_add.3 \
|
|||
sqlite3changegroup_delete.3 \
|
||||
sqlite3changegroup_new.3 \
|
||||
sqlite3changegroup_output.3 \
|
||||
sqlite3changegroup_schema.3 \
|
||||
sqlite3changeset_apply.3 \
|
||||
sqlite3changeset_apply_strm.3 \
|
||||
sqlite3changeset_concat.3 \
|
||||
|
@ -239,6 +241,7 @@ sqlite3changeset_old.3 \
|
|||
sqlite3changeset_op.3 \
|
||||
sqlite3changeset_pk.3 \
|
||||
sqlite3changeset_start.3 \
|
||||
sqlite3changeset_upgrade.3 \
|
||||
sqlite3rebaser_configure.3 \
|
||||
sqlite3rebaser_create.3 \
|
||||
sqlite3rebaser_delete.3 \
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_ACCESS_EXISTS 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,16 +1,18 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CHANGESETAPPLY_NOSAVEPOINT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm SQLITE_CHANGESETAPPLY_NOSAVEPOINT ,
|
||||
.Nm SQLITE_CHANGESETAPPLY_INVERT ,
|
||||
.Nm SQLITE_CHANGESETAPPLY_IGNORENOOP
|
||||
.Nm SQLITE_CHANGESETAPPLY_IGNORENOOP ,
|
||||
.Nm SQLITE_CHANGESETAPPLY_FKNOACTION
|
||||
.Nd flags for sqlite3changeset_apply_v2
|
||||
.Sh SYNOPSIS
|
||||
.In sqlite3.h
|
||||
.Fd #define SQLITE_CHANGESETAPPLY_NOSAVEPOINT
|
||||
.Fd #define SQLITE_CHANGESETAPPLY_INVERT
|
||||
.Fd #define SQLITE_CHANGESETAPPLY_IGNORENOOP
|
||||
.Fd #define SQLITE_CHANGESETAPPLY_FKNOACTION
|
||||
.Sh DESCRIPTION
|
||||
The following flags may passed via the 9th parameter to sqlite3changeset_apply_v2
|
||||
and sqlite3changeset_apply_v2_strm:
|
||||
|
@ -44,13 +46,19 @@ an insert change if all fields of the conflicting row match the row
|
|||
being inserted.
|
||||
.El
|
||||
.Pp
|
||||
.It SQLITE_CHANGESETAPPLY_FKNOACTION
|
||||
If this flag it set, then all foreign key constraints in the target
|
||||
database behave as if they were declared with "ON UPDATE NO ACTION
|
||||
ON DELETE NO ACTION", even if they are actually CASCADE, RESTRICT,
|
||||
SET NULL or SET DEFAULT.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 12033.
|
||||
interface documentation at line 12211.
|
||||
.Bd -literal
|
||||
#define SQLITE_CHANGESETAPPLY_NOSAVEPOINT 0x0001
|
||||
#define SQLITE_CHANGESETAPPLY_INVERT 0x0002
|
||||
#define SQLITE_CHANGESETAPPLY_IGNORENOOP 0x0004
|
||||
#define SQLITE_CHANGESETAPPLY_FKNOACTION 0x0008
|
||||
.Ed
|
||||
.Sh SEE ALSO
|
||||
.Xr sqlite3changeset_apply 3 ,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CHANGESETSTART_INVERT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -17,7 +17,7 @@ before applying it.
|
|||
It is an error to specify this flag with a patchset.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 11359.
|
||||
interface documentation at line 11488.
|
||||
.Bd -literal
|
||||
#define SQLITE_CHANGESETSTART_INVERT 0x0002
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CHANGESET_DATA 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -64,7 +64,7 @@ The results of invoking the sqlite3changeset_conflict() API are undefined.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 12071.
|
||||
interface documentation at line 12256.
|
||||
.Bd -literal
|
||||
#define SQLITE_CHANGESET_DATA 1
|
||||
#define SQLITE_CHANGESET_NOTFOUND 2
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CHANGESET_OMIT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -41,7 +41,7 @@ and the call to sqlite3changeset_apply() returns SQLITE_ABORT.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 12132.
|
||||
interface documentation at line 12317.
|
||||
.Bd -literal
|
||||
#define SQLITE_CHANGESET_OMIT 0
|
||||
#define SQLITE_CHANGESET_REPLACE 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CHECKPOINT_PASSIVE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -24,7 +24,7 @@ documentation for details on the meaning of each of these checkpoint
|
|||
modes.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 9594.
|
||||
interface documentation at line 9706.
|
||||
.Bd -literal
|
||||
#define SQLITE_CHECKPOINT_PASSIVE 0 /* Do as much as possible w/o blocking */
|
||||
#define SQLITE_CHECKPOINT_FULL 1 /* Wait for writers, then checkpoint */
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CONFIG_SINGLETHREAD 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -436,7 +436,7 @@ configured sorter-reference size threshold - then a reference is stored
|
|||
in each sorted record and the required column values loaded from the
|
||||
database as records are returned in sorted order.
|
||||
The default value for this option is to never use this optimization.
|
||||
Specifying a negative value for this option restores the default behaviour.
|
||||
Specifying a negative value for this option restores the default behavior.
|
||||
This option is only available if SQLite is compiled with the SQLITE_ENABLE_SORTER_REFERENCES
|
||||
compile-time option.
|
||||
.It SQLITE_CONFIG_MEMDB_MAXSIZE
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_CREATE_INDEX 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_DBCONFIG_MAINDBNAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -180,7 +180,7 @@ Usually, when a database in wal mode is closed or detached from a database
|
|||
handle, SQLite checks if this will mean that there are now no connections
|
||||
at all to the database.
|
||||
If so, it performs a checkpoint operation before closing the connection.
|
||||
This option may be used to override this behaviour.
|
||||
This option may be used to override this behavior.
|
||||
The first parameter passed to this operation is an integer - positive
|
||||
to disable checkpoints-on-close, or zero (the default) to enable them,
|
||||
and negative to leave the setting unchanged.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_DBSTATUS_LOOKASIDE_USED 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -137,7 +137,7 @@ The highwater mark is always 0.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8540.
|
||||
interface documentation at line 8652.
|
||||
.Bd -literal
|
||||
#define SQLITE_DBSTATUS_LOOKASIDE_USED 0
|
||||
#define SQLITE_DBSTATUS_CACHE_USED 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_DENY 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_DESERIALIZE_FREEONCLOSE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -36,7 +36,7 @@ The SQLITE_DESERIALIZE_READONLY flag means that the deserialized database
|
|||
should be treated as read-only.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10625.
|
||||
interface documentation at line 10754.
|
||||
.Bd -literal
|
||||
#define SQLITE_DESERIALIZE_FREEONCLOSE 1 /* Call sqlite3_free() on close */
|
||||
#define SQLITE_DESERIALIZE_RESIZEABLE 2 /* Resize using sqlite3_realloc64() */
|
||||
|
|
|
@ -1,11 +1,12 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_DETERMINISTIC 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm SQLITE_DETERMINISTIC ,
|
||||
.Nm SQLITE_DIRECTONLY ,
|
||||
.Nm SQLITE_SUBTYPE ,
|
||||
.Nm SQLITE_INNOCUOUS
|
||||
.Nm SQLITE_INNOCUOUS ,
|
||||
.Nm SQLITE_RESULT_SUBTYPE
|
||||
.Nd function flags
|
||||
.Sh SYNOPSIS
|
||||
.In sqlite3.h
|
||||
|
@ -13,6 +14,7 @@
|
|||
.Fd #define SQLITE_DIRECTONLY
|
||||
.Fd #define SQLITE_SUBTYPE
|
||||
.Fd #define SQLITE_INNOCUOUS
|
||||
.Fd #define SQLITE_RESULT_SUBTYPE
|
||||
.Sh DESCRIPTION
|
||||
These constants may be ORed together with the preferred text encoding
|
||||
as the fourth argument to
|
||||
|
@ -78,28 +80,50 @@ application-defined functions unless the function has been carefully
|
|||
audited and found to be free of potentially security-adverse side-effects
|
||||
and information-leaks.
|
||||
.It SQLITE_SUBTYPE
|
||||
The SQLITE_SUBTYPE flag indicates to SQLite that a function may call
|
||||
The SQLITE_SUBTYPE flag indicates to SQLite that a function might call
|
||||
.Fn sqlite3_value_subtype
|
||||
to inspect the sub-types of its arguments.
|
||||
Specifying this flag makes no difference for scalar or aggregate user
|
||||
functions.
|
||||
However, if it is not specified for a user-defined window function,
|
||||
then any sub-types belonging to arguments passed to the window function
|
||||
may be discarded before the window function is called (i.e. sqlite3_value_subtype()
|
||||
will always return 0).
|
||||
This flag instructs SQLite to omit some corner-case optimizations that
|
||||
might disrupt the operation of the
|
||||
.Fn sqlite3_value_subtype
|
||||
function, causing it to return zero rather than the correct subtype().
|
||||
SQL functions that invokes
|
||||
.Fn sqlite3_value_subtype
|
||||
should have this property.
|
||||
If the SQLITE_SUBTYPE property is omitted, then the return value from
|
||||
.Fn sqlite3_value_subtype
|
||||
might sometimes be zero even though a non-zero subtype was specified
|
||||
by the function argument expression.
|
||||
.It SQLITE_RESULT_SUBTYPE
|
||||
The SQLITE_RESULT_SUBTYPE flag indicates to SQLite that a function
|
||||
might call
|
||||
.Fn sqlite3_result_subtype
|
||||
to cause a sub-type to be associated with its result.
|
||||
Every function that invokes
|
||||
.Fn sqlite3_result_subtype
|
||||
should have this property.
|
||||
If it does not, then the call to
|
||||
.Fn sqlite3_result_subtype
|
||||
might become a no-op if the function is used as term in an expression index.
|
||||
On the other hand, SQL functions that never invoke
|
||||
.Fn sqlite3_result_subtype
|
||||
should avoid setting this property, as the purpose of this property
|
||||
is to disable certain optimizations that are incompatible with subtypes.
|
||||
.El
|
||||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5509.
|
||||
interface documentation at line 5513.
|
||||
.Bd -literal
|
||||
#define SQLITE_DETERMINISTIC 0x000000800
|
||||
#define SQLITE_DIRECTONLY 0x000080000
|
||||
#define SQLITE_SUBTYPE 0x000100000
|
||||
#define SQLITE_INNOCUOUS 0x000200000
|
||||
#define SQLITE_RESULT_SUBTYPE 0x001000000
|
||||
.Ed
|
||||
.Sh SEE ALSO
|
||||
.Xr sqlite3_create_function 3 ,
|
||||
.Xr sqlite3_result_subtype 3 ,
|
||||
.Xr sqlite3_value_subtype 3 ,
|
||||
.Xr SQLITE_DBCONFIG_MAINDBNAME 3 ,
|
||||
.Xr SQLITE_UTF8 3
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_ERROR_MISSING_COLLSEQ 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_FCNTL_LOCKSTATE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_INDEX_CONSTRAINT_EQ 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -79,7 +79,7 @@ does not matter (for example because the constraints are numeric) and
|
|||
so the sqlite3_vtab_collation() interface is not commonly needed.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7366.
|
||||
interface documentation at line 7474.
|
||||
.Bd -literal
|
||||
#define SQLITE_INDEX_CONSTRAINT_EQ 2
|
||||
#define SQLITE_INDEX_CONSTRAINT_GT 4
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_INDEX_SCAN_UNIQUE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -12,7 +12,7 @@ Virtual table implementations are allowed to set the sqlite3_index_info.idxFlags
|
|||
field to some combination of these bits.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7357.
|
||||
interface documentation at line 7465.
|
||||
.Bd -literal
|
||||
#define SQLITE_INDEX_SCAN_UNIQUE 1 /* Scan visits at most 1 row */
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_INTEGER 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -40,7 +40,7 @@ Software that links against both SQLite version 2 and SQLite version
|
|||
3 should use SQLITE3_TEXT, not SQLITE_TEXT.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5006.
|
||||
interface documentation at line 5009.
|
||||
.Bd -literal
|
||||
#define SQLITE_INTEGER 1
|
||||
#define SQLITE_FLOAT 2
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_IOCAP_ATOMIC 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_LIMIT_LENGTH 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -73,7 +73,7 @@ may start.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4065.
|
||||
interface documentation at line 4068.
|
||||
.Bd -literal
|
||||
#define SQLITE_LIMIT_LENGTH 0
|
||||
#define SQLITE_LIMIT_SQL_LENGTH 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_LOCK_NONE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_MUTEX_FAST 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -48,7 +48,7 @@ Applications that override the built-in mutex logic must be prepared
|
|||
to accommodate additional static mutexes.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8068.
|
||||
interface documentation at line 8178.
|
||||
.Bd -literal
|
||||
#define SQLITE_MUTEX_FAST 0
|
||||
#define SQLITE_MUTEX_RECURSIVE 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_OK 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_OPEN_READONLY 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_PREPARE_PERSISTENT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -54,7 +54,7 @@ error (error code SQLITE_ERROR) if the statement uses any virtual tables.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4134.
|
||||
interface documentation at line 4137.
|
||||
.Bd -literal
|
||||
#define SQLITE_PREPARE_PERSISTENT 0x01
|
||||
#define SQLITE_PREPARE_NORMALIZE 0x02
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_ROLLBACK 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -23,7 +23,7 @@ potential return value from the
|
|||
callback and that SQLITE_ABORT is also a result code.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10013.
|
||||
interface documentation at line 10125.
|
||||
.Bd -literal
|
||||
#define SQLITE_ROLLBACK 1
|
||||
/* #define SQLITE_IGNORE 2 // Also used by sqlite3_authorizer() callback */
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SCANSTAT_COMPLEX 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -10,7 +10,7 @@
|
|||
.Sh DESCRIPTION
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10154.
|
||||
interface documentation at line 10266.
|
||||
.Bd -literal
|
||||
#define SQLITE_SCANSTAT_COMPLEX 0x0001
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SCANSTAT_NLOOP 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -80,7 +80,7 @@ the output variable is set to -1.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10031.
|
||||
interface documentation at line 10143.
|
||||
.Bd -literal
|
||||
#define SQLITE_SCANSTAT_NLOOP 0
|
||||
#define SQLITE_SCANSTAT_NVISIT 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SERIALIZE_NOCOPY 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -24,7 +24,7 @@ been initialized by a prior call to
|
|||
.Fn sqlite3_deserialize .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10567.
|
||||
interface documentation at line 10686.
|
||||
.Bd -literal
|
||||
#define SQLITE_SERIALIZE_NOCOPY 0x001 /* Do no memory allocations */
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SESSION_CONFIG_STRMSIZE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -10,7 +10,7 @@
|
|||
.Sh DESCRIPTION
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 12530.
|
||||
interface documentation at line 12715.
|
||||
.Bd -literal
|
||||
#define SQLITE_SESSION_CONFIG_STRMSIZE 1
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SESSION_OBJCONFIG_SIZE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -40,7 +40,7 @@ It is an error (SQLITE_MISUSE) to attempt to modify this setting after
|
|||
the first table has been attached to the session object.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10887.
|
||||
interface documentation at line 11016.
|
||||
.Bd -literal
|
||||
#define SQLITE_SESSION_OBJCONFIG_SIZE 1
|
||||
#define SQLITE_SESSION_OBJCONFIG_ROWID 2
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SHM_NLOCK 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SHM_UNLOCK 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_STATUS_MEMORY_USED 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -91,7 +91,7 @@ YYTRACKMAXSTACKDEPTH.
|
|||
New status parameters may be added from time to time.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8437.
|
||||
interface documentation at line 8549.
|
||||
.Bd -literal
|
||||
#define SQLITE_STATUS_MEMORY_USED 0
|
||||
#define SQLITE_STATUS_PAGECACHE_USED 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_STMTSTATUS_FULLSCAN_STEP 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -81,7 +81,7 @@ to sqlite3_stmt_status() is ignored when the opcode is SQLITE_STMTSTATUS_MEMUSED
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8693.
|
||||
interface documentation at line 8805.
|
||||
.Bd -literal
|
||||
#define SQLITE_STMTSTATUS_FULLSCAN_STEP 1
|
||||
#define SQLITE_STMTSTATUS_SORT 2
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_SYNC_NORMAL 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_TESTCTRL_FIRST 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -6,6 +6,7 @@
|
|||
.Nm SQLITE_TESTCTRL_PRNG_SAVE ,
|
||||
.Nm SQLITE_TESTCTRL_PRNG_RESTORE ,
|
||||
.Nm SQLITE_TESTCTRL_PRNG_RESET ,
|
||||
.Nm SQLITE_TESTCTRL_FK_NO_ACTION ,
|
||||
.Nm SQLITE_TESTCTRL_BITVEC_TEST ,
|
||||
.Nm SQLITE_TESTCTRL_FAULT_INSTALL ,
|
||||
.Nm SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS ,
|
||||
|
@ -13,6 +14,7 @@
|
|||
.Nm SQLITE_TESTCTRL_ASSERT ,
|
||||
.Nm SQLITE_TESTCTRL_ALWAYS ,
|
||||
.Nm SQLITE_TESTCTRL_RESERVE ,
|
||||
.Nm SQLITE_TESTCTRL_JSON_SELFCHECK ,
|
||||
.Nm SQLITE_TESTCTRL_OPTIMIZATIONS ,
|
||||
.Nm SQLITE_TESTCTRL_ISKEYWORD ,
|
||||
.Nm SQLITE_TESTCTRL_SCRATCHMALLOC ,
|
||||
|
@ -43,6 +45,7 @@
|
|||
.Fd #define SQLITE_TESTCTRL_PRNG_SAVE
|
||||
.Fd #define SQLITE_TESTCTRL_PRNG_RESTORE
|
||||
.Fd #define SQLITE_TESTCTRL_PRNG_RESET
|
||||
.Fd #define SQLITE_TESTCTRL_FK_NO_ACTION
|
||||
.Fd #define SQLITE_TESTCTRL_BITVEC_TEST
|
||||
.Fd #define SQLITE_TESTCTRL_FAULT_INSTALL
|
||||
.Fd #define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS
|
||||
|
@ -50,6 +53,7 @@
|
|||
.Fd #define SQLITE_TESTCTRL_ASSERT
|
||||
.Fd #define SQLITE_TESTCTRL_ALWAYS
|
||||
.Fd #define SQLITE_TESTCTRL_RESERVE
|
||||
.Fd #define SQLITE_TESTCTRL_JSON_SELFCHECK
|
||||
.Fd #define SQLITE_TESTCTRL_OPTIMIZATIONS
|
||||
.Fd #define SQLITE_TESTCTRL_ISKEYWORD
|
||||
.Fd #define SQLITE_TESTCTRL_SCRATCHMALLOC
|
||||
|
@ -84,12 +88,13 @@ Applications should not use any of these parameters or the
|
|||
interface.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8173.
|
||||
interface documentation at line 8283.
|
||||
.Bd -literal
|
||||
#define SQLITE_TESTCTRL_FIRST 5
|
||||
#define SQLITE_TESTCTRL_PRNG_SAVE 5
|
||||
#define SQLITE_TESTCTRL_PRNG_RESTORE 6
|
||||
#define SQLITE_TESTCTRL_PRNG_RESET 7 /* NOT USED */
|
||||
#define SQLITE_TESTCTRL_FK_NO_ACTION 7
|
||||
#define SQLITE_TESTCTRL_BITVEC_TEST 8
|
||||
#define SQLITE_TESTCTRL_FAULT_INSTALL 9
|
||||
#define SQLITE_TESTCTRL_BENIGN_MALLOC_HOOKS 10
|
||||
|
@ -97,6 +102,7 @@ interface documentation at line 8173.
|
|||
#define SQLITE_TESTCTRL_ASSERT 12
|
||||
#define SQLITE_TESTCTRL_ALWAYS 13
|
||||
#define SQLITE_TESTCTRL_RESERVE 14 /* NOT USED */
|
||||
#define SQLITE_TESTCTRL_JSON_SELFCHECK 14
|
||||
#define SQLITE_TESTCTRL_OPTIMIZATIONS 15
|
||||
#define SQLITE_TESTCTRL_ISKEYWORD 16 /* NOT USED */
|
||||
#define SQLITE_TESTCTRL_SCRATCHMALLOC 17 /* NOT USED */
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_TRACE_STMT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,11 +1,11 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_TXN_NONE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm SQLITE_TXN_NONE ,
|
||||
.Nm SQLITE_TXN_READ ,
|
||||
.Nm SQLITE_TXN_WRITE
|
||||
.Nd allowed return values from [sqlite3_txn_state()]
|
||||
.Nd allowed return values from sqlite3_txn_state()
|
||||
.Sh SYNOPSIS
|
||||
.In sqlite3.h
|
||||
.Fd #define SQLITE_TXN_NONE
|
||||
|
@ -37,7 +37,7 @@ The transaction state will change to to SQLITE_TXN_NONE at the next
|
|||
ROLLBACK or COMMIT.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6569.
|
||||
interface documentation at line 6673.
|
||||
.Bd -literal
|
||||
#define SQLITE_TXN_NONE 0
|
||||
#define SQLITE_TXN_READ 1
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_UTF8 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -22,7 +22,7 @@ These constant define integer codes that represent the various text
|
|||
encodings supported by SQLite.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5496.
|
||||
interface documentation at line 5500.
|
||||
.Bd -literal
|
||||
#define SQLITE_UTF8 1 /* IMP: R-37514-35566 */
|
||||
#define SQLITE_UTF16LE 2 /* IMP: R-03371-37637 */
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_VERSION 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -38,9 +38,9 @@ in, then the last four hexadecimal digits of the hash may be modified.
|
|||
These declarations were extracted from the
|
||||
interface documentation at line 120.
|
||||
.Bd -literal
|
||||
#define SQLITE_VERSION "3.43.0"
|
||||
#define SQLITE_VERSION_NUMBER 3043000
|
||||
#define SQLITE_SOURCE_ID "2023-08-24 12:36:59 0f80b798b3f4b81a7bb4233c58294edd0f1156f36b6ecf5ab8e83631d468778c"
|
||||
#define SQLITE_VERSION "3.45.1"
|
||||
#define SQLITE_VERSION_NUMBER 3045001
|
||||
#define SQLITE_SOURCE_ID "2024-01-30 16:01:20 e876e51a0ed5c5b3126f52e532044363a014bc594cfefa87ffb5b82257cc467a"
|
||||
.Ed
|
||||
.Sh SEE ALSO
|
||||
.Xr sqlite3_version 3
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_VTAB_CONSTRAINT_SUPPORT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -77,7 +77,7 @@ and any ATTACH-ed databases) whenever the virtual table is used.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 9628.
|
||||
interface documentation at line 9740.
|
||||
.Bd -literal
|
||||
#define SQLITE_VTAB_CONSTRAINT_SUPPORT 1
|
||||
#define SQLITE_VTAB_INNOCUOUS 2
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE_WIN32_DATA_DIRECTORY_TYPE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -15,7 +15,7 @@ They define the allowed values for the type argument to the sqlite3_win32_set_di
|
|||
interface.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6441.
|
||||
interface documentation at line 6545.
|
||||
.Bd -literal
|
||||
#define SQLITE_WIN32_DATA_DIRECTORY_TYPE 1
|
||||
#define SQLITE_WIN32_TEMP_DIRECTORY_TYPE 2
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_AGGREGATE_CONTEXT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -53,7 +53,7 @@ This routine must be called from the same thread in which the aggregate
|
|||
SQL function is running.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5806.
|
||||
interface documentation at line 5831.
|
||||
.Bd -literal
|
||||
SQLITE_API void *sqlite3_aggregate_context(sqlite3_context*, int nBytes);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_AGGREGATE_COUNT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -47,7 +47,7 @@ To encourage programmers to avoid these functions, we will not explain
|
|||
what they do.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5590.
|
||||
interface documentation at line 5609.
|
||||
.Bd -literal
|
||||
#ifndef SQLITE_OMIT_DEPRECATED
|
||||
SQLITE_API SQLITE_DEPRECATED int sqlite3_aggregate_count(sqlite3_context*);
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_API_ROUTINES 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_AUTO_EXTENSION 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -51,7 +51,7 @@ that is opened.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7103.
|
||||
interface documentation at line 7207.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_auto_extension(void(*xEntryPoint)(void));
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_AUTOVACUUM_PAGES 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -48,7 +48,7 @@ There is only one autovacuum pages callback per database connection.
|
|||
Each call to the sqlite3_autovacuum_pages() interface overrides all
|
||||
previous invocations for that database connection.
|
||||
If the callback argument (C) to sqlite3_autovacuum_pages(D,C,P,X) is
|
||||
a NULL pointer, then the autovacuum steps callback is cancelled.
|
||||
a NULL pointer, then the autovacuum steps callback is canceled.
|
||||
The return value from sqlite3_autovacuum_pages() is normally SQLITE_OK,
|
||||
but might be some other error code if something goes wrong.
|
||||
The current implementation will only return SQLITE_OK or SQLITE_MISUSE,
|
||||
|
@ -71,7 +71,7 @@ nFreePage; }
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6668.
|
||||
interface documentation at line 6772.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_autovacuum_pages(
|
||||
sqlite3 *db,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BACKUP 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -16,7 +16,7 @@ and is destroyed by a call to
|
|||
.Fn sqlite3_backup_finish .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8995.
|
||||
interface documentation at line 9107.
|
||||
.Bd -literal
|
||||
typedef struct sqlite3_backup sqlite3_backup;
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BACKUP_INIT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -231,7 +231,7 @@ If they are invoked at the same time as another thread is invoking
|
|||
sqlite3_backup_step() it is possible that they return invalid values.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 9007.
|
||||
interface documentation at line 9119.
|
||||
.Bd -literal
|
||||
SQLITE_API sqlite3_backup *sqlite3_backup_init(
|
||||
sqlite3 *pDest, /* Destination database handle */
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BIND_BLOB 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -259,7 +259,7 @@ SQLITE_NOMEM is returned if malloc() fails.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4540.
|
||||
interface documentation at line 4543.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_bind_blob(sqlite3_stmt*, int, const void*, int n, void(*)(void*));
|
||||
SQLITE_API int sqlite3_bind_blob64(sqlite3_stmt*, int, const void*, sqlite3_uint64,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BIND_PARAMETER_COUNT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -25,7 +25,7 @@ If parameters of the ?NNN form are used, there may be gaps in the list.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4696.
|
||||
interface documentation at line 4699.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_bind_parameter_count(sqlite3_stmt*);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BIND_PARAMETER_INDEX 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -23,7 +23,7 @@ or
|
|||
.Fn sqlite3_prepare16_v3 .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4745.
|
||||
interface documentation at line 4748.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_bind_parameter_index(sqlite3_stmt*, const char *zName);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BIND_PARAMETER_NAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -34,7 +34,7 @@ or
|
|||
.Fn sqlite3_prepare16_v3 .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4717.
|
||||
interface documentation at line 4720.
|
||||
.Bd -literal
|
||||
SQLITE_API const char *sqlite3_bind_parameter_name(sqlite3_stmt*, int);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -24,7 +24,7 @@ The
|
|||
interface returns the size of the BLOB in bytes.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7561.
|
||||
interface documentation at line 7669.
|
||||
.Bd -literal
|
||||
typedef struct sqlite3_blob sqlite3_blob;
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB_BYTES 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -25,7 +25,7 @@ Passing any other pointer in to this routine results in undefined and
|
|||
probably undesirable behavior.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7716.
|
||||
interface documentation at line 7824.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_blob_bytes(sqlite3_blob *);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB_CLOSE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -23,7 +23,7 @@ If an error occurs while committing the transaction, an error code
|
|||
is returned and the transaction rolled back.
|
||||
.Pp
|
||||
Calling this function with an argument that is not a NULL pointer or
|
||||
an open blob handle results in undefined behaviour.
|
||||
an open blob handle results in undefined behavior.
|
||||
Calling this routine with a null pointer (such as would be returned
|
||||
by a failed call to
|
||||
.Fn sqlite3_blob_open )
|
||||
|
@ -33,7 +33,7 @@ values returned by the sqlite3_errcode() and sqlite3_errmsg() functions
|
|||
are set before returning.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7693.
|
||||
interface documentation at line 7801.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_blob_close(sqlite3_blob *);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB_OPEN 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -120,7 +120,7 @@ eventually be released by a call to
|
|||
.Fn sqlite3_blob_close .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7575.
|
||||
interface documentation at line 7683.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_blob_open(
|
||||
sqlite3*,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB_READ 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -45,7 +45,7 @@ probably undesirable behavior.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7732.
|
||||
interface documentation at line 7840.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_blob_read(sqlite3_blob *, void *Z, int N, int iOffset);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB_REOPEN 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -41,7 +41,7 @@ on an aborted blob handle always returns zero.
|
|||
This function sets the database handle error code and message.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7668.
|
||||
interface documentation at line 7776.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_blob_reopen(sqlite3_blob *, sqlite3_int64);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BLOB_WRITE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -62,7 +62,7 @@ probably undesirable behavior.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7761.
|
||||
interface documentation at line 7869.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_blob_write(sqlite3_blob *, const void *z, int n, int iOffset);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BUSY_HANDLER 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_BUSY_TIMEOUT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CANCEL_AUTO_EXTENSION 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -19,7 +19,7 @@ routine returns 1 if initialization routine X was successfully unregistered
|
|||
and it returns 0 if X was not on the list of initialization routines.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7141.
|
||||
interface documentation at line 7245.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_cancel_auto_extension(void(*xEntryPoint)(void));
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CHANGEGROUP 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -12,7 +12,7 @@ A changegroup is an object used to combine two or more changesets
|
|||
or patchsets
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 11681.
|
||||
interface documentation at line 11822.
|
||||
.Bd -literal
|
||||
typedef struct sqlite3_changegroup sqlite3_changegroup;
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CHANGES 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CHANGESET_ITER 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -12,7 +12,7 @@ An instance of this object acts as a cursor for iterating over the
|
|||
elements of a changeset or patchset.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10816.
|
||||
interface documentation at line 10945.
|
||||
.Bd -literal
|
||||
typedef struct sqlite3_changeset_iter sqlite3_changeset_iter;
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CLEAR_BINDINGS 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -17,7 +17,7 @@ does not reset the bindings on a prepared statement.
|
|||
Use this routine to reset all host parameters to NULL.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4763.
|
||||
interface documentation at line 4766.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_clear_bindings(sqlite3_stmt*);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CLOSE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COLLATION_NEEDED 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -47,7 +47,7 @@ or
|
|||
.Fn sqlite3_create_collation_v2 .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6246.
|
||||
interface documentation at line 6350.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_collation_needed(
|
||||
sqlite3*,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COLUMN_BLOB 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -324,7 +324,7 @@ immediately after the suspect return value is obtained and before any
|
|||
other SQLite interface is called on the same database connection.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5038.
|
||||
interface documentation at line 5041.
|
||||
.Bd -literal
|
||||
SQLITE_API const void *sqlite3_column_blob(sqlite3_stmt*, int iCol);
|
||||
SQLITE_API double sqlite3_column_double(sqlite3_stmt*, int iCol);
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COLUMN_COUNT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -22,7 +22,7 @@ it might return no rows.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4773.
|
||||
interface documentation at line 4776.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_column_count(sqlite3_stmt *pStmt);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COLUMN_DATABASE_NAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -85,7 +85,7 @@ for the same prepared statement and result column
|
|||
at the same time then the results are undefined.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4819.
|
||||
interface documentation at line 4822.
|
||||
.Bd -literal
|
||||
SQLITE_API const char *sqlite3_column_database_name(sqlite3_stmt*,int);
|
||||
SQLITE_API const void *sqlite3_column_database_name16(sqlite3_stmt*,int);
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COLUMN_DECLTYPE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -46,7 +46,7 @@ Type is associated with individual values, not with the containers
|
|||
used to hold those values.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4868.
|
||||
interface documentation at line 4871.
|
||||
.Bd -literal
|
||||
SQLITE_API const char *sqlite3_column_decltype(sqlite3_stmt*,int);
|
||||
SQLITE_API const void *sqlite3_column_decltype16(sqlite3_stmt*,int);
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COLUMN_NAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -47,7 +47,7 @@ If there is no AS clause then the name of the column is unspecified
|
|||
and may change from one release of SQLite to the next.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4789.
|
||||
interface documentation at line 4792.
|
||||
.Bd -literal
|
||||
SQLITE_API const char *sqlite3_column_name(sqlite3_stmt*, int N);
|
||||
SQLITE_API const void *sqlite3_column_name16(sqlite3_stmt*, int N);
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COMMIT_HOOK 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -72,7 +72,7 @@ See also the
|
|||
interface.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6618.
|
||||
interface documentation at line 6722.
|
||||
.Bd -literal
|
||||
SQLITE_API void *sqlite3_commit_hook(sqlite3*, int(*)(void*), void*);
|
||||
SQLITE_API void *sqlite3_rollback_hook(sqlite3*, void(*)(void *), void*);
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COMPILEOPTION_USED 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_COMPLETE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CONFIG 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CONTEXT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -22,7 +22,7 @@ and/or
|
|||
.Fn sqlite3_set_auxdata .
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4526.
|
||||
interface documentation at line 4529.
|
||||
.Bd -literal
|
||||
typedef struct sqlite3_context sqlite3_context;
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CONTEXT_DB_HANDLE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -20,7 +20,7 @@ and
|
|||
routines that originally registered the application defined function.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5866.
|
||||
interface documentation at line 5891.
|
||||
.Bd -literal
|
||||
SQLITE_API sqlite3 *sqlite3_context_db_handle(sqlite3_context*);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CREATE_COLLATION 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -126,7 +126,7 @@ backwards compatibility.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6142.
|
||||
interface documentation at line 6246.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_create_collation(
|
||||
sqlite3*,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CREATE_FILENAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CREATE_FUNCTION 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -186,7 +186,7 @@ However, such calls must not close the database connection nor finalize
|
|||
or reset the prepared statement in which the function is running.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 5329.
|
||||
interface documentation at line 5333.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_create_function(
|
||||
sqlite3 *db,
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_CREATE_MODULE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -53,7 +53,7 @@ same name are dropped.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 7422.
|
||||
interface documentation at line 7530.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_create_module(
|
||||
sqlite3 *db, /* SQLite connection to register module with */
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DATA_COUNT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -28,7 +28,7 @@ returns 0 columns of data.
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 4985.
|
||||
interface documentation at line 4988.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_data_count(sqlite3_stmt *pStmt);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DATA_DIRECTORY 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -42,7 +42,7 @@ or else the use of the data_store_directory pragma
|
|||
should be avoided.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6378.
|
||||
interface documentation at line 6482.
|
||||
.Bd -literal
|
||||
SQLITE_API SQLITE_EXTERN char *sqlite3_data_directory;
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DATABASE_FILE_OBJECT 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_CACHEFLUSH 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -47,7 +47,7 @@ and
|
|||
functions.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 10171.
|
||||
interface documentation at line 10283.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_db_cacheflush(sqlite3*);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_CONFIG 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_FILENAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -48,7 +48,7 @@ it can be used as the filename input parameter to these routines:
|
|||
.Pp
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6509.
|
||||
interface documentation at line 6613.
|
||||
.Bd -literal
|
||||
SQLITE_API sqlite3_filename sqlite3_db_filename(sqlite3 *db, const char *zDbName);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_HANDLE 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -21,7 +21,7 @@ call (or its variants) that was used to create the statement in the
|
|||
first place.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6474.
|
||||
interface documentation at line 6578.
|
||||
.Bd -literal
|
||||
SQLITE_API sqlite3 *sqlite3_db_handle(sqlite3_stmt*);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_MUTEX 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -18,7 +18,7 @@ If the threading mode is Single-thread or Multi-thread
|
|||
then this routine returns a NULL pointer.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 8099.
|
||||
interface documentation at line 8209.
|
||||
.Bd -literal
|
||||
SQLITE_API sqlite3_mutex *sqlite3_db_mutex(sqlite3*);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_NAME 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -34,7 +34,7 @@ on multiple threads should mutex-protect calls to this API and should
|
|||
make their own private copy of the result prior to releasing the mutex.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6487.
|
||||
interface documentation at line 6591.
|
||||
.Bd -literal
|
||||
SQLITE_API const char *sqlite3_db_name(sqlite3 *db, int N);
|
||||
.Ed
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
.Dd August 24, 2023
|
||||
.Dd January 24, 2024
|
||||
.Dt SQLITE3_DB_READONLY 3
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -17,7 +17,7 @@ of connection D is read-only, 0 if it is read/write, or -1 if N is
|
|||
not the name of a database on connection D.
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
These declarations were extracted from the
|
||||
interface documentation at line 6541.
|
||||
interface documentation at line 6645.
|
||||
.Bd -literal
|
||||
SQLITE_API int sqlite3_db_readonly(sqlite3 *db, const char *zDbName);
|
||||
.Ed
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue