http://www.sqlite.org/c3ref/open.html

http://www.sqlite.org/c3ref/close.html

http://www.sqlite.org/c3ref/errcode.html

http://www.sqlite.org/c3ref/errcode.html

http://www.sqlite.org/c3ref/profile.html

Enable/disable tracing of SQL execution. Tracing can be disabled by setting Nothing as the logger callback.

Warning: If the logger callback throws an exception, your whole program will crash. Enable only for debugging!

http://www.sqlite.org/c3ref/get_autocommit.html

Return True if the connection is in autocommit mode, or False if a transaction started with BEGIN is still active.

Be warned that some errors roll back the transaction automatically, and that ROLLBACK will throw an error if no transaction is active. Use getAutoCommit to avoid such an error:

 autocommit <- getAutoCommit conn
 when (not autocommit) $
     exec conn "ROLLBACK"

https://www.sqlite.org/c3ref/enable_shared_cache.html

Enable or disable shared cache for all future connections.

Like exec, but invoke the callback for each result row.

If the callback throws an exception, it will be rethrown by execWithCallback.

http://www.sqlite.org/c3ref/prepare.html

If the query contains no SQL statements, this returns Right Nothing.

http://www.sqlite.org/c3ref/db_handle.html

http://www.sqlite.org/c3ref/step.html

http://www.sqlite.org/c3ref/reset.html

Warning:

• If the most recent step call failed, this will return the corresponding error.
• This does not reset the bindings on a prepared statement. Use clearBindings to do that.

http://www.sqlite.org/c3ref/finalize.html

Warning: If the most recent step call failed, this will return the corresponding error.

http://www.sqlite.org/c3ref/clear_bindings.html

Set all parameters in the prepared statement to null.

http://www.sqlite.org/c3ref/sql.html

Return a copy of the original SQL text used to compile the statement.

http://www.sqlite.org/c3ref/bind_parameter_count.html

This returns the index of the largest (rightmost) parameter. Note that this is not necessarily the number of parameters. If numbered parameters like ?5 are used, there may be gaps in the list.

See ParamIndex for more information.

http://www.sqlite.org/c3ref/bind_parameter_name.html

http://www.sqlite.org/c3ref/bind_parameter_index.html

http://www.sqlite.org/c3ref/column_count.html

http://www.sqlite.org/c3ref/column_name.html

http://www.sqlite.org/c3ref/enable_load_extension.html

Enable or disable extension loading.

http://www.sqlite.org/c3ref/last_insert_rowid.html

http://www.sqlite.org/c3ref/changes.html

Return the number of rows that were changed, inserted, or deleted by the most recent INSERT, DELETE, or UPDATE statement.

http://www.sqlite.org/c3ref/total_changes.html

Return the total number of row changes caused by INSERT, DELETE, or UPDATE statements since the Database was opened.

http://sqlite.org/c3ref/create_function.html

Create a custom SQL function or redefine the behavior of an existing function.

Like createFunction except that it creates an aggregate function.

Delete an SQL function (scalar or aggregate).

https://www.sqlite.org/c3ref/context_db_handle.html

http://www.sqlite.org/c3ref/create_collation.html

Delete a collation.

http://www.sqlite.org/c3ref/interrupt.html

Cause any pending operation on the Database handle to stop at its earliest opportunity. This simply sets a flag and returns immediately. It does not wait for the pending operation to finish.

You'll need to compile with -threaded for this to do any good. Without -threaded, FFI calls block the whole RTS, meaning interrupt would never run at the same time as step.

https://www.sqlite.org/c3ref/blob_open.html

Open a blob for incremental I/O.

https://www.sqlite.org/c3ref/blob_close.html

https://www.sqlite.org/c3ref/blob_reopen.html

https://www.sqlite.org/c3ref/blob_bytes.html

https://www.sqlite.org/c3ref/blob_read.html

https://www.sqlite.org/c3ref/blob_write.html

The context in which a custom SQL function is executed.

The arguments of a custom SQL function.

The type of blob handles used for incremental blob I/O

A handle for an online backup process.

A ByteString containing UTF8-encoded text with no NUL characters.

Index of a parameter in a parameterized query. Parameter indices start from 1.

When a query is prepared, SQLite allocates an array indexed from 1 to the highest parameter index. For example:

>Right stmt <- prepare conn "SELECT ?1, ?5, ?3, ?"
>bindParameterCount stmt
ParamIndex 6

This will allocate an array indexed from 1 to 6 (? takes the highest preceding index plus one). The array is initialized with null values. When you bind a parameter with bindSQLData, it assigns a new value to one of these indices.

See http://www.sqlite.org/lang_expr.html#varparam for the syntax of parameter placeholders, and how parameter indices are assigned.

Index of a column in a result set. Column indices start from 0.

Number of columns in a result set.

Number of arguments of a user defined SQL function.

Index of an argument to a custom function. Indices start from 0.