Small. Fast. Reliable.
Choose any three.
Choose any three.
|
Isolation In SQLite
(isolation.html)
... And the SELECT statement
obviously does not see any changes that occur after the SELECT statement
completes. But what about changes that occur while the SELECT statement
is running? What if a SELECT statement is started and the sqlite3_step()
interface ...
|
|
C API: Database Connection Configuration Options
(c3ref/c_dbconfig_defensive.html)
SQLITE_DBCONFIG_MAINDBNAME, SQLITE_DBCONFIG_LOOKASIDE, SQLITE_DBCONFIG_ENABLE_FKEY, SQLITE_DBCONFIG_ENABLE_TRIGGER, SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER, SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION ...
... For statistics to be collected, the flag must be set on
the database handle both when the SQL statement is prepared and when it
is stepped. The flag is set (collection of statistics is enabled)
by default. This option takes ...
|
|
NULL Handling in SQLite
(nulls.html)
... This involved making NULLs
indistinct for the purposes of the SELECT DISTINCT statement and
for the UNION operator in a SELECT. NULLs are still distinct
in a UNIQUE column. This seems somewhat arbitrary, but the desire
to be compatible with ...
|
|
C API: Result Values From A Query
(c3ref/column_blob.html)
sqlite3_column_blob(), sqlite3_column_double(), sqlite3_column_int(), sqlite3_column_int64(), sqlite3_column_text(), sqlite3_column_text16 ...
... In every case the first argument is a pointer
to the prepared statement that is being evaluated (the sqlite3_stmt*
that was returned from sqlite3_prepare_v2() or one of its variants)
and the second argument is the index of the column for ...
|
|
SQLite Changes From Version 3.5.9 To 3.6.0
(35to36.html)
... The sqlite3_next_stmt() interface allows an application to discover
all prepared statements associated with a database connection.
Added the page_count PRAGMA for returning the size of the underlying
database file in pages.
Added a new R*Tree index extension.
|
|
The SQLite Bytecode Engine
(opcode.html)
2. Introduction
SQLite works by translating each SQL statement into bytecode and
then running that bytecode.
A prepared statement in SQLite is mostly just the bytecode needed to
implement the corresponding SQL. The sqlite3_prepare_v2() interface
is a compiler that translates SQL into ...
|
|
The SQLite Query Optimizer Overview
(optoverview.html)
5. The LIKE Optimization
... The LIKE optimization is not attempted if the
right-hand side is a parameter and the statement was prepared using
sqlite3_prepare() or sqlite3_prepare16().
Suppose the initial sequence of non-wildcard characters on the right-hand
side of the LIKE or ...
|
|
35% Faster Than The Filesystem
(fasterthanfs.html)
2.1. Read Performance Measurements
... In this chart, an SQL statement ("SELECT v FROM kv WHERE k=?1")
is prepared once. Then for each blob, the blob key value is bound
to the ?1 parameter and the statement is evaluated to extract the
blob content ...
|
|
The Virtual Table Mechanism Of SQLite
(vtab.html)
2.13. The xUpdate Method
... This will occur
when an SQL statement updates a rowid, as in the statement:
UPDATE table SET rowid=rowid+1 WHERE ...;
The xUpdate method must return SQLITE_OK if and only if it is
successful. If a failure occurs, the xUpdate ...
|
|
C API: Setting The Result Of An SQL Function
(c3ref/result_blob.html)
sqlite3_result_blob(), sqlite3_result_blob64(), sqlite3_result_double(), sqlite3_result_error(), sqlite3_result_error16(), sqlite3_result_error_toobig ...
... These functions work very much like the parameter binding family of
functions used to bind values to host parameters in prepared statements.
Refer to the SQL parameter documentation for additional information.
The sqlite3_result_blob() interface sets the result from
an application ...
|
Page generated by FTS5 in about 106.06 ms.