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 ... 

sqlite3_get_table(), sqlite3_free_table()

 ... The sqlite3_get_table() interface is implemented as a wrapper around sqlite3_exec(). The sqlite3_get_table() routine does not have access to any internal data structures of SQLite. It uses only the public interface defined here. As a consequence, errors that occur in the ... 

5. Convenience Wrappers Around Core Routines The sqlite3_exec() interface is a convenience wrapper that carries out all four of the above steps with a single function call. A callback function passed into sqlite3_exec() is used to process each row of the result set. The sqlite3_get_table() is ... 

struct sqlite3

 ... sqlite3_autovacuum_pages sqlite3_blob_open sqlite3_busy_handler sqlite3_busy_timeout sqlite3_changes sqlite3_changes64 sqlite3_collation_needed sqlite3_collation_needed16 sqlite3_commit_hook sqlite3_create_collation sqlite3_create_collation16 sqlite3_create_collation_v2 sqlite3_create_function sqlite3_create_function16 sqlite3_create_function_v2 sqlite3_create_module sqlite3_create_module_v2 sqlite3_create_window_function sqlite3_db_cacheflush sqlite3_db_config sqlite3_db_filename sqlite3_db_mutex sqlite3_db_name sqlite3_db_readonly sqlite3_db_release_memory sqlite3_db_status sqlite3_drop_modules sqlite3_enable_load_extension sqlite3_errcode sqlite3_errmsg sqlite3_errmsg16 sqlite3_error_offset sqlite3_errstr sqlite3_exec sqlite3_extended_errcode sqlite3_extended_result_codes sqlite3_file_control sqlite3_free_table sqlite3_get_autocommit sqlite3_get_clientdata ... 

 ... The function calls to pay attention to here are the call to sqlite3_open() on line 22 which opens the database, sqlite3_exec() on line 28 that executes SQL commands against the database, and sqlite3_close() on line 33 that closes the database ... 

 ... SAVEPOINT REPLACE RETURNING clause ROLLBACK TRANSACTION SAVEPOINT SELECT UPDATE UPSERT VACUUM WITH clause The routines sqlite3_prepare_v2(), sqlite3_prepare(), sqlite3_prepare16(), sqlite3_prepare16_v2(), sqlite3_exec(), and sqlite3_get_table() accept an SQL statement list (sql-stmt-list) which is a semicolon-separated list of statements. sql-stmt ... 

sqlite3_stmt_readonly()

 ... For example, if an application defines a function "eval()" that calls sqlite3_exec(), then the following SQL statement would change the database file through side-effects: But because the SELECT statement does not change the database file directly, sqlite3_stmt_readonly() would still ... 

 ... sqlite3_open(), sqlite3_exec(), and sqlite3_close(). More control over the execution of the database engine is provided using sqlite3_prepare_v2() to compile an SQLite statement into byte code and sqlite3_step() to execute that bytecode. A family of routines with names beginning with sqlite3_column_ ... 

4. Usage  ... then that might be all that you need to do. Otherwise, the API call above should be followed by: sqlite3_exec(db, "VACUUM", 0, 0, 0); It never hurts to run the VACUUM, even if you don't need it. If ... 

 ... If it fails to obtain a required lock immediately, sqlite3_backup_step() uses any registered busy-handler callback or timeout in the same way as sqlite3_step() or sqlite3_exec() does. Usually, it does not matter if the page-sizes of the source database ...