In the IndexedDB API
object represents exception conditions that can be encountered while performing database operations.
A request was aborted, for example, through a call to
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 provided to an operation does not meet requirements.
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:
The operation failed, because the requested database object could not be found; for example, an object store did not exist but was being opened.
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.
A mutation operation was attempted in a
A lock for the transaction could not be obtained in a reasonable time.
A request was made against a transaction that is either not currently active or is already finished.
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.
A request to open a database with a version lower than the one it already has. This can only happen with
The most appropriate error code for the condition.
Error message describing the exception raised.