Enum DatabaseError 

#[non_exhaustive]
pub enum DatabaseError {
    Storage(String),
    Sql {
        message: String,
    },
    AsyncContext,
    EngineUnavailable(Engine),
    Reentrant,
}

Errors from a Database operation.

thiserror-derived per docs/CODE_STANDARDS.md: callers match on the variant rather than only displaying it.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

Storage(String)

A database path couldn’t be resolved, created, or otherwise accessed — an unset data directory, an invalid database name, or an underlying filesystem failure.

Sql

The SQL engine reported a statement failure (a syntax error, a constraint violation, a type mismatch — whatever the engine itself surfaces).

Fields

message: String

The engine-reported failure message.

AsyncContext

Reserved for async-bridging backends: a synchronous call ran from inside an async runtime worker thread, which the turso engine’s async bridge can’t safely block on. engine-sqlite’s connection never raises this — declared now so this enum stays additive-stable once the turso backend needs it.

EngineUnavailable(Engine)

The requested (or resolved-default) Engine isn’t compiled into this build.

Reserved, and unconstructable by any of today’s code paths: an Engine variant only exists at all when the feature compiling its backend is on, so an engine a caller can name is by construction compiled in — see Database::open’s own Errors section for what the neither-engine-compiled build reports instead.

Reentrant

A call re-entered a Database handle the calling thread already holds — typically an execute/query/transaction issued on a captured (e.g. Arc-shared) handle from inside that same handle’s Database::transaction closure.

Reported rather than deadlocking on the handle’s non-reentrant connection mutex: run statements inside a transaction through the Transaction handle the closure is given. Calls from other threads are unaffected — they queue on the mutex as the module doc’s Threading model section promises.

Trait Implementations

impl Debug for DatabaseError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for DatabaseError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for DatabaseError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.