Struct deltachat::sql::pool::PooledConnection
source · pub struct PooledConnection {
pool: Weak<InnerPool>,
conn: Option<Connection>,
_permit: OwnedSemaphorePermit,
_write_mutex_guard: Option<OwnedMutexGuard<()>>,
}
Expand description
Pooled connection.
Fields§
§pool: Weak<InnerPool>
Weak reference to the pool used to return the connection back.
conn: Option<Connection>
Only None
right after moving the connection back to the pool.
_permit: OwnedSemaphorePermit
Semaphore permit, dropped after returning the connection to the pool.
_write_mutex_guard: Option<OwnedMutexGuard<()>>
Write mutex guard.
None
for read-only connections with PRAGMA query_only=1
.
Methods from Deref<Target = Connection>§
pub fn busy_timeout(&self, timeout: Duration) -> Result<(), Error>
pub fn busy_timeout(&self, timeout: Duration) -> Result<(), Error>
Set a busy handler that sleeps for a specified amount of time when a table is locked. The handler will sleep multiple times until at least “ms” milliseconds of sleeping have accumulated.
Calling this routine with an argument equal to zero turns off all busy handlers.
There can only be a single busy handler for a particular database
connection at any given moment. If another busy handler was defined
(using busy_handler
) prior to calling this
routine, that other busy handler is cleared.
Newly created connections currently have a default busy timeout of 5000ms, but this may be subject to change.
pub fn busy_handler(
&self,
callback: Option<fn(_: i32) -> bool>,
) -> Result<(), Error>
pub fn busy_handler( &self, callback: Option<fn(_: i32) -> bool>, ) -> Result<(), Error>
Register a callback to handle SQLITE_BUSY
errors.
If the busy callback is None
, then SQLITE_BUSY
is returned
immediately upon encountering the lock. The argument to the busy
handler callback is the number of times that the
busy handler has been invoked previously for the
same locking event. If the busy callback returns false
, then no
additional attempts are made to access the
database and SQLITE_BUSY
is returned to the
application. If the callback returns true
, then another attempt
is made to access the database and the cycle repeats.
There can only be a single busy handler defined for each database
connection. Setting a new busy handler clears any previously set
handler. Note that calling busy_timeout()
or evaluating PRAGMA busy_timeout=N
will change the busy handler
and thus clear any previously set busy handler.
Newly created connections default to a
busy_timeout()
handler with a timeout
of 5000ms, although this is subject to change.
pub fn prepare_cached(&self, sql: &str) -> Result<CachedStatement<'_>, Error>
pub fn prepare_cached(&self, sql: &str) -> Result<CachedStatement<'_>, Error>
Prepare a SQL statement for execution, returning a previously prepared
(but not currently in-use) statement if one is available. The
returned statement will be cached for reuse by future calls to
prepare_cached
once it is dropped.
fn insert_new_people(conn: &Connection) -> Result<()> {
{
let mut stmt = conn.prepare_cached("INSERT INTO People (name) VALUES (?1)")?;
stmt.execute(["Joe Smith"])?;
}
{
// This will return the same underlying SQLite statement handle without
// having to prepare it again.
let mut stmt = conn.prepare_cached("INSERT INTO People (name) VALUES (?1)")?;
stmt.execute(["Bob Jones"])?;
}
Ok(())
}
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub fn set_prepared_statement_cache_capacity(&self, capacity: usize)
pub fn set_prepared_statement_cache_capacity(&self, capacity: usize)
Set the maximum number of cached prepared statements this connection will hold. By default, a connection will hold a relatively small number of cached statements. If you need more, or know that you will not use cached statements, you can set the capacity manually using this method.
pub fn flush_prepared_statement_cache(&self)
pub fn flush_prepared_statement_cache(&self)
Remove/finalize all prepared statements currently in the cache.
pub fn db_config(&self, config: DbConfig) -> Result<bool, Error>
pub fn db_config(&self, config: DbConfig) -> Result<bool, Error>
Returns the current value of a config
.
SQLITE_DBCONFIG_ENABLE_FKEY
: returnfalse
ortrue
to indicate whether FK enforcement is off or onSQLITE_DBCONFIG_ENABLE_TRIGGER
: returnfalse
ortrue
to indicate whether triggers are disabled or enabledSQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER
: returnfalse
ortrue
to indicate whetherfts3_tokenizer
are disabled or enabledSQLITE_DBCONFIG_NO_CKPT_ON_CLOSE
: returnfalse
to indicate checkpoints-on-close are not disabled ortrue
if they areSQLITE_DBCONFIG_ENABLE_QPSG
: returnfalse
ortrue
to indicate whether the QPSG is disabled or enabledSQLITE_DBCONFIG_TRIGGER_EQP
: returnfalse
to indicate output-for-trigger are not disabled ortrue
if it is
pub fn set_db_config(
&self,
config: DbConfig,
new_val: bool,
) -> Result<bool, Error>
pub fn set_db_config( &self, config: DbConfig, new_val: bool, ) -> Result<bool, Error>
Make configuration changes to a database connection
SQLITE_DBCONFIG_ENABLE_FKEY
:false
to disable FK enforcement,true
to enable FK enforcementSQLITE_DBCONFIG_ENABLE_TRIGGER
:false
to disable triggers,true
to enable triggersSQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER
:false
to disablefts3_tokenizer()
,true
to enablefts3_tokenizer()
SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE
:false
(the default) to enable checkpoints-on-close,true
to disable themSQLITE_DBCONFIG_ENABLE_QPSG
:false
to disable the QPSG,true
to enable QPSGSQLITE_DBCONFIG_TRIGGER_EQP
:false
to disable output for trigger programs,true
to enable it
pub fn pragma_query_value<T, F>(
&self,
schema_name: Option<DatabaseName<'_>>,
pragma_name: &str,
f: F,
) -> Result<T, Error>
pub fn pragma_query_value<T, F>( &self, schema_name: Option<DatabaseName<'_>>, pragma_name: &str, f: F, ) -> Result<T, Error>
Query the current value of pragma_name
.
Some pragmas will return multiple rows/values which cannot be retrieved with this method.
Prefer PRAGMA function introduced in SQLite 3.20:
SELECT user_version FROM pragma_user_version;
pub fn pragma_query<F>(
&self,
schema_name: Option<DatabaseName<'_>>,
pragma_name: &str,
f: F,
) -> Result<(), Error>
pub fn pragma_query<F>( &self, schema_name: Option<DatabaseName<'_>>, pragma_name: &str, f: F, ) -> Result<(), Error>
Query the current rows/values of pragma_name
.
Prefer PRAGMA function introduced in SQLite 3.20:
SELECT * FROM pragma_collation_list;
pub fn pragma<F, V>(
&self,
schema_name: Option<DatabaseName<'_>>,
pragma_name: &str,
pragma_value: V,
f: F,
) -> Result<(), Error>
pub fn pragma<F, V>( &self, schema_name: Option<DatabaseName<'_>>, pragma_name: &str, pragma_value: V, f: F, ) -> Result<(), Error>
Query the current value(s) of pragma_name
associated to
pragma_value
.
This method can be used with query-only pragmas which need an argument
(e.g. table_info('one_tbl')
) or pragmas which returns value(s)
(e.g. integrity_check
).
Prefer PRAGMA function introduced in SQLite 3.20:
SELECT * FROM pragma_table_info(?1);
pub fn pragma_update<V>(
&self,
schema_name: Option<DatabaseName<'_>>,
pragma_name: &str,
pragma_value: V,
) -> Result<(), Error>where
V: ToSql,
pub fn pragma_update<V>(
&self,
schema_name: Option<DatabaseName<'_>>,
pragma_name: &str,
pragma_value: V,
) -> Result<(), Error>where
V: ToSql,
Set a new value to pragma_name
.
Some pragmas will return the updated value which cannot be retrieved with this method.
pub fn pragma_update_and_check<F, T, V>(
&self,
schema_name: Option<DatabaseName<'_>>,
pragma_name: &str,
pragma_value: V,
f: F,
) -> Result<T, Error>
pub fn pragma_update_and_check<F, T, V>( &self, schema_name: Option<DatabaseName<'_>>, pragma_name: &str, pragma_value: V, f: F, ) -> Result<T, Error>
Set a new value to pragma_name
and return the updated value.
Only few pragmas automatically return the updated value.
pub fn transaction(&mut self) -> Result<Transaction<'_>, Error>
pub fn transaction(&mut self) -> Result<Transaction<'_>, Error>
Begin a new transaction with the default behavior (DEFERRED).
The transaction defaults to rolling back when it is dropped. If you
want the transaction to commit, you must call
commit
or
set_drop_behavior(DropBehavior::Commit)
.
§Example
fn perform_queries(conn: &mut Connection) -> Result<()> {
let tx = conn.transaction()?;
do_queries_part_1(&tx)?; // tx causes rollback if this fails
do_queries_part_2(&tx)?; // tx causes rollback if this fails
tx.commit()
}
§Failure
Will return Err
if the underlying SQLite call fails.
pub fn transaction_with_behavior(
&mut self,
behavior: TransactionBehavior,
) -> Result<Transaction<'_>, Error>
pub fn transaction_with_behavior( &mut self, behavior: TransactionBehavior, ) -> Result<Transaction<'_>, Error>
Begin a new transaction with a specified behavior.
See transaction
.
§Failure
Will return Err
if the underlying SQLite call fails.
pub fn unchecked_transaction(&self) -> Result<Transaction<'_>, Error>
pub fn unchecked_transaction(&self) -> Result<Transaction<'_>, Error>
Begin a new transaction with the default behavior (DEFERRED).
Attempt to open a nested transaction will result in a SQLite error.
Connection::transaction
prevents this at compile time by taking &mut self
, but Connection::unchecked_transaction()
may be used to defer
the checking until runtime.
See [Connection::transaction
] and [Transaction::new_unchecked
]
(which can be used if the default transaction behavior is undesirable).
§Example
fn perform_queries(conn: Rc<Connection>) -> Result<()> {
let tx = conn.unchecked_transaction()?;
do_queries_part_1(&tx)?; // tx causes rollback if this fails
do_queries_part_2(&tx)?; // tx causes rollback if this fails
tx.commit()
}
§Failure
Will return Err
if the underlying SQLite call fails. The specific
error returned if transactions are nested is currently unspecified.
pub fn savepoint(&mut self) -> Result<Savepoint<'_>, Error>
pub fn savepoint(&mut self) -> Result<Savepoint<'_>, Error>
Begin a new savepoint with the default behavior (DEFERRED).
The savepoint defaults to rolling back when it is dropped. If you want
the savepoint to commit, you must call commit
or
set_drop_behavior(DropBehavior::Commit)
.
§Example
fn perform_queries(conn: &mut Connection) -> Result<()> {
let sp = conn.savepoint()?;
do_queries_part_1(&sp)?; // sp causes rollback if this fails
do_queries_part_2(&sp)?; // sp causes rollback if this fails
sp.commit()
}
§Failure
Will return Err
if the underlying SQLite call fails.
pub fn savepoint_with_name<T>(
&mut self,
name: T,
) -> Result<Savepoint<'_>, Error>
pub fn savepoint_with_name<T>( &mut self, name: T, ) -> Result<Savepoint<'_>, Error>
pub fn transaction_state(
&self,
db_name: Option<DatabaseName<'_>>,
) -> Result<TransactionState, Error>
pub fn transaction_state( &self, db_name: Option<DatabaseName<'_>>, ) -> Result<TransactionState, Error>
Determine the transaction state of a database
pub fn set_transaction_behavior(&mut self, behavior: TransactionBehavior)
pub fn set_transaction_behavior(&mut self, behavior: TransactionBehavior)
Set the default transaction behavior for the connection.
§Note
This will only apply to transactions initiated by transaction
or unchecked_transaction
.
§Example
fn perform_queries(conn: &mut Connection) -> Result<()> {
conn.set_transaction_behavior(TransactionBehavior::Immediate);
let tx = conn.transaction()?;
do_queries_part_1(&tx)?; // tx causes rollback if this fails
do_queries_part_2(&tx)?; // tx causes rollback if this fails
tx.commit()
}
pub fn execute_batch(&self, sql: &str) -> Result<(), Error>
pub fn execute_batch(&self, sql: &str) -> Result<(), Error>
Convenience method to run multiple SQL statements (that cannot take any parameters).
§Example
fn create_tables(conn: &Connection) -> Result<()> {
conn.execute_batch(
"BEGIN;
CREATE TABLE foo(x INTEGER);
CREATE TABLE bar(y TEXT);
COMMIT;",
)
}
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub fn execute<P>(&self, sql: &str, params: P) -> Result<usize, Error>where
P: Params,
pub fn execute<P>(&self, sql: &str, params: P) -> Result<usize, Error>where
P: Params,
Convenience method to prepare and execute a single SQL statement.
On success, returns the number of rows that were changed or inserted or
deleted (via sqlite3_changes
).
§Example
§With positional params
fn update_rows(conn: &Connection) {
match conn.execute("UPDATE foo SET bar = 'baz' WHERE qux = ?1", [1i32]) {
Ok(updated) => println!("{} rows were updated", updated),
Err(err) => println!("update failed: {}", err),
}
}
§With positional params of varying types
fn update_rows(conn: &Connection) {
match conn.execute(
"UPDATE foo SET bar = 'baz' WHERE qux = ?1 AND quux = ?2",
params![1i32, 1.5f64],
) {
Ok(updated) => println!("{} rows were updated", updated),
Err(err) => println!("update failed: {}", err),
}
}
§With named params
fn insert(conn: &Connection) -> Result<usize> {
conn.execute(
"INSERT INTO test (name) VALUES (:name)",
&[(":name", "one")],
)
}
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub fn path(&self) -> Option<&str>
pub fn path(&self) -> Option<&str>
Returns the path to the database file, if one exists and is known.
Returns Some("")
for a temporary or in-memory database.
Note that in some cases PRAGMA database_list is likely to be more robust.
pub fn last_insert_rowid(&self) -> i64
pub fn last_insert_rowid(&self) -> i64
Get the SQLite rowid of the most recent successful INSERT.
Uses sqlite3_last_insert_rowid under the hood.
pub fn query_row<T, P, F>(&self, sql: &str, params: P, f: F) -> Result<T, Error>
pub fn query_row<T, P, F>(&self, sql: &str, params: P, f: F) -> Result<T, Error>
Convenience method to execute a query that is expected to return a single row.
§Example
fn preferred_locale(conn: &Connection) -> Result<String> {
conn.query_row(
"SELECT value FROM preferences WHERE name='locale'",
[],
|row| row.get(0),
)
}
If the query returns more than one row, all rows except the first are ignored.
Returns Err(QueryReturnedNoRows)
if no results are returned. If the
query truly is optional, you can call .optional()
on the result of
this to get a Result<Option<T>>
.
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub fn query_row_and_then<T, E, P, F>(
&self,
sql: &str,
params: P,
f: F,
) -> Result<T, E>
pub fn query_row_and_then<T, E, P, F>( &self, sql: &str, params: P, f: F, ) -> Result<T, E>
Convenience method to execute a query that is expected to return a
single row, and execute a mapping via f
on that returned row with
the possibility of failure. The Result
type of f
must implement
std::convert::From<Error>
.
§Example
fn preferred_locale(conn: &Connection) -> Result<String> {
conn.query_row_and_then(
"SELECT value FROM preferences WHERE name='locale'",
[],
|row| row.get(0),
)
}
If the query returns more than one row, all rows except the first are ignored.
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub fn prepare(&self, sql: &str) -> Result<Statement<'_>, Error>
pub fn prepare(&self, sql: &str) -> Result<Statement<'_>, Error>
Prepare a SQL statement for execution.
§Example
fn insert_new_people(conn: &Connection) -> Result<()> {
let mut stmt = conn.prepare("INSERT INTO People (name) VALUES (?1)")?;
stmt.execute(["Joe Smith"])?;
stmt.execute(["Bob Jones"])?;
Ok(())
}
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub fn prepare_with_flags(
&self,
sql: &str,
flags: PrepFlags,
) -> Result<Statement<'_>, Error>
pub fn prepare_with_flags( &self, sql: &str, flags: PrepFlags, ) -> Result<Statement<'_>, Error>
Prepare a SQL statement for execution.
§Failure
Will return Err
if sql
cannot be converted to a C-compatible string
or if the underlying SQLite call fails.
pub unsafe fn handle(&self) -> *mut sqlite3
pub unsafe fn handle(&self) -> *mut sqlite3
Get access to the underlying SQLite database connection handle.
§Warning
You should not need to use this function. If you do need to, please open an issue on the rusqlite repository and describe your use case.
§Safety
This function is unsafe because it gives you raw access
to the SQLite connection, and what you do with it could impact the
safety of this Connection
.
pub fn get_interrupt_handle(&self) -> InterruptHandle
pub fn get_interrupt_handle(&self) -> InterruptHandle
Get access to a handle that can be used to interrupt long-running queries from another thread.
pub fn changes(&self) -> u64
pub fn changes(&self) -> u64
Return the number of rows modified, inserted or deleted by the most recently completed INSERT, UPDATE or DELETE statement on the database connection.
pub fn total_changes(&self) -> u64
pub fn total_changes(&self) -> u64
Return the total number of rows modified, inserted or deleted by all completed INSERT, UPDATE or DELETE statements since the database connection was opened, including those executed as part of trigger programs.
pub fn is_autocommit(&self) -> bool
pub fn is_autocommit(&self) -> bool
Test for auto-commit mode. Autocommit mode is on by default.
pub fn cache_flush(&self) -> Result<(), Error>
pub fn cache_flush(&self) -> Result<(), Error>
Flush caches to disk mid-transaction
pub fn is_readonly(&self, db_name: DatabaseName<'_>) -> Result<bool, Error>
pub fn is_readonly(&self, db_name: DatabaseName<'_>) -> Result<bool, Error>
Determine if a database is read-only
pub fn db_name(&self, index: usize) -> Result<String, Error>
pub fn db_name(&self, index: usize) -> Result<String, Error>
Return the schema name for a database connection
§Failure
Return an Error::InvalidDatabaseIndex
if index
is out of range.
pub fn is_interrupted(&self) -> bool
pub fn is_interrupted(&self) -> bool
Determine whether an interrupt is currently in effect