Small. Fast. Reliable.
Choose any three.
Choose any three.
|
Dynamic Memory Allocation In SQLite
(malloc.html)
4.1. Computing and controlling parameters M and n
... The maximum amount of general-purpose memory needed by the application
is determined by such factors as how many simultaneous open
database connection and prepared statement objects the application
uses, and on the complexity of the prepared statements. For any ...
|
|
Transaction
(lang_transaction.html)
... A statement finishes when its
last cursor closes, which is guaranteed to happen when the
prepared statement is reset or
finalized. Some statements might "finish"
for the purpose of transaction control prior to being reset or finalized,
but there is ...
|
|
Using SQLite In Multi-Threaded Applications
(threadsafe.html)
1. Overview
... In this mode, SQLite can be safely used by multiple threads provided that
no single database connection nor any object derived from database connection,
such as a prepared statement,
is used in two or more threads at the same time ...
|
|
Implementation Limits For SQLite
(limits.html)
... Prepare short SQL statements like this:
INSERT INTO tab1 VALUES(?,?,?);
Then use the sqlite3_bind_XXXX() functions
to bind your large string values to the SQL statement. The use of binding
obviates the need to escape quote characters in the string, reducing ...
|
|
SQLite Unlock-Notify API
(unlock_notify.html)
... Otherwise, the
** system may become deadlocked.
*/
int sqlite3_blocking_prepare_v2(
sqlite3 *db, /* Database handle. */
const char *zSql, /* UTF-8 encoded SQL statement. */
int nSql, /* Length of zSql in bytes. */
sqlite3_stmt **ppStmt, /* OUT: A pointer to the prepared statement */
const char **pz /* OUT ...
|
|
C API: Status Parameters for database connections
(c3ref/c_dbstatus_options.html)
SQLITE_DBSTATUS_LOOKASIDE_USED, SQLITE_DBSTATUS_CACHE_USED, SQLITE_DBSTATUS_SCHEMA_USED, SQLITE_DBSTATUS_STMT_USED, SQLITE_DBSTATUS_LOOKASIDE_HIT, SQLITE_DBSTATUS_LOOKASIDE_MISS_SIZE ...
... SQLITE_DBSTATUS_STMT_USED
This parameter returns the approximate number of bytes of heap
and lookaside memory used by all prepared statements associated with
the database connection.
The highwater mark associated with SQLITE_DBSTATUS_STMT_USED is always 0.
SQLITE_DBSTATUS_CACHE_HIT
This parameter returns the number of ...
|
|
Architecture of SQLite
(arch.html)
... Code Generator
After the parser assembles tokens into a parse tree,
the code generator runs to analyze the parse tree and generate
bytecode that performs the work of the SQL statement.
The prepared statement object is a container for this ...
|
|
Compile-time Options
(compile.html)
4. Options To Set Default Parameter Values
... The SQLITE_LIMIT_WORKER_THREADS
parameter sets the maximum number of auxiliary threads that a single
prepared statement will launch to assist it with a query. If not specified,
the default maximum is 0.
The value set here cannot be more than SQLITE_MAX_WORKER_THREADS ...
|
|
Custom Builds Of SQLite
(custombuild.html)
... The
SQLITE_CONFIG_MULTITHREAD setting disables the mutexes that
serialize access to database connection objects and
prepared statement objects. With this setting, the application
is free to use SQLite from multiple threads, but it must make sure
than no two threads try ...
|
|
C API: Create Or Redefine SQL Functions
(c3ref/create_function.html)
sqlite3_create_function(), sqlite3_create_function16(), sqlite3_create_function_v2(), sqlite3_create_window_function()
... However, such calls must not
close the database connection nor finalize or reset the prepared
statement in which the function is running.
See also lists of
Objects,
Constants, and
Functions.
|
Page generated by FTS5 in about 106.31 ms.