Note that as of Firefox 40, IndexedDB transactions have relaxed durability guarantees to increase performance (see bug 1112702.) Previously in a
IDBTransaction.oncomplete was fired only when all data was guaranteed to have been flushed to disk. In Firefox 40+ the
complete event is fired after the OS has been told to write the data but potentially before that data has actually been flushed to disk. The
complete event may thus be delivered quicker than before, however, there exists a small chance that the entire transaction will be lost if the OS crashes or there is a loss of system power before the data is flushed to disk. Since such catastrophic events are rare most consumers should not need to concern themselves further.
Returns one of several types of error when there is an unsuccessful transaction. This property is
null if the transaction is not finished, is finished and successfully committed, or was aborted with
The mode for isolating access to data in the object stores that are in the scope of the transaction. For possible values, see the Constants section below. The default value is
DOMStringList of the names of
The event handler for the
complete event, thrown when the transaction completes successfully.