Small. Fast. Reliable.
Choose any three.
Choose any three.
|
C API: Determine if a virtual table query is DISTINCT
(c3ref/vtab_distinct.html)
sqlite3_vtab_distinct()
... The sqlite3_vtab_distinct() interface returns an integer between 0 and
3. The integer returned by sqlite3_vtab_distinct()
gives the virtual table additional information about how the query
planner wants the output to be ordered. As long as the virtual table
can meet ...
|
|
The ON CONFLICT Clause
(lang_conflict.html)
... The ON CONFLICT clause described here has been a part of
SQLite since before version 3.0.0 (2004-06-18). The phrase
"ON CONFLICT" is also part of UPSERT, which is an extension
to INSERT added in version ...
|
|
Why Is SQLite Coded In C
(whyc.html)
1.3. Low-Dependency
... In its minimum configuration, SQLite requires only the following
routines from the standard C library:
memcmp()
memcpy()
memmove()
memset()
strcmp()
strlen()
strncmp()
In a more complete build, SQLite also uses library routines like
malloc() and free() and ...
|
|
Why SQLite Uses Bytecode
(whybytecode.html)
3. Advantages Of Compiling Into A Tree Of Objects
The SQLite developers think that the bytecode approach is
best, at least for the use cases the SQLite tries to fill, but the
tree-of-objects approach to processing SQL does have some advantages over
bytecode. There are always tradeoffs.
|
|
Imposter Tables
(imposter.html)
3. Summary And Final Warning
The imposter table mechanism is a power analysis and debugging tool
for SQLite. But as with all sharp tools, it can also be dangerous and
can result in corrupt database files if misused. Do not attempt to
use imposter tables ...
|
|
C API: Query Progress Callbacks
(c3ref/progress_handler.html)
sqlite3_progress_handler()
... However, beginning with
SQLite version 3.41.0, the progress handler callback might also be
invoked directly from sqlite3_prepare() while analyzing and generating
code for complex queries.
See also lists of
Objects,
Constants, and
Functions.
|
|
RETURNING
(lang_returning.html)
... The RETURNING syntax has been supported by SQLite since version 3.35.0
(2021-03-12).
1.1. Typical Use
The RETURNING clause is designed to provide the application with the
values of columns that are filled in automatically by ...
|
|
The Base64() SQL Function
(base64.html)
... The base64() function is not a standard part of SQLite.
It must be loaded as a separate extension. The source code to
base64() is in the
base64.c source file
in the ext/misc/ folder of the
SQLite source tree ...
|
|
Memory-Mapped I/O
(mmap.html)
... However if a version
of SQLite prior to 3.7.0 runs PRAGMA integrity_check on such a
database, it will (incorrectly) report database corruption due to
the unused space at the end. Or if a version of SQLite prior to ...
|
|
The DBSTAT Virtual Table
(dbstat.html)
3. Aggregated Data
Beginning with SQLite version 3.31.0 (2020-01-22), the DBSTAT table
has a new hidden column named "aggregate", which if constrained to be
TRUE will cause DBSTAT to generate one row per btree in the database,
rather than ...
|
Page generated by FTS5 in about 376.19 ms.