IDBDatabase: transaction() method

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015.

Note: This feature is available in Web Workers.

The transaction method of the IDBDatabase interface immediately returns a transaction object (IDBTransaction) containing the IDBTransaction.objectStore method, which you can use to access your object store.

Syntax

js
transaction(storeNames)
transaction(storeNames, mode)
transaction(storeNames, mode, options)

Parameters

storeNames

The names of object stores that are in the scope of the new transaction, declared as an array of strings. Specify only the object stores that you need to access. If you need to access only one object store, you can specify its name as a string. Therefore the following lines are equivalent:

js
db.transaction(["my-store-name"]);
db.transaction("my-store-name");

If you need to access all object stores in the database, you can use the property IDBDatabase.objectStoreNames:

js
const transaction = db.transaction(db.objectStoreNames);

Passing an empty array will throw an exception.

mode Optional

The types of access that can be performed in the transaction. Transactions are opened in one of three modes:

readonly

Open a transaction for reading from an object store. This is the default mode.

readwrite

Open a transaction for both reading and writing from an object store. This should only be used if need to write into the database.

readwriteflush

Force a transaction to flush to disk before delivering the complete event. This might be used for storing critical data that cannot be recomputed later.

options Optional

Object defining additional options, including:

durability

One of the three string-literal values below:

"strict"

The user agent may consider that the transaction has successfully committed only after verifying that all outstanding changes have been successfully written to a persistent storage medium. This is recommended where the risk of data loss outweighs the impact of its use on performance and power (compared to relaxed).

"relaxed"

The user agent may consider that the transaction has successfully committed as soon as all outstanding changes have been written to the operating system, without subsequent verification. This offers better performance than strict, and is recommended for ephemeral data such as caches or quickly changing records.

"default"

The user agent should use its default durability behavior for the storage bucket. This is the default for transactions if not otherwise specified.

Return value

An IDBTransaction object.

Exceptions

InvalidStateError DOMException

Thrown if the close() method has previously been called on this IDBDatabase instance.

NotFoundError DOMException

Thrown if an object store specified in the 'storeNames' parameter has been deleted or removed.

TypeError

Thrown if the value for the mode parameter is invalid.

InvalidAccessError DOMException

Thrown if the function was called with an empty list of store names.

Examples

In this example we open a database connection, then use transaction() to open a transaction on the database. For a complete example, see our To-do Notifications app (view example live).

js
let db;

// Let us open our database
const DBOpenRequest = window.indexedDB.open("toDoList", 4);

DBOpenRequest.onsuccess = (event) => {
  note.appendChild(document.createElement("li")).textContent =
    "Database initialized.";

  // store the result of opening the database in the db variable.
  // This is used a lot below
  db = DBOpenRequest.result;

  // Run the displayData() function to populate the task list with
  // all the to-do list data already in the IDB
  displayData();
};

// open a read/write db transaction, ready for adding the data
const transaction = db.transaction(["toDoList"], "readwrite");

// report on the success of opening the transaction
transaction.oncomplete = (event) => {
  note.appendChild(document.createElement("li")).textContent =
    "Transaction completed: database modification finished.";
};

transaction.onerror = (event) => {
  note.appendChild(document.createElement("li")).textContent =
    "Transaction not opened due to error. Duplicate items not allowed.";
};

// you would then go on to do something to this database
// via an object store
const objectStore = transaction.objectStore("toDoList");
// etc.

Specifications

Specification
Indexed Database API 3.0
# ref-for-dom-idbdatabase-transaction③

Browser compatibility

desktop mobile
Chrome
Edge
Firefox
Opera
Safari
Chrome Android
Firefox for Android
Opera Android
Safari on iOS
Samsung Internet
WebView Android
WebView on iOS
transaction
Chrome – Full support
Chrome 23 (Release date: 2012-11-06)
footnote Full support
Edge – Full support
Edge 12 (Release date: 2015-07-29)
footnote Full support
Firefox – Full support
Firefox 10 (Release date: 2012-01-31)
footnote Full support
Opera – Full support
Opera 15 (Release date: 2013-07-02)
footnote Full support
Safari – Full support
Safari 8 (Release date: 2014-10-16)
footnote Full support
Chrome Android – Full support
Chrome Android 25 (Release date: 2013-02-27)
footnote Full support
Firefox for Android – Full support
Firefox for Android 22 (Release date: 2013-06-25)
footnote Full support
Opera Android – Full support
Opera Android 14 (Release date: 2013-05-21)
footnote Full support
Safari on iOS – Full support
Safari on iOS 8 (Release date: 2014-09-17)
footnote Full support
Samsung Internet – Full support
Samsung Internet 1.5 (Release date: 2013-09-25)
footnote Full support
WebView Android – Full support
WebView Android 4.4 (Release date: 2013-12-09)
footnote Full support
WebView on iOS – Full support
WebView on iOS 8 (Release date: 2014-09-17)
footnote Full support
mode parameter supports readwriteflush
Experimental Non-standard
Chrome – No support
Chrome
footnote No support
Edge – No support
Edge
footnote No support
Firefox – No support
Firefox 40 (Release date: 2015-08-11)
disabled
disabled From version 40 users must explicitly set the dom.indexedDB.experimental preference to true. To change preferences in Firefox, visit about:config.
Opera – No support
Opera
footnote No support
Safari – No support
Safari
footnote No support
Chrome Android – No support
Chrome Android
footnote No support
Firefox for Android – No support
Firefox for Android
footnote No support
Opera Android – No support
Opera Android
footnote No support
Safari on iOS – No support
Safari on iOS
footnote No support
Samsung Internet – No support
Samsung Internet
footnote No support
WebView Android – No support
WebView Android
footnote No support
WebView on iOS – No support
WebView on iOS
footnote No support

Legend

Tip: you can click/tap on a cell for more information.

Full support
Full support
No support
No support
Experimental. Expect behavior to change in the future.
Non-standard. Check cross-browser support before using.
User must explicitly enable this feature.

See also