Small. Fast. Reliable.
Choose any three.
Choose any three.
|
C API: One-Step Query Execution Interface
(c3ref/exec.html)
sqlite3_exec()
The sqlite3_exec() interface is a convenience wrapper around
sqlite3_prepare_v2(), sqlite3_step(), and sqlite3_finalize(),
that allows an application to run multiple statements of SQL
without having to use a lot of C code.
The sqlite3_exec() interface runs zero or more UTF-8 ...
|
|
The Next-Generation Query Planner
(queryplanner-ng.html)
1. Introduction
The task of the "query planner" is to figure
out the best algorithm or "query plan" to accomplish an SQL statement.
Beginning with SQLite version 3.8.0 (2013-08-26),
the query planner component has been
rewritten so that ...
|
|
The SQLite Query Optimizer Overview
(optoverview.html)
1. Introduction
This document provides an overview of how the query planner and optimizer
for SQLite works.
Given a single SQL statement, there might be dozens, hundreds, or even
thousands of ways to implement that statement, depending on the complexity
of the ...
|
|
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 ...
... These routines return information about a single column of the current
result row of a query. 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 ...
|
|
Query Planning
(queryplanner.html)
Overview
... The query planner is an
AI that
tries to pick the fastest and most efficient algorithm for each SQL
statement.
Most of the time, the query planner in SQLite does a good job.
However, the query planner needs indices to ...
|
|
Many Small Queries Are Efficient In SQLite
(np1queryprob.html)
1. Executive Summary
... SQLite can also do large and complex queries efficiently, just like
client/server databases. But SQLite can do many smaller queries
efficiently too. Application developers can use whichever technique
works best for the task at hand.
|
|
EXPLAIN
(lang_explain.html)
... When the EXPLAIN QUERY PLAN phrase
appears, the statement returns high-level information regarding the query
plan that would have been used.
The EXPLAIN QUERY PLAN command is described in
more detail here.
2.1. EXPLAIN operates at run-time ...
|
|
C API: Prepared Statement Scan Status
(c3ref/stmt_scanstatus.html)
sqlite3_stmt_scanstatus(), sqlite3_stmt_scanstatus_v2()
... If SQLITE_SCANSTAT_COMPLEX
is specified, then status information is available for all elements
of a query plan that are reported by "EXPLAIN QUERY PLAN" output. If
SQLITE_SCANSTAT_COMPLEX is not specified, then only query plan elements
that correspond to query loops (the ...
|
|
Uniform Resource Identifiers
(uri.html)
3.2. Query String
A URI filename can optionally be followed by a query string.
The query string consists of text following the first "?"
character but excluding the optional fragment that begins with
"#". The query string is divided into key/value pairs.
We usually ...
|
|
C API: Prepared Statement Scan Status Opcodes
(c3ref/c_scanstat_est.html)
SQLITE_SCANSTAT_NLOOP, SQLITE_SCANSTAT_NVISIT, SQLITE_SCANSTAT_EST, SQLITE_SCANSTAT_NAME, SQLITE_SCANSTAT_EXPLAIN, SQLITE_SCANSTAT_SELECTID ...
... SQLITE_SCANSTAT_EST
The "double" variable pointed to by the V parameter will be set to the
query planner's estimate for the average number of rows output from each
iteration of the X-th loop. If the query planner's estimates ...
|
Page generated by FTS5 in about 222.61 ms.