Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Warning: This interface was removed from the specification and was replaced by usage of DOMException.

In the IndexedDB API, an IDBDatabaseException object represents exception conditions that can be encountered while performing database operations.


Attribute Type Description
code unsigned short The most appropriate error code for the condition.
message DOMString Error message describing the exception raised.


Note: Do not rely on the numeric values of the constants, which might change as the specifications continue to change. Use the constant names instead.

Constant Value Description
ABORT_ERR 8 A request was aborted, for example, through a call to IDBTransaction.abort.
CONSTRAINT_ERR 4 A mutation operation in the transaction failed because a constraint was not satisfied. For example, an object, such as an object store or index, already exists and a request attempted to create a new one.
DATA_ERR 5 Data provided to an operation does not meet requirements.
NON_TRANSIENT_ERR 2 An operation was not allowed on an object. Unless the cause of the error is corrected, retrying the same operation would result in failure.

An operation was called on an object where it is not allowed or at a time when it is not allowed. It also occurs if a request is made on a source object that has been deleted or removed.

More specific variants of this error includes: TRANSACTION_INACTIVE_ERR and READ_ONLY_ERR.

NOT_FOUND_ERR 3 The operation failed because the requested database object could not be found; for example, an object store did not exist but was being opened.
QUOTA_ERR 11 Either there's not enough remaining storage space or the storage quota was reached and the user declined to give more space to the database.
READ_ONLY_ERR 9 A mutation operation was attempted in a READ_ONLY transaction.
TIMEOUT_ERR 10 A lock for the transaction could not be obtained in a reasonable time.
TRANSACTION_INACTIVE_ERR 7 A request was made against a transaction that is either not currently active or is already finished.
UNKNOWN_ERR 1 The operation failed for reasons unrelated to the database itself, and it is not covered by any other error code--for example, a failure due to disk IO errors.
VER_ERR 12 A request to open a database with a version lower than the one it already has. This can only happen with IDBOpenDBRequest.

Browser compatibility

BCD tables only load in the browser