C API: Query The EXPLAIN Setting For A Prepared Statement
(c3ref/stmt_isexplain.html)
sqlite3_stmt_isexplain()
The sqlite3_stmt_isexplain(S) interface returns 1 if the
prepared statement S is an EXPLAIN statement, or 2 if the
statement S is an EXPLAIN QUERY PLAN.
The sqlite3_stmt_isexplain(S) interface returns 0 if S is
an ordinary statement or a ...
|
C API: Declared Datatype Of A Query Result
(c3ref/column_decltype.html)
sqlite3_column_decltype(), sqlite3_column_decltype16()
The first parameter is a prepared statement.
If this statement is a SELECT statement and the Nth column of the
returned result set of that SELECT is a table column (not an
expression or subquery) then the declared type of ...
|
Query Language Understood by SQLite
(lang.html)
SQL As Understood By SQLite
SQLite understands most of the standard SQL
language. But it does omit some features
while at the same time
adding a few features of its own. This document attempts to
describe precisely what parts of ...
|
C API: Query Progress Callbacks
(c3ref/progress_handler.html)
sqlite3_progress_handler()
... An example use for this
interface is to keep a GUI updated during a large query.
The parameter P is passed through as the only parameter to the
callback function X. The parameter N is the approximate number of
virtual ...
|
EXPLAIN QUERY PLAN
(eqp.html)
1. The EXPLAIN QUERY PLAN Command
... This document is a guide to
understanding and interpreting the EXPLAIN QUERY PLAN output. Background
information is available separately:
A primer on How SQLite Works.
Notes on the query optimizer.
How indexing works.
The next generation query planner.
A query ...
|
C API: Interrupt A Long-Running Query
(c3ref/interrupt.html)
sqlite3_is_interrupted()
... This routine is typically
called in response to a user action such as pressing "Cancel"
or Ctrl-C where the user wants a long query operation to halt
immediately.
It is safe to call this routine from a thread different ...
|
C API: Source Of Data In A Query Result
(c3ref/column_database_name.html)
sqlite3_column_database_name(), sqlite3_column_database_name16(), sqlite3_column_table_name(), sqlite3_column_table_name16(), sqlite3_column_origin_name(), sqlite3_column_origin_name16()
... Otherwise, they return the name of the attached database, table,
or column that query result column was extracted from.
As with all other SQLite APIs, those whose names end with "16" return
UTF-16 encoded strings and the other functions ...
|
C API: Convenience Routines For Running Queries
(c3ref/free_table.html)
sqlite3_get_table(), sqlite3_free_table()
... A result table records the
complete query results from one or more queries.
The table conceptually has a number of rows and columns. But
these numbers are not part of the result table itself. These
numbers are obtained separately. Let ...
|
C API: Determine if a virtual table query is DISTINCT
(c3ref/vtab_distinct.html)
sqlite3_vtab_distinct()
... 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 ordering requirements of the query planner, it may set ...
|
Profiling SQL Queries
(profile.html)
1. Overview
SQLite contains built-in support for profiling SQL queries, but it is not
enabled by default. In order to enable support for query profiling, SQLite must
be compiled with the following option:
-DSQLITE_ENABLE_STMT_SCANSTATUS
Building SQLite with this option enables the ...
|
Page generated by FTS5 in about 234.97 ms.