Small. Fast. Reliable.
Choose any three.
Choose any three.
|
C API: Introduction
(c3ref/intro.html)
... A database connection object sqlite3, and the
prepared statement object sqlite3_stmt.
List Of Constants.
This is a list of numeric constants used by SQLite and represented by
#defines in the sqlite3.h header file. These constants
are things such as ...
|
|
How SQLite Works
(howitworks.html)
2.2. Compiling SQLite Programs
... The bytecode generated by the code generator is called a
"prepared statement". Translating SQL source text into a
prepared statement is analogous to converting a C++ program
into machine code by invoking gcc or clang. Human-readable
source text (SQL ...
|
|
Result and Error Codes
(rescode.html)
6. Result Code Meanings
... This result code can be returned from sqlite3_step() for
a prepared statement that was generated using sqlite3_prepare() or
sqlite3_prepare16(). If the database schema was changed by some other
process in between the time that the statement was prepared and the ...
|
|
C API: Configuration Options
(c3ref/c_config_covering_index_scan.html)
SQLITE_CONFIG_SINGLETHREAD, SQLITE_CONFIG_MULTITHREAD, SQLITE_CONFIG_SERIALIZED, SQLITE_CONFIG_MALLOC, SQLITE_CONFIG_GETMALLOC, SQLITE_CONFIG_SCRATCH ...
... In other words, it disables
mutexing on database connection and prepared statement objects.
The application is responsible for serializing access to
database connections and prepared statements. But other mutexes
are enabled so that SQLite will be safe to use in ...
|
|
The INDEXED BY Clause
(lang_indexedby.html)
... If index-name does not exist or cannot be used
for the query, then the preparation of the SQL statement fails.
The "NOT INDEXED" clause specifies that no index shall be used when
accessing the preceding table, including implied indices ...
|
|
The Error And Warning Log
(errlog.html)
3. Variety of Error Messages
... Any time there is an error either compiling an SQL statement
(using sqlite3_prepare_v2() or its siblings) or running an SQL
statement (using sqlite3_step()) that error is logged.
When a schema change occurs that requires a prepared statement to be reparsed ...
|
|
SQLite Frequently Asked Questions
(faq.html)
... Nor will you receive an error if you
prepare statements using sqlite3_prepare_v2() instead of
sqlite3_prepare().
The sqlite3_prepare_v2() interface creates a
prepared statement that will automatically recompile itself if
the schema changes. The easiest way to deal with
SQLITE_SCHEMA errors is ...
|
|
C API: Register A Callback To Handle SQLITE_BUSY Errors
(c3ref/busy_handler.html)
sqlite3_busy_handler()
... A busy handler must not close the database connection
or prepared statement that invoked the busy handler.
See also lists of
Objects,
Constants, and
Functions.
|
|
Pragma statements supported by SQLite
(pragma.html)
PRAGMA recursive_triggers
... Changing the recursive_triggers setting affects the execution of
all statements prepared
using the database connection, including those prepared before the
setting was changed. Any existing statements prepared using the legacy
sqlite3_prepare() interface may fail with an SQLITE_SCHEMA error
after the ...
|
|
The Carray() Table-Valued Function
(carray.html)
3.1. Single-Argument CARRAY
... SQLITE_STATIC → This means that the application that invokes
sqlite3_carray_bind() maintains ownership of the data array and that
the application promises SQLite that it will not change or deallocate
the data until after the prepared statement is finialized.
SQLITE_TRANSIENT &rarr ...
|
Page generated by FTS5 in about 122.78 ms.