3.1. Query Planning Decisions Can Be Deferred Until Runtime  ... The query plan is mutable and can be tweaked as it is running, based on the progress of the query. Thus a query can be dynamically self-tuning.

 ... Content can be accessed and updated using concise SQL queries instead of lengthy and error-prone procedural routines. The file format can be extended in future releases simply by adding new tables and/or column, preserving backwards compatibility. Applications can ... 

2.3.4. Enforcing Required Parameters On Table-Valued Functions  ... SELECT * FROM realtab, tablevaluedfunc(realtab.x); Assuming that the first hidden column of "tablevaluedfunc" is "param1", the query above is semantically equivalent to this: SELECT * FROM realtab, tablevaluedfunc WHERE tablevaluedfunc.param1 = realtab.x; The query planner must decide between many ... 

 ... UPDATE, DELETE, and INSERT (of course) Common table expressions including recursive common table expressions Row values UPSERT An advanced query planner Full-text search R-tree indexes JSON support The IS operator Table-valued functions REPLACE INTO VACUUM REINDEX The ... 

1. Situations Where SQLite Works Well  ... The SQL query language means that receivers are not required to parse the entire transfer all at once, but can instead query the received content as needed. The data format is "transparent" in the sense that it is easily decoded ... 

sqlite3_set_authorizer()

 ... When a table is referenced by a SELECT but no column values are extracted from that table (for example in a query like "SELECT count(*) FROM tab") then the SQLITE_READ authorizer callback is invoked once for that table with a ... 

2.1. Queries To query the geopoly table using an indexed geospatial search, use one of the functions geopoly_overlap() or geopoly_within() as a boolean function in the WHERE clause, with the "_shape" column as the first argument to the function. For example: SELECT ... 

5. Convenience Wrappers Around Core Routines  ... The sqlite3_get_table() interface differs from sqlite3_exec() in that it stores the results of queries in heap memory rather than invoking a callback. It is important to realize that neither sqlite3_exec() nor sqlite3_get_table() do anything that cannot be accomplished using the ... 

SQLITE_INDEX_CONSTRAINT_EQ, SQLITE_INDEX_CONSTRAINT_GT, SQLITE_INDEX_CONSTRAINT_LE, SQLITE_INDEX_CONSTRAINT_LT, SQLITE_INDEX_CONSTRAINT_GE, SQLITE_INDEX_CONSTRAINT_MATCH ... 

 ... Each value represents an operator that is part of a constraint term in the WHERE clause of a query that uses a virtual table. The left-hand operand of the operator is given by the corresponding aConstraint[].iColumn field. An ... 

sqlite3_prepare(), sqlite3_prepare_v2(), sqlite3_prepare_v3(), sqlite3_prepare16(), sqlite3_prepare16_v2(), sqlite3_prepare16_v3()

 ... If the specific value bound to a host parameter in the WHERE clause might influence the choice of query plan for a statement, then the statement will be automatically recompiled, as if there had been a schema change, on the ...