DexieError
since v.1.3.3
Acts as the base class for exceptions that can be returned in rejected Dexie promises.
Inheritance Hierarchy
Dexie.DexieError
Dexie.AbortError
Dexie.BulkError
Dexie.ConstraintError
Dexie.DatabaseClosedError
Dexie.DataCloneError
Dexie.DataError
Dexie.IncompatiblePromiseError (Obsolete since v2.0.0)
Dexie.InternalError
Dexie.InvalidAccessError
Dexie.InvalidArgumentError
Dexie.InvalidStateError
Dexie.InvalidTableError
Dexie.MissingAPIError
Dexie.ModifyError
Dexie.NoSuchDatabaseError
Dexie.NotFoundError
Dexie.OpenFailedError
Dexie.QuotaExceededError
Dexie.PrematureCommitError
Dexie.ReadOnlyError
Dexie.SchemaError
Dexie.SubTransactionError
Dexie.TimeoutError
Dexie.TransactionInactiveError
Dexie.UpgradeError
Dexie.UnknownError
Dexie.UnsupportedError
Dexie.VersionChangeError
Dexie.VersionError
Sample
Sample: switch(error.name)
Properties
message: string
Detailed message
inner?: any
Inner exception instance (if any)
stack?: string
Can be present if the error was thrown. If signaled, there wont be any call stack.
Catching Errors Affect Transaction
If explicitly catching an error, the ongoing transaction will NOT abort. If that is not your desire, for example if you are just catching the error for logging purpose, you should rethrow the error after logging it.
The catch effect also applies when using yield or async / await and a standard try..catch.