Indexed Database API 2.0

1. Introduction

User agents need to store large numbers of objects locally in order to satisfy off-line data requirements of Web applications. [WEBSTORAGE] is useful for storing pairs of keys and their corresponding values. However, it does not provide in-order retrieval of keys, efficient searching over values, or storage of duplicate values for a key.

This specification provides a concrete API to perform advanced key-value data management that is at the heart of most sophisticated query processors. It does so by using transactional databases to store keys and their corresponding values (one or more per key), and providing a means of traversing keys in a deterministic order. This is often implemented through the use of persistent B-tree data structures that are considered efficient for insertion and deletion as well as in-order traversal of very large numbers of data records.

In the following example, the API is used to access a "library" database that holds books stored by their "isbn" attribute. Additionally, an index is maintained on the "title" attribute of the objects stored in the object store. This index can be used to look up books by title, and enforces a uniqueness constraint. Another index is maintained on the "author" attribute of the objects, and can be used to look up books by author.

A connection to the database is opened. If the "library" database did not already exist, it is created and an event handler creates the object store and indexes. Finally, the opened connection is saved for use in subsequent examples.

var request = indexedDB.open("library");

request.onupgradeneeded = function() {
  // The database did not previously exist, so create object stores and indexes.
  var db = request.result;
  var store = db.createObjectStore("books", {keyPath: "isbn"});
  var titleIndex = store.createIndex("by_title", "title", {unique: true});
  var authorIndex = store.createIndex("by_author", "author");

  // Populate with initial data.
  store.put({title: "Quarry Memories", author: "Fred", isbn: 123456});
  store.put({title: "Water Buffaloes", author: "Fred", isbn: 234567});
  store.put({title: "Bedrock Nights", author: "Barney", isbn: 345678});
};

request.onsuccess = function() {
  db = request.result;
};

The following example populates the database using a transaction.

var tx = db.transaction("books", "readwrite");
var store = tx.objectStore("books");

store.put({title: "Quarry Memories", author: "Fred", isbn: 123456});
store.put({title: "Water Buffaloes", author: "Fred", isbn: 234567});
store.put({title: "Bedrock Nights", author: "Barney", isbn: 345678});

tx.oncomplete = function() {
  // All requests have succeeded and the transaction has committed.
};

The following example looks up a single book in the database by title using an index.

var tx = db.transaction("books", "readonly");
var store = tx.objectStore("books");
var index = store.index("by_title");

var request = index.get("Bedrock Nights");
request.onsuccess = function() {
  var matching = request.result;
  if (matching !== undefined) {
    // A match was found.
    report(matching.isbn, matching.title, matching.author);
  } else {
    // No match was found.
    report(null);
  }
};

The following example looks up all books in the database by author using an index and a cursor.

var tx = db.transaction("books", "readonly");
var store = tx.objectStore("books");
var index = store.index("by_author");

var request = index.openCursor(IDBKeyRange.only("Fred"));
request.onsuccess = function() {
  var cursor = request.result;
  if (cursor) {
    // Called for each matching record.
    report(cursor.value.isbn, cursor.value.title, cursor.value.author);
    cursor.continue();
  } else {
    // No more matching records.
    report(null);
  }
};

The following example shows how errors could be handled when a request fails.

var tx = db.transaction("books", "readwrite");
var store = tx.objectStore("books");
var request = store.put({title: "Water Buffaloes", author: "Slate", isbn: 987654});
request.onerror = function() {
  // The uniqueness constraint of the "by_title" index failed.
  report(request.error);
  // Could call request.preventDefault() to prevent the transaction from aborting.
};
tx.onabort = function() {
  // Otherwise the transaction will automatically abort due the failed request.
  report(tx.error);
};

The database connection may be closed when it is no longer needed.

db.close();

In the future, the database may have grown to contain other object stores and indexes. The following example shows one way to handle opening an older version of the database.

var request = indexedDB.open("library", 3); // Request version 3.

request.onupgradeneeded = function(event) {
  var db = request.result;
  if (event.oldVersion < 1) {
    // Version 1 is the first version of the database.
    var store = db.createObjectStore("books", {keyPath: "isbn"});
    var titleIndex = store.createIndex("by_title", "title", {unique: true});
    var authorIndex = store.createIndex("by_author", "author");
  }
  if (event.oldVersion < 2) {
    // Version 2 introduces a new index of books by year.
    var bookStore = request.transaction.objectStore("books");
    var yearIndex = bookStore.createIndex("by_year", "year");
  }
  if (event.oldVersion < 3) {
    // Version 3 introduces a new object store for magazines with two indexes.
    var magazines = db.createObjectStore("magazines");
    var publisherIndex = magazines.createIndex("by_publisher", "publisher");
    var frequencyIndex = magazines.createIndex("by_frequency", "frequency");
  }
};

request.onsuccess = function() {
  db = request.result; // db.version will be 3.
};

2. Constructs

A sorted list is a DOMStringList containing strings sorted in ascending order by code unit.

2.1. Database

A database’s origin is the same as the origin of the document or worker. Each origin has an associated set of databases.

The database origin is not affected by changes to the Document's domain.

Each origin has an associated set of databases. A database has zero or more object stores which hold the data stored in the database.

A database has a name which identifies it within a specific origin. The name can be any string value, including the empty string, and stays constant for the lifetime of the database. Database names are always compared in a case-sensitive manner, as opaque sequences of 16-bit code units. Implementations must support all names.

A database has a version. When a database is first created, its version is 0 (zero).

2.1.1. Database Connection

Script does not interact with databases directly. Instead, script has indirect access via a connection. A connection object can be used to manipulate the objects of that database. It is also the only way to obtain a transaction for that database.

The act of opening a database creates a connection. There may be multiple connections to a given database at any given time.

A connection has a version, which is set when the connection is created. It remains constant for the lifetime of the connection unless an upgrade is aborted, in which case it is set to the previous version of the database. Once the connection is closed the version does not change.

Each connection has a close pending flag which is initially unset.

When a connection is initially created it is in opened state. The connection can be closed through several means. If the execution context where the connection was created is destroyed (for example due to the user navigating away from that page), the connection is closed. The connection can also be closed explicitly using the steps for closing a database connection. When the connection is closed the close pending flag is always set if it hasn’t already been.

A connection may be closed by a user agent in exceptional circumstances, for example due to loss of access to the file system or a permission change. If this occurs the user agent must run the steps for closing a database connection with the connection and with the forced flag set.

A connection has an object store set, which is initialized to the set of object stores in the associated database when the connection is created. The contents of the set will remain constant except when an upgrade transaction is running.

A connection's get the parent algorithm returns null.

2.2. Object Store

An object store is the primary storage mechanism for storing data in a database.

Each database has a set of object stores. The set of object stores can be changed, but only using an upgrade transaction, i.e. in response to an upgradeneeded event. When a new database is created it doesn’t contain any object stores.

An object store has a list of records which hold the data stored in the object store. Each record consists of a key and a value. The list is sorted according to key in ascending order. There can never be multiple records in a given object store with the same key.

An object store has a name. The name can be any string value, including the empty string. At any one time, the name is unique within the database to which it belongs. Object store names are always compared in a case-sensitive manner, as opaque sequences of 16-bit code units.

An object store optionally has a key path. If the object store has a key path it is said to use in-line keys. Otherwise it is said to use out-of-line keys.

An object store optionally has a key generator.

An object store can derive a key for a record from one of three sources:

A key generator. A key generator generates a monotonically increasing numbers every time a key is needed.
Keys can be derived via a key path.
Keys can also be explicitly specified when a value is stored in the object store.

2.2.1. Object Store Handle

Script does not interact with object stores directly. Instead, within a transaction, script has indirect access via an object store handle.

An object store handle has an associated object store and an associated transaction. Multiple handles may be associated with the same object store in different transactions, but there must be only one object store handle associated with a particular object store within a transaction.

An object store handle has an index set, which is initialized to the set of indexes that reference the associated object store when the object store handle is created. The contents of the set will remain constant except when an upgrade transaction is running.

An object store handle has a name, which is initialized to the name of the associated object store when the object store handle is created. The name will remain constant except when an upgrade transaction is running.

2.3. Values

Each record is associated with a value. User agents must support any ECMAScript [ECMA-262] value supported by the structured clone algorithm [HTML]. This includes simple types such as String primitive values and Date objects as well as Object and Array instances, File objects, Blob objects, ImageData objects, and so on. Record values are stored and retrieved by value rather than by reference; later changes to a value have no effect on the record stored in the database.

2.4. Keys

In order to efficiently retrieve records stored in an indexed database, each record is organized according to its key.

A key has an associated type which is one of: number, date, string, binary, or array.

A key also has an associated value, which will be either: an unrestricted double if type is number or date, a DOMString if type is string, a list of octets if type is binary, or a list of other keys if type is array.

An ECMAScript [ECMA-262] value can be converted to a key by following the steps to convert a value to a key.

An array key is a key with type array. The subkeys of an array key are the members of the array key's value list.

To compare two keys a and b, run these steps:

Let ta be the type of a.
Let tb be the type of b.
If ta is array and tb is binary, string, date or number, return 1.
If tb is array and ta is binary, string, date or number, return -1.
If ta is binary and tb is string, date or number, return 1.
If tb is binary and ta is string, date or number, return -1.
If ta is string and tb is date or number, return 1.
If tb is string and ta is date or number, return -1.
If ta is date and tb is number, return 1.
If tb is date and ta is number, return -1.
Assert: ta and tb are equal.
Let va be the value of a.
Let vb be the value of b.
Switch on ta:
number
date
1. If va is greater than vb, then return 1.
2. If va is less than vb, then return -1.
3. Return 0
string
1. Let length be the lesser of va’s length and vb’s length.
2. Let i be 0.
3. While i is less than length, run these substeps:
  1. Let u be the code unit of va at index i
  2. Let v be the code unit of vb at index i
  3. If u is greater than v then return 1
  4. If u is less than v then return -1
  5. Increase i by 1
4. If va’s length is greater than vb’s length, then return 1
5. If va’s length is less than vb’s length, then return -1
6. Return 0
binary
1. Let length be the lesser of va’s length and vb’s length.
2. Let i be 0.
3. While i is less than length, run these substeps:
  1. Let u be the octet in va at index i
  2. Let v be the octet in vb at index i
  3. If u is greater than v then return 1
  4. If u is less than v then return -1
  5. Increase i by 1
4. If va’s length is greater than vb’s length, then return 1
5. If va’s length is less than vb’s length, then return -1
6. Return 0
array
1. Let length be the lesser of va’s length and vb’s length.
2. Let i be 0.
3. While i is less than length, run these substeps:
  1. Let u be the key in va at index i
  2. Let v be the key in vb at index i
  3. Let c be the result of recursively running the steps to compare two keys with u and v
  4. If c is not 0, return c
  5. Increase i by 1
4. If va’s length is greater than vb’s length, then return 1
5. If va’s length is less than vb’s length, then return -1
6. Return 0

The key a is greater than the key b if the result of running the steps to compare two keys with a and b is 1.

The key a is less than the key b if the result of running the steps to compare two keys with a and b is -1.

The key a is equal to the key b if the result of running the steps to compare two keys with a and b is 0.

2.5. Key Path

A key path is a DOMString or sequence<DOMString> that defines how to extract a key from a value. A valid key path is one of:

An empty DOMString.
An identifier, which is a DOMString matching the IdentifierName production from the ECMAScript Language Specification [ECMA-262].
A DOMString consisting of two or more identifiers separated by periods (ASCII character code 46, U+002E FULL STOP).
A non-empty sequence<DOMString> containing only strings conforming to the above requirements.

Key path values can only be accessed from properties explicitly copied by the structured clone algorithm, as well as the following type-specific properties:

Type	Properties
`Blob`	`size`, `type`
`File`	`name`, `lastModified`, `lastModifiedDate`
Array	`length`
String	`length`

2.6. Index

It is sometimes useful to retrieve records in an object store through other means than their key. An index allows looking up records in an object store using properties of the values in the object stores records.

An index is a specialized persistent key-value storage and has a referenced object store. The index has a list of records which hold the data stored in the index. The records in an index are automatically populated whenever records in the referenced object store are inserted, updated or deleted. There can be several indexes referencing the same object store, in which changes to the object store cause all such indexes to get updated.

The values in the index’s records are always values of keys in the index’s referenced object store. The keys are derived from the referenced object store’s values using a key path. If a given record with key X in the object store referenced by the index has the value A, and evaluating the index’s key path on A yields the result Y, then the index will contain a record with key Y and value X.

For example, if an index’s referenced object store contains a record with the key 123 and the value

{ first:
  "Alice", last: "Smith" }

, and the index’s key path is "first" then the index would contain a record with the key "Alice" and the value 123.

Records in an index are said to have a referenced value. This is the value of the record in the index’s referenced object store which has a key equal to the index’s record’s value. So in the example above, the record in the index whose key is Y and value is X has a referenced value of A.

In the preceding example, the record in the index with key "Alice" and value 123 would have a referenced value of

{ first: "Alice", last: "Smith"
  }

The records in an index are always sorted according to the record's key. However unlike object stores, a given index can contain multiple records with the same key. Such records are additionally sorted according to the index's record's value (meaning the key of the record in the referenced object store).

An index has a name. The name can be any string value, including the empty string. At any one time, the name is unique within index’s referenced object store. Index names are always compared in a case-sensitive manner, as opaque sequences of 16-bit code units.

An index has a unique flag. When this flag is set, the index enforces that no two records in the index has the same key. If a record in the index’s referenced object store is attempted to be inserted or modified such that evaluating the index’s key path on the records new value yields a result which already exists in the index, then the attempted modification to the object store fails.

An index has a multiEntry flag. This flag affects how the index behaves when the result of evaluating the index’s key path yields an array key. If the multiEntry flag is unset, then a single record whose key is an array key is added to the index. If the multiEntry flag is true, then the one record is added to the index for each of the subkeys.

2.6.1. Index Handle

Script does not interact with indexes directly. Instead, within a transaction, script has indirect access via an index handle.

An index handle has an associated index and an associated object store handle. The transaction of an index handle is the transaction of its associated object store handle. Multiple handles may be associated with the same index in different transactions, but there must be only one index handle associated with a particular index within a transaction.

An index handle has a name, which is initialized to the name of the associated index when the index handle is created. The name will remain constant except when an upgrade transaction is running.

2.7. Transactions

A Transaction is used to interact with the data in a database. Whenever data is read or written to the database it is done by using a transaction.

Transactions offer some protection from application and system failures. A transaction may be used to store multiple data records or to conditionally modify certain data records. A transaction represents an atomic and durable set of data access and data mutation operations.

All transactions are created through a connection, which is the transaction’s connection.

A transaction has a scope that determines the object stores with which the transaction may interact. A transaction’s scope remains fixed for the lifetime of that transaction.

A transaction has a mode that determines which types of interactions can be performed upon that transaction. The mode is set when the transaction is created and remains fixed for the life of the transaction. A transaction's mode is one of the following:

"readonly": The transaction is only allowed to read data. No modifications can be done by this type of transaction. This has the advantage that several read-only transactions can run at the same time even if their scopes are overlapping, i.e. if they are using the same object stores. This type of transaction can be created any time once a database has been opened.
"readwrite": The transaction is allowed to read, modify and delete data from existing object stores. However object stores and indexes can’t be added or removed. Multiple "readwrite" transactions can’t run at the same time if their scopes are overlapping since that would mean that they can modify each other’s data in the middle of the transaction. This type of transaction can be created any time once a database has been opened.
"versionchange": The transaction is allowed to read, modify and delete data from existing object stores, and can also create and remove object stores and indexes. It is the only type of transaction that can do so. This type of transaction can’t be manually created, but instead is created automatically when an upgradeneeded event is fired.

A transaction has an active flag, which determines if new requests can be made against the transaction. A transaction is said to be active if its active flag is set.

A transaction has a request list of requests which have been made against the transaction.

A transaction has a error which is set if the transaction is aborted.

A transaction's get the parent algorithm returns the transaction’s connection.

A read-only transaction is a transaction with mode "readonly".

A read/write transaction is a transaction with mode "readwrite".

2.7.1. Transaction Lifetime

Transactions are expected to be short lived. This is encouraged by the automatic committing functionality described below.

The lifetime of a transaction is as follows:

A transaction is created with a scope and a mode. When a transaction is created its active flag is initially set.
The implementation must allow requests to be placed against the transaction whenever the active flag is set. This is the case even if the transaction has not yet been started. Until the transaction is started the implementation must not execute these requests; however, the implementation must keep track of the requests and their order. Requests may be placed against a transaction only while that transaction is active. If an attempt is made to place a request against a transaction when that transaction is not active, the implementation must reject the attempt by throwing a TransactionInactiveError.
Once an implementation is able to enforce the constraints defined for the transaction scope and mode, defined below, the implementation must queue a task to start the transaction asynchronously.
Once the transaction has been started the implementation can start executing the requests placed against the transaction. Unless otherwise defined, requests must be executed in the order in which they were made against the transaction. Likewise, their results must be returned in the order the requests were placed against a specific transaction. There is no guarantee about the order that results from requests in different transactions are returned. Similarly, the transaction modes ensure that two requests placed against different transactions can execute in any order without affecting what resulting data is stored in the database.
A transaction can be aborted at any time before it is finished, even if the transaction isn’t currently active or hasn’t yet started. When a transaction is aborted the implementation must undo (roll back) any changes that were made to the database during that transaction. This includes both changes to the contents of object stores as well as additions and removals of object stores and indexes.
A transaction can fail for reasons not tied to a particular request. For example due to IO errors when committing the transaction, or due to running into a quota limit where the implementation can’t tie exceeding the quota to a partcular request. In this case the implementation must run the steps for aborting a transaction using the transaction as transaction and the appropriate error type as error. For example if quota was exceeded then QuotaExceededError should be used as error, and if an IO error happened, UnknownError should be used as error.
When a transaction has been started and it can no longer become active, the implementation must attempt to commit it, as long as the transaction has not been aborted. This usually happens after all requests placed against the transaction have been executed and their returned results handled, and no new requests have been placed against the transaction. When a transaction is committed, the implementation must atomically write any changes to the database made by requests placed against the transaction. That is, either all of the changes must be written, or if an error occurs, such as a disk write error, the implementation must not write any of the changes to the database. If such an error occurs, the implementation must abort the transaction by following the steps for aborting a transaction, otherwise it must commit the transaction by following the steps for committing a transaction.
When a transaction is committed or aborted, it is said to be finished. If a transaction can’t be finished, for example due to the implementation crashing or the user taking some explicit action to cancel it, the implementation must abort the transaction.

The following constraints define when a transaction can be started:

Any number of read-only transactions are allowed to run concurrently, even if the transaction’s scope overlap and include the same object stores. As long as a read-only transaction is running, the data that the implementation returns through requests created with that transaction must remain constant. That is, two requests to read the same piece of data must yield the same result both for the case when data is found and the result is that data, and for the case when data is not found and a lack of data is indicated.

There are a number of ways that an implementation can ensure this. The implementation could prevent any read/write transaction, whose scope overlaps the scope of the read-only transaction, from starting until the read-only transaction finishes. Or the implementation could allow the read-only transaction to see a snapshot of the contents of the object stores which is taken when the read-only transaction started.
Similarly, implementations must ensure that a read/write transaction is only affected by changes to object stores that are made using the transaction itself. For example, the implementation must ensure that another transaction does not modify the contents of object stores in the read/write transaction’s scope. The implementation must also ensure that if the read/write transaction completes successfully, the changes written to object stores using the transaction can be committed to the database without merge conflicts. An implementation must not abort a transaction due to merge conflicts.
If multiple read/write transactions are attempting to access the same object store (i.e. if they have overlapping scope), the transaction that was created first must be the transaction which gets access to the object store first. Due to the requirements in the previous paragraph, this also means that it is the only transaction which has access to the object store until the transaction is finished.
Any transaction created after a read/write transaction must see the changes written by the read/write transaction. So if a read/write transaction, A, is created, and later another transaction B, is created, and the two transactions have overlapping scopes, then B must see any changes made to any object stores that are part of that overlapping scope. Due to the requirements in the previous paragraph, this also means that the B transaction does not have access to any object stores in that overlapping scope until the A transaction is finished.

Generally speaking, the above requirements mean that any transaction which has an overlapping scope with a read/write transaction and which was created after that read/write transaction, can’t run in parallel with that read/write transaction.
User agents must ensure a reasonable level of fairness across transactions to prevent starvation. For example, if multiple read-only transactions are started one after another the implementation must not indefinitely prevent a pending read/write transaction from starting.

2.7.2. Upgrade Transactions

An upgrade transaction is a transaction with mode "versionchange".

An upgrade transaction is automatically created when running steps for running an upgrade transaction after a connection is opened to a database giving a greater version than the current version. This transaction will be active inside the upgradeneeded event handler, allowing the creation of new object stores and indexes.

An upgrade transaction is never run concurrently with other transactions. When a database is opened with a version number higher than the current version, a new upgrade transaction is automatically created and made available through the open request when the upgradeneeded event is fired. The upgradeneeded event isn’t fired, and thus the upgrade transaction isn’t started, until all other connections to the same database are closed. This ensures that all other transactions are finished.

As long as an upgrade transaction is running, attempts to open more connections to the same database are delayed, and any attempts to use the same connection to start additional transactions will result in an exception being thrown. Thus upgrade transactions not only ensure that no other transactions are running concurrently, but also ensure that no other transactions are queued against the same database as long as the transaction is running.

2.8. Requests

Each asynchronous operation on a database is done using a request. Every request represents one operation.

A request has a done flag which is initially unset.

A request has a source object.

A request has a result and an error, neither of which are accessible until the done flag is set.

A request has a transaction which is initially null. This will be set when a request is placed against a transaction using the steps for asynchronously executing a request.

When a request is made, a new request is returned with its done flag unset. If a request completes successfully, the done flag is set, the result is set to the result of the request, and an event with type success is fired at the request.

If an error occurs while performing the operation, the done flag is set, the error is set to the error, and an event with type error is fired at the request.

A request's get the parent algorithm returns the request’s transaction.

Requests are not typically re-used, but there are exceptions. When a cursor is iterated, the success of the iteration is reported on the same request object used to open the cursor. And when an upgrade transaction is necessary, the same open request is used for both the upgradeneeded event and final result of the open operation itself. In both cases, the request’s done flag will be unset then set again, and the result may change.

2.8.1. Open Requests

An open request is a special type of request used when opening a connection or deleting a database. In addition to success and error events, blocked and upgradeneeded may be fired at an open request to indicate progress.

The source of an open request is always null.

The transaction of an open request is null unless an upgradeneeded event has been fired.

An open request's get the parent algorithm returns null.

Open requests are processed in a connection queue. The queue contains all open requests associated with an origin and a name. Requests added to the connection queue processed in order and each request must run to completion before the next request is processed. An open request may be blocked on other connections, requiring those connections to close before the request can complete and allow further requests to be processed.

2.9. Key Range

Records can be retrieved from object stores and indexes using either keys or key ranges. A key range is a continuous interval over some data type used for keys.

A key range has an associated lower bound (null or a key).

A key range has an associated upper bound (null or a key).

A key range has an associated lower open flag. Unless otherwise stated it is unset.

A key range has an associated upper open flag. Unless otherwise stated it is unset.

A key range may have a lower bound equal to its upper bound. A key range must not have a lower bound greater than its upper bound.

A key range containing only key has both lower bound and upper bound equal to key.

A key is in a key range if both of the following conditions are fulfilled:

The lower bound is null, or it is less than key, or it is both equal to key and the lower open flag is unset.
The upper bound is null, or it is greater than key, or it is both equal to key and the upper open flag is unset.

An unbounded key range is a key range that has both lower bound and upper bound equal to null. All keys are in an unbounded key range.

The steps to convert a value to a key range with value and optional null disallowed flag are as follows:

If value is a key range, return value.
If value is undefined or is null, then throw a DataError if null disallowed flag is set, or return an unbounded key range otherwise.
Let key be the result of running the steps to convert a value to a key with value. Rethrow any exceptions.
If key is invalid, throw a DataError.
Return a key range containing only key.

2.10. Cursor

A cursor is used to iterate over a range of records in an index or an object store in a specific direction.

A cursor has a transaction, the transaction that was active when the cursor was created.

A cursor has a range of records in either an index or an object store.

A cursor has a source that indicates which index or an object store is associated with the records over which the cursor is iterating.

A cursor has a direction that determines whether it moves in monotonically increasing or decreasing order of the record keys when iterated, and if it skips duplicated values when iterating indexes. The direction of a cursor also determines if the cursor initial position is at the start of its source or at its end. A cursor’s direction is one of the following:

"next": This direction causes the cursor to be opened at the start of the source. When iterated, the cursor should yield all records, including duplicates, in monotonically increasing order of keys.
"nextunique": This direction causes the cursor to be opened at the start of the source. When iterated, the cursor should not yield records with the same key, but otherwise yield all records, in monotonically increasing order of keys. For every key with duplicate values, only the first record is yielded. When the source is an object store or an index with the unique flag set, this direction has exactly the same behavior as "next".
"prev": This direction causes the cursor to be opened at the end of the source. When iterated, the cursor should yield all records, including duplicates, in monotonically decreasing order of keys.
"prevunique": This direction causes the cursor to be opened at the end of the source. When iterated, the cursor should not yield records with the same key, but otherwise yield all records, in monotonically decreasing order of keys. For every key with duplicate values, only the first record is yielded. When the source is an object store or an index with the unique flag set, this direction has exactly the same behavior as "prev".

A cursor has a position within its range. It is possible for the list of records which the cursor is iterating over to change before the full range of the cursor has been iterated. In order to handle this, cursors maintain their position not as an index, but rather as a key of the previously returned record. For a forward iterating cursor, the next time the cursor is asked to iterate to the next record it returns the record with the lowest key greater than the one previously returned. For a backwards iterating cursor, the situation is opposite and it returns the record with the highest key less than the one previously returned.

For cursors iterating indexes the situation is a little bit more complicated since multiple records can have the same key and are therefore also sorted by value. When iterating indexes the cursor also has an object store position, which indicates the value of the previously found record in the index. Both position and the object store position are used when finding the next appropriate record.

A cursor has a key and a value which represent the key and the value of the last iterated record.

A cursor has a got value flag. When this flag unset, the cursor is either in the process of loading the next value or it has reached the end of its range. When it is set, it indicates that the cursor is currently holding a value and that it is ready to iterate to the next one.

If the source of a cursor is an object store, the effective object store of the cursor is that object store and the effective key of the cursor is the cursor’s position. If the source of a cursor is an index, the effective object store of the cursor is that index’s referenced object store and the effective key is the cursor’s object store position.

A cursor also has a key only flag, that indicates whether the cursor’s value is exposed via the API. Unless stated otherwise it is unset.

2.11. Key Generators

When a object store is created it can be specified to use a key generator. A key generator keeps an internal current number. The current number is always a positive integer. Whenever the key generator is used to generate a new key, the generator’s current number is returned and then incremented to prepare for the next time a new key is needed. Implementations must use the following rules for generating numbers when a key generator is used.

Every object store that uses key generators use a separate generator. I.e. interacting with one object store never affects the key generator of any other object store.
The current number of a key generator is always set to 1 when the object store for that key generator is first created.
When a key generator is used to generate a new key for a object store, the key generator’s current number is used as the new key value and then the key generator’s current number is increased by 1.
When a record is stored and a key is specified in the call to store the record, if type of the key is number and the value is greater than or equal to the key generator’s current number, then the key generator’s current number is set to the smallest integer number greater than the explicit key. A key can be specified both for object stores which use in-line keys, by setting the property on the stored value which the object store’s key path points to, and for object stores which use out-of-line keys, by passing a key argument to the call to store the record.

Only specified keys of type number may affect the current number of the key generator. Keys of type date, array (regardless of the other keys they contain), binary, or string (regardless of whether they could be parsed as numbers) have no effect on the current number of the key generator. Keys of type number with value less than 1 do not affect the current number since they are always lower than the current number.
Modifying a key generator’s current number is considered part of a database operation. This means that if the operation fails and the operation is reverted, the current number is reverted to the value it had before the operation started. This applies both to modifications that happen due to the current number getting increased by 1 when the key generator is used, and to modifications that happen due to a record being stored with a key value specified in the call to store the record.
Likewise, if a transaction is aborted, the current number of the key generator for each object store in the transaction’s scope is reverted to the value it had before the transaction was started.
When the current number of a key generator reaches above the value 2⁵³ (9007199254740992) any attempts to use the key generator to generate a new key will result in a ConstraintError. It is still possible to insert records into the object store by specifying an explicit key, however the only way to use a key generator again for the object store is to delete the object store and create a new one.

As long as key generators are used in a normal fashion this will not be a problem. If you generate a new key 1000 times per second day and night, you won’t run into this limit for over 285000 years.
The current number for a key generator never decreases, other than as a result of database operations being reverted. Deleting a record from an object store never affects the object store’s key generator. Even clearing all records from an object store, for example using the clear() method, does not affect the current number of the object store’s key generator.

A practical result of this is that the first key generated for an object store is always 1 (unless a higher numeric key is inserted first) and the key generated for an object store is always a positive integer higher than the highest numeric key in the store. The same key is never generated twice for the same object store unless a transaction is rolled back.

Each object store gets its own key generator:

store1 = db.createObjectStore("store1", { autoIncrement: true });
store1.put("a"); // Will get key 1
store2 = db.createObjectStore("store2", { autoIncrement: true });
store2.put("a"); // Will get key 1
store1.put("b"); // Will get key 2
store2.put("b"); // Will get key 2

If an insertion fails due to constraint violations or IO error, the key generator is not updated.

transaction.onerror = function(e) { e.preventDefault() };
store = db.createObjectStore("store1", { autoIncrement: true });
index = store.createIndex("index1", "ix", { unique: true });
store.put({ ix: "a"}); // Will get key 1
store.put({ ix: "a"}); // Will fail
store.put({ ix: "b"}); // Will get key 2

Removing items from an objectStore never affects the key generator. Including when clear() is called.

store = db.createObjectStore("store1", { autoIncrement: true });
store.put("a"); // Will get key 1
store.delete(1);
store.put("b"); // Will get key 2
store.clear();
store.put("c"); // Will get key 3
store.delete(IDBKeyRange.lowerBound(0));
store.put("d"); // Will get key 4

Inserting an item with an explicit key affects the key generator if, and only if, the key is numeric and higher than the last generated key.

store = db.createObjectStore("store1", { autoIncrement: true });
store.put("a"); // Will get key 1
store.put("b", 3); // Will use key 3
store.put("c"); // Will get key 4
store.put("d", -10); // Will use key -10
store.put("e"); // Will get key 5
store.put("f", 6.00001); // Will use key 6.0001
store.put("g"); // Will get key 7
store.put("f", 8.9999); // Will use key 8.9999
store.put("g"); // Will get key 9
store.put("h", "foo"); // Will use key "foo"
store.put("i"); // Will get key 10
store.put("j", [1000]); // Will use key [1000]
store.put("k"); // Will get key 11
// All of these would behave the same if the objectStore used a
// keyPath and the explicit key was passed inline in the object

Aborting a transaction rolls back any increases to the key generator which happened during the transaction. This is to make all rollbacks consistent since rollbacks that happen due to crash never has a chance to commit the increased key generator value.

db.createObjectStore("store", { autoIncrement: true });
trans1 = db.transaction(["store"], "readwrite");
store_t1 = trans1.objectStore("store");
store_t1.put("a"); // Will get key 1
store_t1.put("b"); // Will get key 2
trans1.abort();
trans2 = db.transaction(["store"], "readwrite");
store_t2 = trans2.objectStore("store");
store_t2.put("c"); // Will get key 1
store_t2.put("d"); // Will get key 2

The following examples illustrate the different behaviors when trying to use in-line keys and key generators to save an object to an object store.

If the following conditions are true:

The object store has a key generator.
There is no in-line value for the key path property.

Then the value provided by the key generator is used to populate the key value. In the example below the key path for the object store is "foo.bar". The actual object has no value for the bar property, { foo: {} }. When the object is saved in the object store the bar property is assigned a value of 1 because that is the next key generated by the key generator.

var store = db.createObjectStore("store", { keyPath: "foo.bar",
                                            autoIncrement: true });
store.put({ foo: {} }).onsuccess = function(e) {
  var key = e.target.result;
  console.assert(key === 1);
};

If the following conditions are true:

The object store has a key generator.
There is a value for the key path property.

Then the value associated with the key path property is used. The auto-generated key is not used. In the example below the key path for the object store is "foo.bar". The actual object has a value of 10 for the bar property, { foo: { bar: 10} }. When the object is saved in the object store the bar property keeps its value of 10, because that is the key value.

var store = db.createObjectStore("store", { keyPath: "foo.bar",
                                            autoIncrement: true });
store.put({ foo: { bar: 10 } }).onsuccess = function(e) {
  var key = e.target.result;
  console.assert(key === 10);
};

The following example illustrates the scenario when the specified in-line key is defined through a key path but there is no property matching it. The value provided by the key generator is then used to populate the key value and the system is responsible for creating as many properties as it requires to suffice the property dependencies on the hierarchy chain. In the example below the key path for the object store is "foo.bar.baz". The actual object has no value for the foo property, { zip: {} }. When the object is saved in the object store the foo, bar, and baz properties are created each as a child of the other until a value for foo.bar.baz can be assigned. The value for foo.bar.baz is the next key generated by the object store.

var store = db.createObjectStore("store", { keyPath: "foo.bar.baz",
                                            autoIncrement: true });
store.put({ zip: {} }).onsuccess = function(e) {
  var key = e.target.result;
  console.assert(key === 1);
  store.get(key).onsuccess = function(e) {
    var value = e.target.result;
    // value will be: { zip: {}, foo: { bar: { baz: 1 } } }
    console.assert(value.foo.bar.baz === 1);
  };
};

Attempting to store a property on a primitive value will fail and throw an error. In the first example below the key path for the object store is "foo". The actual object is a primitive with the value, 4. Trying to define a property on that primitive value fails. The same is true for arrays. Properties are not allowed on an array. In the second example below, the actual object is an array, [10]. Trying to define a property on the array fails.

var store = db.createObjectStore("store", { keyPath: "foo", autoIncrement: true });

// The key generation will attempt to create and store the key path
// property on this primitive.
store.put(4); // will throw DataError

// The key generation will attempt to create and store the key path
// property on this array.
store.put([10]); // will throw DataError

3. Exceptions

Each of the exceptions defined in this document is a DOMException with a specific type. The exception types and properties such as code value are defined in [WEBIDL].

Type	Description
`AbortError`	A request was aborted.
`ConstraintError`	A mutation operation in the transaction failed because a constraint was not satisfied.
`DataCloneError`	The data being stored could not be cloned by the internal structured cloning algorithm.
`DataError`	Data provided to an operation does not meet requirements.
`InvalidAccessError`	An invalid operation was performed on an object.
`InvalidStateError`	An operation was called on an object on which it is not allowed or at a time when it is not allowed, or if a request is made on a source object that has been deleted or removed.
`NotFoundError`	The operation failed because the requested database object could not be found.
`QuotaExceededError`	The operation failed because there was not enough remaining storage space, or the storage quota was reached and the user declined to give more space to the database.
`SyntaxError`	The keyPath argument contains an invalid key path.
`ReadOnlyError`	The mutating operation was attempted in a read-only transaction.
`TransactionInactiveError`	A request was placed against a transaction which is currently not active, or which is finished.
`UnknownError`	The operation failed for reasons unrelated to the database itself and not covered by any other errors.
`VersionError`	An attempt was made to open a database using a lower version than the existing version.

4. API

The API methods return without blocking the calling thread. All asynchronous operations immediately return an IDBRequest instance. This object does not initially contain any information about the result of the operation. Once information becomes available, an event is fired on the request and the information becomes available through the properties of the IDBRequest instance.

The task source for these tasks is the database access task source.

4.1. The `IDBRequest` interface

The IDBRequest interface provides the means to access results of asynchronous requests to databases and database objects using event handler IDL attributes [HTML].

Every method for making asynchronous requests returns an IDBRequest object that communicates back to the requesting application through events. This design means that any number of requests can be active on any database at a time.

In the following example, we open a database asynchronously. Various event handlers are registered for responding to various situations.

var request = indexedDB.open('AddressBook', 15);
request.onsuccess = function(evt) {...};
request.onerror = function(evt) {...};

[Exposed=(Window,Worker)]
interface IDBRequest : EventTarget {
  readonly attribute any                                        result;
  readonly attribute DOMException?                              error;
  readonly attribute (IDBObjectStore or IDBIndex or IDBCursor)? source;
  readonly attribute IDBTransaction?                            transaction;
  readonly attribute IDBRequestReadyState                       readyState;

  // Event handlers:
  attribute EventHandler onsuccess;
  attribute EventHandler onerror;
};

enum IDBRequestReadyState {
  "pending",
  "done"
};

The result attribute’s getter must throw an InvalidStateError if the done flag is unset. Otherwise, the attribute’s getter must return the result of the request, or undefined if the request.resulted in an error.

The error attribute’s getter must throw an InvalidStateError if the done flag is unset. Otherwise, the attribute’s getter must return the error of the request, or null if no error occurred.

The source attribute’s getter must return the source of the request, or null if no source is set.

The transaction attribute’s getter must return the transaction of the request. This property can be null for certain requests, such as for request returned from open().

The readyState attribute’s getter must return "pending" if the done flag is unset, and "done" otherwise.

The onsuccess attribute is the event handler for the success event.

The onerror attribute is the event handler for the error event.

Methods on IDBDatabase that return a open request use an extended interface to allow listening to the blocked event and upgradeneeded event.

[Exposed=(Window,Worker)]
interface IDBOpenDBRequest : IDBRequest {
  // Event handlers:
  attribute EventHandler onblocked;
  attribute EventHandler onupgradeneeded;
};

The onblocked attribute is the event handler for the blocked event.

The onupgradeneeded attribute is the event handler for the upgradeneeded event.

4.2. Event interfaces

This specification fires events with the following custom interfaces:

[Exposed=(Window,Worker),
 Constructor(DOMString type, optional IDBVersionChangeEventInit eventInitDict)]
interface IDBVersionChangeEvent : Event {
  readonly attribute unsigned long long  oldVersion;
  readonly attribute unsigned long long? newVersion;
};

dictionary IDBVersionChangeEventInit : EventInit {
  unsigned long long  oldVersion = 0;
  unsigned long long? newVersion = null;
};

The oldVersion attribute getter returns the previous version of the database.

The newVersion attribute getter returns the new version of the database, or null if the database is being deleted. See the steps for running an upgrade transaction.

Events are constructed as defined in Constructing events, in [DOM].

To fire a version change event named e at target given oldVersion and newVersion, dispatch an event at target. The event must use the IDBVersionChangeEvent interface with its type set to e, its oldVersion attribute set to oldVersion, and its newVersion attribute set to newVersion. This event must not bubble or be cancelable.

4.3. The `IDBFactory` interface

Database objects are accessed through methods on the IDBFactory interface. A single object implementing this interface is present in the global scope of environments that support Indexed DB operations.

[NoInterfaceObject]
interface IDBEnvironment {
  readonly attribute IDBFactory indexedDB;
};
Window implements IDBEnvironment;
WorkerGlobalScope implements IDBEnvironment;

The indexedDB attribute provides applications a mechanism for accessing capabilities of indexed databases.

[Exposed=(Window,Worker)]
interface IDBFactory {
  IDBOpenDBRequest open(DOMString name,
                        [EnforceRange] optional unsigned long long version);
  IDBOpenDBRequest deleteDatabase(DOMString name);

  short cmp(any first, any second);
};

The open(name, version) method, when invoked, must run these steps:

If version is 0 (zero), throw a TypeError.
Let request be a new open request.
Run the following substeps in parallel:
1. Let result be the result of running the steps for opening a database, with the origin of the IDBEnvironment used to access this IDBFactory, name, version if given and undefined otherwise, and request.
  
  If version is not given and a database with that name already exists, a connection will be opened without changing the version. If version is not given and no database with that name exists, a new database will be created with version equal to 1.
2. Queue a task to run these substeps:
  1. If result is an error, set the error of request to result and dispatch an event at request. The event must use the Event interface and set the type attribute to "error". The event does bubble but is not cancelable.
  2. Otherwise, set the result of request to result and dispatch an event at request. The event must use the Event interface and set the type attribute to "success". The event does not bubble and is not cancelable. If the steps above resulted in an upgrade transaction being run, then firing the "success" event must be done after the upgrade transaction completes.
    
    The last requirement is to ensure that in case another version upgrade is about to happen, the success event is fired on the connection first so that the script gets a chance to register a listener for the versionchange event.
    
    The firing of "success" or "error" events do not follow the normal steps to fire a success event or fire an error event as there is no active transaction at the time when they fire.
Return a new IDBOpenDBRequest object for request.

The deleteDatabase(name) method, when invoked, must run these steps:

Let request be a new open request.
Run the following substeps in parallel:
1. Let result be the result of running the steps for deleting a database, with the origin of the IDBEnvironment used to access this IDBFactory, name, and request.
2. Queue a task to run these substeps:
  1. If result is an error set the error of request to result and dispatch an event at request. The event must use the Event interface and set the type attribute to "error". The event does bubble but is not cancelable.
  2. Otherwise, set the result of request to undefined and fire a version change event named success at request with result and null.
    
    The firing of "success" or "error" events do not follow the normal steps to fire a success event or fire an error event as there is no active transaction at the time when they fire.
Return a new IDBOpenDBRequest object for request.

The cmp(first, second) method, when invoked, must run these steps:

Let a be the result of running the steps to convert a value to a key with first. Rethrow any exceptions.
If a is invalid, throw a DataError.
Let b be the result of running the steps to convert a value to a key with second. Rethrow any exceptions.
If b is invalid, throw a DataError.
Return the results of running the steps to compare two keys with a and b.

4.4. The `IDBDatabase` interface

The IDBDatabase interface represents a connection to a database.

An IDBDatabase object must not be garbage collected if its associated connection's close pending flag is unset and it has one or more event listeners registers whose type is one of abort, error, or versionchange. If an IDBDatabase object is garbage collected, the associated connection must be closed.

[Exposed=(Window,Worker)]
interface IDBDatabase : EventTarget {
  readonly attribute DOMString          name;
  readonly attribute unsigned long long version;
  readonly attribute DOMStringList      objectStoreNames;

  IDBTransaction transaction((DOMString or sequence<DOMString>) storeNames,
                             optional IDBTransactionMode mode = "readonly");
  void           close();

  IDBObjectStore createObjectStore(DOMString name,
                                   optional IDBObjectStoreParameters options);
  void           deleteObjectStore(DOMString name);

  // Event handlers:
  attribute EventHandler onabort;
  attribute EventHandler onclose;
  attribute EventHandler onerror;
  attribute EventHandler onversionchange;
};

dictionary IDBObjectStoreParameters {
  (DOMString or sequence<DOMString>)? keyPath = null;
  boolean                             autoIncrement = false;
};

The name attribute’s getter must return the name of the connected database. The attribute must return this name even if the close pending flag is set on the connection. In other words, the value of this attribute stays constant for the lifetime of the IDBDatabase instance.

The version attribute’s getter must return this connection's version.

The objectStoreNames attribute’s getter must return a sorted list of the names of the object stores in this connection's object store set.

The createObjectStore(name, options) method, when invoked, must run these steps:

Let database be the database associated with this connection.
Let transaction be the currently running upgrade transaction associated with database, or throw an InvalidStateError if none.
If transaction is not active, throw a TransactionInactiveError.
If an object store named name already exists in database throw a ConstraintError.
Let keyPath be options’s keyPath member if it is not undefined or null, or null otherwise.
If keyPath is not null and is not a valid key path, throw a SyntaxError.
Let autoIncrement be set if options’s autoIncrement member is true, or unset otherwise.
If autoIncrement is set and keyPath is an empty string or any sequence (empty or otherwise), throw an InvalidAccessError.
Let store be a new object store in database. Set the created object store's name to name. If autoIncrement is set, then the created object store uses a key generator. If keyPath is not null, set the created object store's key path to keyPath.
Return a new object store handle associated with store and transaction.

This method creates and returns a new object store with the given name in the connected database. Note that this method must only be called from within an upgrade transaction.

This method synchronously modifies the objectStoreNames property on the IDBDatabase instance on which it was called.

In some implementations it is possible for the implementation to run into problems after queuing a task to create the object store after the createObjectStore() method has returned. For example in implementations where metadata about the newly created object store is inserted into the database asynchronously, or where the implementation might need to ask the user for permission for quota reasons. Such implementations must still create and return an IDBObjectStore object, and once the implementation determines that creating the object store has failed, it must abort the transaction using the steps for aborting a transaction using the appropriate error. For example if creating the object store failed due to quota reasons, QuotaExceededError must be used as error.

The deleteObjectStore(name) method, when invoked, must run these steps:

Let database be the database associated with this connection.
Let transaction be the currently running upgrade transaction associated with database, or throw an InvalidStateError if none.
If transaction is not active, throw a TransactionInactiveError.
Let store be the object store named name in database, or throw a NotFoundError if none.
Remove store from this connection's object store set.
Destroy store.

This method destroys the object store with the given name in the connected database. Note that this method must only be called from within an upgrade transaction.

This method synchronously modifies the objectStoreNames property on the IDBDatabase instance on which it was called.

The transaction(storeNames, mode) method, when invoked, must run these steps:

If mode parameter is not "readonly" or "readwrite", throw a TypeError.
If this method is called on IDBDatabase object for which an upgrade transaction is still running, throw an InvalidStateError.
If this method is called on an IDBDatabase instance where the close pending flag is set, throw an InvalidStateError.
Let scope be the set of unique strings in storeNames if it is a sequence, or a set containing one string equal to storeNames otherwise.
If any string in scope is not the name of an object store in the connected database, throw a NotFoundError.
If scope is empty, throw an InvalidAccessError.
Let transaction be a newly created transaction with connection, mode and the set of object stores named in scope.
When control is returned to the event loop, the implementation must unset the active flag.

Specify this more precisely in terms of tasks and microtasks.
Return an IDBTransaction object representing transaction.

The close() method, when invoked, must run these steps:

Run the steps for closing a database connection with this connection.

The onabort attribute is the event handler for the abort event.

The onclose attribute is the event handler for the close event.

🎉 The onclose attribute is new in this edition. 🎉

The onerror attribute is the event handler for the error event.

The onversionchange attribute is the event handler for the versionchange event.

4.5. The `IDBObjectStore` interface

The IDBObjectStore interface represents an object store handle.

[Exposed=(Window,Worker)]
interface IDBObjectStore {
           attribute DOMString      name;
  readonly attribute any            keyPath;
  readonly attribute DOMStringList  indexNames;
  readonly attribute IDBTransaction transaction;
  readonly attribute boolean        autoIncrement;

  IDBRequest put(any value, optional any key);
  IDBRequest add(any value, optional any key);
  IDBRequest delete(any query);
  IDBRequest clear();
  IDBRequest get(any query);
  IDBRequest getKey(any query);
  IDBRequest getAll(optional any query,
                    [EnforceRange] optional unsigned long count);
  IDBRequest getAllKeys(optional any query,
                        [EnforceRange] optional unsigned long count);
  IDBRequest count(optional any query);

  IDBRequest openCursor(optional any query,
                        optional IDBCursorDirection direction = "next");
  IDBRequest openKeyCursor(optional any query,
                           optional IDBCursorDirection direction = "next");

  IDBIndex   index(DOMString name);

  IDBIndex   createIndex(DOMString name,
                         (DOMString or sequence<DOMString>) keyPath,
                         optional IDBIndexParameters options);
  void       deleteIndex(DOMString indexName);
};

dictionary IDBIndexParameters {
  boolean unique = false;
  boolean multiEntry = false;
};

The name attribute’s getter must return this object store handle's name.

The name attribute’s setter must run these steps:

Let name be the given value.
Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not an upgrade transaction, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If store’s name is equal to name, terminate these steps.
If an object store named name already exists in store’s database, throw a ConstraintError.
Set store’s name to name.
Set this object store handle's name to name.

🎉 The name attribute’s setter is new in this edition. 🎉

The keyPath attribute’s getter must return this object store handle's object store's key path, or null if none.

The conversion is done following the normal [WEBIDL] binding logic for DOMString and sequence<DOMString> values, as appropriate.

The returned value is not the same instance that was used when the object store was created. However, if this attribute returns an object (specifically an Array), it returns the same object instance every time it is inspected. Changing the properties of the object has no effect on the object store.

The indexNames attribute’s getter must return a sorted list of the names of indexes in this object store handle's index set.

The transaction attribute’s getter must return this object store handle's transaction,

The autoIncrement attribute’s getter must return true if this object store handle's object store has a key generator, and false otherwise.

The put(value, key) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If transaction is a read-only transaction, throw a ReadOnlyError.
If store uses in-line keys and key was given, throw a DataError.
If store uses out-of-line keys and has no key generator and key was not given, throw a DataError.
If key was given, run these substeps:
1. Let r be the result of running the steps to convert a value to a key with key. Rethrow any exceptions.
2. If r is invalid, throw a DataError.
3. Let key be r.
Let clone be structured clone of value. Rethrow any exceptions.
If store uses in-line keys, run these substeps:
1. Let kpk be the result of running the steps to extract a key from a value using a key path with clone and store’s key path. Rethrow any exceptions.
2. If kpk is invalid, throw a DataError.
3. If kpk is not failure, let key be kpk.
4. Otherwise, if store does not have a key generator, throw a DataError.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for storing a record into an object store as operation, using store, the clone as value, key, and with the no-overwrite flag unset.

The add(value, key) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If transaction is a read-only transaction, throw a ReadOnlyError.
If store uses in-line keys and key was given, throw a DataError.
If store uses out-of-line keys and has no key generator and key was not given, throw a DataError.
If key was given, run these substeps:
1. Let r be the result of running the steps to convert a value to a key with key. Rethrow any exceptions.
2. If r is invalid, throw a DataError.
3. Let key be r.
Let clone be structured clone of value. Rethrow any exceptions.
If store uses in-line keys, run these substeps:
1. Let kpk be the result of running the steps to extract a key from a value using a key path with clone and store’s key path. Rethrow any exceptions.
2. If kpk is invalid, throw a DataError.
3. If kpk is not failure, let key be kpk.
4. Otherwise, if store does not have a key generator, throw a DataError.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for storing a record into an object store as operation, using store, clone as value, key, and with the no-overwrite flag set.

The delete(query) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If transaction is a read-only transaction, throw a ReadOnlyError.
Let range be the result of running the steps to convert a value to a key range with query and null disallowed flag set. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for deleting records from an object store as operation, using store and range.

The query parameter may be a key or an IDBKeyRange identifying the records keys to be deleted.

The clear() method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If transaction is a read-only transaction, throw a ReadOnlyError.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for clearing an object store as operation, using store.

The get(query) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query and null disallowed flag set. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for retrieving a value from an object store as operation, using store and range.

The query parameter may be a key or an IDBKeyRange identifying the record to be retrieved. If a range is specified, the method retrieves the first existing value in that range.

This method produces the same result if a record with the given key doesn’t exist as when a record exists, but has undefined as value. If you need to tell the two situations apart, you can use openCursor() with the same key. This will return a cursor with undefined as value if a record exists, or no cursor if no such record exists.

The getKey(query) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query and null disallowed flag set. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for retrieving a key from an object store as operation, using store and range.

The query parameter may be a key or an IDBKeyRange identifying the record key to be retrieved. If a range is specified, the method retrieves the first existing key in that range.

🚧 The getKey() method on IDBObjectStore is new in this edition, but not yet shipping in any browsers. 🚧

The getAll(query, count) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for retrieving multiple values from an object store as operation, using store, range, and count if given.

The query parameter may be a key or an IDBKeyRange identifying the records to be retrieved. If null or not given, an unbounded key range is used. If count is specified and there are more than count records in range, only the first count will be retrieved.

🎉 The getAll() method is new in this edition. 🎉

The getAllKeys(query, count) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for retrieving multiple keys from an object store as operation, using store, range, and count if given.

The query parameter may be a key or an IDBKeyRange identifying the records keys to be retrieved. If null or not given, an unbounded key range is used. If count is specified and there are more than count keys in range, only the first count will be retrieved.

🎉 The getAllKeys() method is new in this edition. 🎉

The count(query) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps to count the records in a range as operation, with source and range.

The query parameter may be a key or an IDBKeyRange identifying the records keys to be counted. If null or not given, an unbounded key range is used.

The openCursor(query, direction) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Let cursor be a new cursor with transaction set to transaction, an undefined position, direction set to direction, got value flag unset, and undefined key and value. The source of cursor is store. The range of cursor is range.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for iterating a cursor with cursor as operation.

The query parameter may be a key or an IDBKeyRange to use as the cursor's range. If null or not given, an unbounded key range is used.

The openKeyCursor(query, direction) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Let cursor be a new cursor with transaction set to transaction, an undefined position, direction set to direction, got value flag unset, and undefined key and value. The source of cursor is store. The range of cursor is range. The key only flag of cursor is set.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this object store handle as source and the steps for iterating a cursor with cursor as operation.

The query parameter may be a key or an IDBKeyRange to use as the cursor's range. If null or not given, an unbounded key range is used.

🎉 The openKeyCursor() method is new in this edition. 🎉

The createIndex(name, keyPath, options) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If transaction is not an upgrade transaction, throw an InvalidStateError.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If an index named name already exists in store, throw a ConstraintError.
If keyPath is not a valid key path, throw a SyntaxError.
Let unique be set if options’s unique member is true, and unset otherwise.
Let multiEntry be set if options’s multiEntry member is true, and unset otherwise.
If keyPath is a sequence and multiEntry is set, throw an InvalidAccessError.
Let index be a new index in store. Set index’s name to name and key path to keyPath. If unique is set, set index’s unique flag. If multiEntry is set, set index’s multiEntry flag.
Add index to this object store handle's index set.
Return a new index handle associated with index and this object store handle.

This method creates and returns a new index with the given name in the object store. Note that this method must only be called from within an upgrade transaction.

The index that is requested to be created can contain constraints on the data allowed in the index’s referenced object store, such as requiring uniqueness of the values referenced by the index’s keyPath. If the referenced object store already contains data which violates these constraints, this must not cause the implementation of createIndex() to throw an exception or affect what it returns. The implementation must still create and return an IDBIndex object, and the implementation must queue a task to abort the upgrade transaction which was used for the createIndex() call.

This method synchronously modifies the indexNames property on the IDBObjectStore instance on which it was called. Although this method does not return an IDBRequest object, the index creation itself is processed as an asynchronous request within the upgrade transaction.

In some implementations it is possible for the implementation to asynchronously run into problems creating the index after the createIndex method has returned. For example in implementations where metadata about the newly created index is queued up to be inserted into the database asynchronously, or where the implementation might need to ask the user for permission for quota reasons. Such implementations must still create and return an IDBIndex object, and once the implementation determines that creating the index has failed, it must abort the transaction using the steps for aborting a transaction using an appropriate error as error. For example if creating the index failed due to quota reasons, QuotaExceededError must be used as error and if the index can’t be created due to unique flag constraints, ConstraintError must be used as error.

The asynchronous creation of indexes is observable in the following example:

var request1 = objectStore.put({name: "betty"}, 1);
var request2 = objectStore.put({name: "betty"}, 2);
var index = objectStore.createIndex("by_name", "name", {unique: true});

At the point where createIndex() called, neither of the requests have executed. When the second request executes, a duplicate name is created. Since the index creation is considered an asynchronous request, the index’s uniqueness constraint does not cause the second request to fail. Instead, the transaction will be aborted when the index is created and the constraint fails.

The index(name) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If store has been deleted, throw an InvalidStateError.
If transaction has finished, throw an InvalidStateError.
Let index be the index named name in this object store handle's index set if one exists, or throw a NotFoundError otherwise.
Return an index handle associated with index and this object store handle.

Each call to this method on the same IDBObjectStore instance with the same name returns the same IDBIndex instance.

The returned IDBIndex instance is specific to this IDBObjectStore instance. If this method is called on a different IDBObjectStore instance with the same name, a different IDBIndex instance is returned.

The deleteIndex(name) method, when invoked, must run these steps:

Let transaction be this object store handle's transaction.
Let store be this object store handle's object store.
If transaction is not an upgrade transaction, throw an InvalidStateError.
If store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let index be the index named name in store if one exists, or throw a NotFoundError otherwise.
Remove index from this object store handle's index set.
Destroy index.

This method destroys the index with the given name in the object store. Note that this method must only be called from within an upgrade transaction.

This method synchronously modifies the indexNames property on the IDBObjectStore instance on which it was called. Although this method does not return an IDBRequest object, the index destruction itself is processed as an asynchronous request within the upgrade transaction.

4.6. The `IDBIndex` interface

The IDBIndex interface represents an index handle.

[Exposed=(Window,Worker)]
interface IDBIndex {
           attribute DOMString      name;
  readonly attribute IDBObjectStore objectStore;
  readonly attribute any            keyPath;
  readonly attribute boolean        multiEntry;
  readonly attribute boolean        unique;

  IDBRequest get(any query);
  IDBRequest getKey(any query);
  IDBRequest getAll(optional any query,
                    [EnforceRange] optional unsigned long count);
  IDBRequest getAllKeys(optional any query,
                        [EnforceRange] optional unsigned long count);
  IDBRequest count(optional any query);

  IDBRequest openCursor(optional any query,
                        optional IDBCursorDirection direction = "next");
  IDBRequest openKeyCursor(optional any query,
                           optional IDBCursorDirection direction = "next");
};

The name attribute’s getter must return this index handle's name.

The name attribute’s setter must run these steps:

Let name be the given value.
Let transaction be this index handle's transaction.
Let index be this index handle's index.
If transaction is not an upgrade transaction, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
If index or index’s object store has been deleted, throw an InvalidStateError.
If index’s name is equal to name, terminate these steps.
If an index named name already exists in index’s object store, throw a ConstraintError.
Set index’s name to name.
Set this index handle's name to name.

🎉 The name attribute’s setter is new in this edition. 🎉

The objectStore attribute’s getter must return this index handle's object store handle.

The keyPath attribute’s getter must return this index handle's index's key path.

The conversion is done following the normal [WEBIDL] binding logic for DOMString and sequence<DOMString> values, as appropriate.

The returned value is not the same instance that was used when the index was created. However, if this attribute returns an object (specifically an Array), it returns the same object instance every time it is inspected. Changing the properties of the object has no effect on the index.

The multiEntry attribute’s getter must return true if this index handle's index's multiEntry flag is set, and false otherwise.

The unique attribute’s getter must return true if this index handle's index's unique flag is set, and false otherwise.

The get(query) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query and null disallowed flag set. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps for retrieving a referenced value from an index as operation, using index and range.

The query parameter may be a key or an IDBKeyRange identifying the record to be retrieved. If a range is specified, the method retrieves the first existing record in that range.

The getKey(query) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query and null disallowed flag set. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps for retrieving a value from an index as operation, using index and range.

The query parameter may be a key or an IDBKeyRange identifying the record key to be retrieved. If a range is specified, the method retrieves the first existing key in that range.

The getAll(query, count) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps for retrieving multiple referenced values from an index as operation, using index, range, and count if given.

🎉 The getAll() method is new in this edition. 🎉

The getAllKeys(query, count) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps for retrieving multiple values from an index as operation, using index, range, and count if given.

🎉 The getAllKeys() method is new in this edition. 🎉

The count(query) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps to count the records in a range as operation, with index as source and range.

The query parameter may be a key or an IDBKeyRange identifying the records keys to be counted. If null or not given, an unbounded key range is used.

The openCursor(query, direction) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Let cursor be a new cursor with transaction set to transaction, an undefined position, direction set to direction, got value flag unset, and undefined key and value. The source of cursor is index. The range of cursor is range.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps for iterating a cursor with cursor as operation.

The query parameter may be a key or an IDBKeyRange to use as the cursor's range. If null or not given, an unbounded key range is used.

The openKeyCursor(query, direction) method, when invoked, must run these steps:

Let transaction be this index handle's transaction.
Let index be this index handle's index.
If index or index’s object store has been deleted, throw an InvalidStateError.
If transaction is not active, throw a TransactionInactiveError.
Let range be the result of running the steps to convert a value to a key range with query. Rethrow any exceptions.
Let cursor be a new cursor with transaction set to transaction, an undefined position, direction set to direction, got value flag unset, and undefined key and value. The source of cursor is index. The range of cursor is range. The key only flag of cursor is set.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this index handle as source and the steps for iterating a cursor with cursor as operation.

The query parameter may be a key or an IDBKeyRange to use as the cursor's range. If null or not given, an unbounded key range is used.

4.7. The `IDBKeyRange` interface

The IDBKeyRange interface represents a key range.

[Exposed=(Window,Worker)]
interface IDBKeyRange {
  readonly attribute any     lower;
  readonly attribute any     upper;
  readonly attribute boolean lowerOpen;
  readonly attribute boolean upperOpen;

  // Static construction methods:
  static IDBKeyRange only(any value);
  static IDBKeyRange lowerBound(any lower, optional boolean open = false);
  static IDBKeyRange upperBound(any upper, optional boolean open = false);
  static IDBKeyRange bound(any lower,
                           any upper,
                           optional boolean lowerOpen = false,
                           optional boolean upperOpen = false);

  boolean includes(any key);
};

The lower attribute’s getter must return result of running the steps to convert a key to a value with the lower bound if it is not null, or undefined otherwise.

The upper attribute’s getter must return the result of running the steps to convert a key to a value with the upper bound if it is not null, or undefined otherwise.

The lowerOpen attribute’s getter must return true if the lower open flag is set, and false otherwise.

The upperOpen attribute’s getter must return true if the upper open flag is set, and false otherwise.

The only(value) method, when invoked, must run these steps:

Let key be the result of running the steps to convert a value to a key with value. Rethrow any exceptions.
If key is invalid, throw a DataError.
Create and return a new key range containing only key.

The lowerBound(lower, lowerOpen) method, when invoked, must run these steps:

Let lowerKey be the result of running the steps to convert a value to a key with lower. Rethrow any exceptions.
If lowerKey is invalid, throw a DataError.
Create and return a new key range with lower bound set to lowerKey, lower open flag set if lowerOpen is true, upper bound set to null and upper open flag set.

The upperBound(upper, upperOpen) method, when invoked, must run these steps:

Let upperKey be the result of running the steps to convert a value to a key with upper. Rethrow any exceptions.
If upperKey is invalid, throw a DataError.
Create and return a new key range with lower bound set to null, lower open flag set, upper bound set if upperKey, and upper open flag set to upperOpen.

The bound(lower, upper, lowerOpen, upperOpen) method, when invoked, must run these steps:

Let lowerKey be the result of running the steps to convert a value to a key with lower. Rethrow any exceptions.
If lowerKey is invalid, throw a DataError.
Let upperKey be the result of running the steps to convert a value to a key with upper. Rethrow any exceptions.
If upperKey is invalid, throw a DataError.
If lowerKey is greater than upperKey, throw a DataError.
Create and return a new key range with lower bound set to lowerKey, lower open flag set if lowerOpen is true, upper bound set to upperKey and upper open flag set if upperOpen is true.

The includes(key) method, when invoked, must run these steps:

Let k be the result of running the steps to convert a value to a key with key. Rethrow any exceptions.
If k is invalid, throw a DataError.
Return true if k is in this range, and false otherwise.

🎉 The includes() method is new in this edition. 🎉

4.8. The `IDBCursor` interface

Cursor objects implement the IDBCursor interface. There is only ever one IDBCursor instance representing a given cursor. There is no limit on how many cursors can be used at the same time.

[Exposed=(Window,Worker)]
interface IDBCursor {
  readonly attribute (IDBObjectStore or IDBIndex) source;
  readonly attribute IDBCursorDirection           direction;
  readonly attribute any                          key;
  readonly attribute any                          primaryKey;

  void advance([EnforceRange] unsigned long count);
  void continue(optional any key);
  void continuePrimaryKey(any key, any primaryKey);

  IDBRequest update(any value);
  IDBRequest delete();
};

enum IDBCursorDirection {
  "next",
  "nextunique",
  "prev",
  "prevunique"
};

The source attribute’s getter must return the source of this cursor. This attribute never returns null or throws an exception, even if the cursor is currently being iterated, has iterated past its end, or its transaction is not active.

The direction attribute’s getter must return the direction of the cursor.

The key attribute’s getter must return the result of running the steps to convert a key to a value with the cursor’s current key. Note that if this property returns an object (e.g. a Date or Array), it returns the same object instance every time it is inspected, until the cursor’s key is changed. This means that if the object is modified, those modifications will be seen by anyone inspecting the value of the cursor. However modifying such an object does not modify the contents of the database.

The primaryKey attribute’s getter must return the result of running the steps to convert a key to a value with the cursor’s current effective key. Note that if this property returns an object (e.g. a Date or Array), it returns the same object instance every time it is inspected, until the cursor’s effective key is changed. This means that if the object is modified, those modifications will be seen by anyone inspecting the value of the cursor. However modifying such an object does not modify the contents of the database.

The update(value) method, when invoked, must run these steps:

Let transaction be this cursor's transaction.
If transaction is not active, throw a TransactionInactiveError.
If transaction is a read-only transaction, throw a ReadOnlyError.
If the cursor’s source or effective object store has been deleted, throw an InvalidStateError.
If this cursor’s got value flag is unset, indicating that the cursor is being iterated or has iterated past its end, throw an InvalidStateError.
If this cursor’s key only flag is set, throw an InvalidStateError.
Let clone be structured clone of value. Rethrow any exceptions.
If the effective object store of this cursor uses in-line keys, run these substeps:
1. Let kpk be the result of running the steps to extract a key from a value using a key path with clone and the key path of the effective object store. Rethrow any exceptions.
2. If kpk is failure, invalid, or not equal to the cursor’s effective key, throw a DataError.
Run steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this cursor as source and the steps for storing a record into an object store as operation, using this cursor’s effective object store as store, the clone as value, this cursor’s effective key as key, and with the no-overwrite flag unset.

The advance(count) method, when invoked, must run these steps:

If count is 0 (zero), throw a TypeError.
Let transaction be this cursor's transaction.
If transaction is not active, throw a TransactionInactiveError.
If the cursor’s source or effective object store has been deleted, throw an InvalidStateError.
If this cursor’s got value flag is unset, indicating that the cursor is being iterated or has iterated past its end, throw an InvalidStateError.
Unset the got value flag on the cursor.
Let request be the request created when this cursor was created.
Unset the done flag on request.
Run the steps for asynchronously executing a request with the cursor’s source as source and the steps for iterating a cursor with this cursor and count, and request.

Calling this method more than once before new cursor data has been loaded - for example, calling advance() twice from the same onsuccess handler - results in an InvalidStateError exception being thrown on the second call because the cursor’s got value flag has been unset.

The continue(key) method, when invoked, must run these steps:

Let transaction be this cursor's transaction.
If transaction is not active, throw a TransactionInactiveError.
If the cursor’s source or effective object store has been deleted, throw an InvalidStateError.
If this cursor’s got value flag is unset, indicating that the cursor is being iterated or has iterated past its end, throw an InvalidStateError.
If key is given, run these substeps:
1. Let r be the result of running the steps to convert a value to a key with key. Rethrow any exceptions.
2. If r is invalid, throw a DataError.
3. Let key be r.
4. If key is less than or equal to this cursor’s position and this cursor’s direction is "next" or "nextunique", throw a DataError.
5. If key is greater than or equal to this cursor’s position and this cursor’s direction is "prev" or "prevunique", throw a DataError.
Unset the got value flag on the cursor.
Let request be the request created when this cursor was created.
Unset the done flag on request.
Run the steps for asynchronously executing a request with the cursor’s source as source and the steps for iterating a cursor with this cursor and key (if given), and request.

Calling this method more than once before new cursor data has been loaded - for example, calling continue() twice from the same onsuccess handler - results in an InvalidStateError exception being thrown on the second call because the cursor’s got value flag has been unset.

The continuePrimaryKey(key, primaryKey) method, when invoked, must run these steps:

Let transaction be this cursor's transaction.
If transaction is not active, throw a TransactionInactiveError.
If the cursor’s source or effective object store has been deleted, throw an InvalidStateError.
If this cursor’s source is not an index throw an InvalidAccessError.
If this cursor’s direction is not "next" or "prev", throw an InvalidAccessError.
If this cursor’s got value flag is unset, indicating that the cursor is being iterated or has iterated past its end, throw an InvalidStateError.
Let r be the result of running the steps to convert a value to a key with key. Rethrow any exceptions.
If r is invalid, throw a DataError.
Let key be r.
Let r be the result of running the steps to convert a value to a key with primaryKey. Rethrow any exceptions.
If r is invalid, throw a DataError.
Let primaryKey be r.
If key is less than or equal to this cursor’s position and this cursor’s direction is "next" or "nextunique", throw a DataError.
If key is greater than or equal to this cursor’s position and this cursor’s direction is "prev" or "prevunique", throw a DataError.
If key is equal to this cursor’s position and primaryKey is less than or equal to this cursor’s object store position and this cursor’s direction is "next" or "nextunique", throw a DataError.
If key is equal to this cursor’s position and primaryKey is greater than or equal to this cursor’s object store position and this cursor’s direction is "prev" or "prevunique", throw a DataError.
Unset the got value flag on the cursor.
Let request be the request created when this cursor was created.
Unset the done flag on request.
Run the steps for asynchronously executing a request with the cursor’s source as source and the steps for iterating a cursor with this cursor, key, primaryKey, and request.

🚧 The continuePrimaryKey() method is new in this edition, but not yet shipping in any browsers. 🚧

Calling this method more than once before new cursor data has been loaded - for example, calling continuePrimaryKey() twice from the same onsuccess handler - results in an InvalidStateError being thrown on the second call because the cursor’s got value flag has been unset.

The delete() method, when invoked, must run these steps:

Let transaction be this cursor's transaction.
If transaction is not active, throw a TransactionInactiveError.
If transaction is a read-only transaction, throw a ReadOnlyError.
If the cursor’s source or effective object store has been deleted, throw an InvalidStateError.
If this cursor’s got value flag is unset, indicating that the cursor is being iterated or has iterated past its end, throw an InvalidStateError.
If this cursor’s key only flag is set, throw an InvalidStateError.
Run the steps for asynchronously executing a request and return the IDBRequest created by these steps. The steps are run with this cursor as source and the steps for deleting records from an object store as operation, using this cursor’s effective object store and effective key as store and key respectively.

A cursor that has the key only flag unset implements the IDBCursorWithValue interface as well.

[Exposed=(Window,Worker)]
interface IDBCursorWithValue : IDBCursor {
  readonly attribute any value;
};

The value attribute’s getter must return the cursor’s current value. Note that if this property returns an object, it returns the same object instance every time it is inspected, until the cursor’s value is changed. This means that if the object is modified, those modifications will be seen by anyone inspecting the value of the cursor. However modifying such an object does not modify the contents of the database.

4.9. The `IDBTransaction` interface

transaction objects implement the following interface:

[Exposed=(Window,Worker)]
interface IDBTransaction : EventTarget {
  readonly attribute DOMStringList      objectStoreNames;
  readonly attribute IDBTransactionMode mode;
  readonly attribute IDBDatabase        db;
  readonly attribute DOMException       error;

  IDBObjectStore objectStore(DOMString name);
  void           abort();

  // Event handlers:
  attribute EventHandler onabort;
  attribute EventHandler oncomplete;
  attribute EventHandler onerror;
};

enum IDBTransactionMode {
  "readonly",
  "readwrite",
  "versionchange"
};

The objectStoreNames attribute’s getter must run the following steps:

If this transaction is an upgrade transaction, return a sorted list of the names of the object stores in this transaction's connection's object store set.
Otherwise, return a sorted list of the names of the object stores in this transaction's scope.

🎉 The objectStoreNames attribute is new in this edition. 🎉

The mode attribute’s getter must return the mode of the transaction.

The db attribute’s getter must return the database connection of which this transaction is a part.

The error attribute’s getter must return this transaction's error, or null if none.

If this transaction was aborted due to a failed request, this will be the same as the request's error. If this transaction was aborted due to an uncaught exception in an event handler, the error will be AbortError. If the transaction was aborted due to an error while committing, it will reflect the reason for the failure (e.g. QuotaExceededError, ConstraintError, or UnknownError).

The objectStore(name) method, when invoked, must run these steps:

If transaction has finished, throw an InvalidStateError.
Let store be the object store named name in this transaction's scope, or throw a NotFoundError if none.
Return an object store handle associated with store and this transaction.

Each call to this method on the same IDBTransaction instance with the same name returns the same IDBObjectStore instance.

The returned IDBObjectStore instance is specific to this IDBTransaction. If this method is called on a different IDBTransaction, a different IDBObjectStore instance is returned.

The abort() method, when invoked, must run these steps:

If this transaction is finished, throw an InvalidStateError.
Unset the transaction's active flag and run the steps for aborting a transaction with null as error.

The onabort attribute is the event handler for the abort event.

The oncomplete attribute is the event handler for the complete event.

The onerror attribute is the event handler for the error event.

To determine if a transaction has completed successfully, listen to the transaction's complete event rather than the success event of a particular request, because the transaction may still fail after the success event fires.

4.10. The `DOMStringList` interface

The DOMStringList interface represents an immutable ordered collection of zero or more DOMString values. The items in a DOMStringList are accessible via an integral index, starting from zero.

The DOMStringList interface was previously defined in [DOM-Level-3-core] but has been removed from the current versions of [DOM] and is now only referenced in this specification. It is hoped that in the future all uses of this type can be replaced by the conceptually similar FrozenArray<DOMString> to enable the use of other Array methods, but retaining support for the contains() method for compatibility with deployed content.

interface DOMStringList {
    readonly attribute unsigned long length;
    getter DOMString (unsigned long index);
    DOMString? item(unsigned long index);

    boolean contains(DOMString str);
};

The supported property indices for a DOMStringList list are the numbers zero to the number of items in list minus one. If list has no items, it has no supported property indices.

To determine the value of an indexed property for a given index index in a DOMStringList list, return the index^th item in list.

The length attribute’s getter must return the number of items in the collection.

The item(index) method must return the index^th item in the collection, or null if there are less than index + 1 items in the collection.

The contains(str) method must return true if str is equal to any item in the collection, and false otherwise.

5. Algorithms

5.1. Opening a database

The steps for opening a database are defined in the following steps. The algorithm in these steps takes four arguments: the origin which requested the database to be opened, a database name, a database version, and a request.

Let queue be the connection queue for origin and name.
Add request to queue.
Wait until all previous requests in queue have been processed.
Let db be the database named name in origin, or null otherwise.
If version is undefined, let version be 1 if db is null, or db’s version otherwise.
If db is null, let db be a new database with name name, version 0 (zero), and with no object stores.
If db’s version is greater than version, abort these steps and return a new VersionError.
Let connection be a new connection to db.
Set connection’s version to version.
If db’s version is less than version, run these substeps:
1. Let openConnections be the set of all connections, except connection, associated with db.
2. For each entry in openConnections that does not have its close pending flag set, queue a task to fire a version change event named versionchange at entry with db’s version and version.
  
  Firing this event might cause one or more of the other objects in openConnections to be closed, in which case the versionchange event must not be fired at those objects if that hasn’t yet been done.
3. Wait for all of the events to be fired.
4. If any of the connections in openConnections are still not closed, queue a task= to fire a version change event named blocked at request with db’s version and version.
5. Wait until all connections in openConnections are closed.
6. Run the steps for running an upgrade transaction using connection, version and request.
7. If connection was closed, create and return a newly created AbortError and abort these steps.
8. If the upgrade transaction was aborted, run the steps for closing a database connection with connection, create and return a newly created AbortError and abort these steps.
Return connection.

5.2. Closing a database

The steps for closing a database connection are as follows. These steps take two arguments, a connection object, and an optional forced flag.

Set the close pending flag of connection.
If the forced flag is set, then for each transaction created using connection run the steps for aborting a transaction with transaction and newly created AbortError.
Wait for all transactions created using connection to complete. Once they are complete, connection is closed.
If the forced flag is set, then fire a close event at connection. The event must use the Event interface and have its type set to "close". The event must not bubble or be cancelable.

🎉 This behavior is new in this edition. 🎉

5.3. Deleting a database

The steps for deleting a database are as follows. The algorithm in these steps takes three arguments: the origin that requested the database to be deleted, a database name, and a request.

Let queue be the connection queue for origin and name.
Add request to queue.
Wait until all previous requests in queue have been processed.
Let db be the database named name in origin, if one exists. Otherwise, return 0 (zero).
Let openConnections be the set of all connections associated with db.
For each entry in openConnections that does not have its close pending flag set, queue a task to fire a version change event named versionchange at entry with db’s version and null.

Firing this event might cause one or more of the other objects in openConnections to be closed, in which case the versionchange event must not be fired at those objects if that hasn’t yet been done.
Wait for all of the events to be fired.
If any of the connections in openConnections are still not closed, fire a version change event named blocked at request with db’s version and null.
Wait until all connections in openConnections are closed.
Let version be db’s version.
Delete db.
Return version.

5.4. Committing a transaction

When taking the steps for committing a transaction the implementation must execute the following algorithm. This algorithm takes one argument, the transaction to commit.

All the changes made to the database by transaction are written to the database.
If an error occurs while writing the changes to the database, abort the transaction by following the steps for aborting a transaction with transaction and an appropriate for the error, for example QuotaExceededError or UnknownError.
Queue a task to dispatch an event at transaction. The event must use the Event interface and have its type set to "complete". The event does not bubble and is not cancelable.

Even if an exception is thrown from one of the event handlers of this event, the transaction is still committed since writing the database changes happens before the event takes places. Only after the transaction has been successfully written is the "complete" event fired.

5.5. Aborting a transaction

When taking the steps for aborting a transaction the implementation must execute the following algorithm. This algorithm takes two arguments: the transaction to abort, and error.

All the changes made to the database by the transaction are reverted. For upgrade transactions this includes changes to the set of object stores and indexes, as well as the change to the version. Any object stores and indexes which were created during the transaction are now considered deleted for the purposes of other algorithms.
If transaction is an upgrade transactions, run the steps for aborting an upgrade transaction with transaction. This reverts changes to all connection, object store handle, and index handle instances associated with transaction.
If error is not null, set transaction’s error to error.
For each request in transaction’s request list with done flag unset, abort the steps for asynchronously executing a request for request and queue a task to run these substeps:
1. Set the done flag on request.
2. Set the result of request to undefined.
3. Set the error of request to a newly created AbortError.
4. Dispatch an event at request. The event must use the Event interface and have its type set to "error". The event bubbles and is cancelable.
This does not always result in any error events being fired. For example if a transaction is aborted due to an error while committing the transaction, or if it was the last remaining request that failed.
Queue a task to dispatch an event at transaction. The event must use the Event interface and have its type set to "abort". The event does bubble but is not cancelable.

5.6. Asynchronously executing a request

When taking the steps for asynchronously executing a request the implementation must run the following algorithm. The algorithm takes a source object and an operation to perform on a database, and an optional request.

These steps can be aborted at any point if the transaction the created request belongs to is aborted using the steps for aborting a transaction

Let transaction be the transaction associated with source.
If transaction is not active, throw a TransactionInactiveError.
If request was not given, let request be a new request with source as source
Add request to the end of transaction’s request list.
Return request and queue up the execution of the remaining steps in this algorithm.
Wait until all previously added requests in transaction have their done flag set.
Let result be the result of performing operation.
If result is an error, then revert all changes made by operation.

This only reverts the changes done by this request, not any other changes made by the transaction.
Queue a task to run these substeps:
1. Set the done flag on request.
2. If result is an error, then run these substeps:
  1. Set the result of request to undefined.
  2. Set the error of request to result.
  3. Fire an error event at request.
3. Otherwise, run these substeps:
  1. Set the result of request to result.
  2. Set the error of request to undefined.
  3. Fire a success event at request.

5.7. Running an upgrade transaction

The steps for running an upgrade transaction are as follows. This algorithm takes three arguments: a connection object which is used to update the database, a new version to be set for the database, and a request.

Let db be connection’s database.
Let transaction be a new upgrade transaction with connection used as connection. The scope of transaction includes every object store in connection.
Unset transaction’s active flag.
Start transaction.

Note that until this transaction is finished, no other connections can be opened to the same database.
Let old version be db’s version.
Set the version of db to version. This change is considered part of the transaction, and so if the transaction is aborted, this change is reverted.
Queue a task to run the following steps:
1. Set request’s result to connection.
2. Set request’s transaction to transaction.
3. Set the done flag on the request.
4. Fire a version change event named upgradeneeded at request with old version and version.
5. If an exception was propagated out from any event handler while dispatching the event in the previous step, abort the transaction by following the steps for aborting a transaction with the error property set to a newly created AbortError.
Wait for transaction to finish.
If transaction is aborted for any reason, the steps for aborting a transaction must be run.
When transaction is finished, immediately set request’s transaction to null. This must be done in the same task as the task firing the complete or abort event, but after the event has been fired.

5.8. Aborting an upgrade transaction

The steps for aborting an upgrade transaction transaction are as follows.

Let connection be transaction’s connection.
Let database be connection’s database.
Set connection’s version to database’s version if database previously existed, or 0 (zero) if database was newly created.

This reverts the value of version returned by the IDBDatabase object.
Set connection’s object store set to the set of object stores in database if database previously existed, or the empty set if database was newly created.

This reverts the value of objectStoreNames returned by the IDBDatabase object.
For each object store handle handle associated with transaction, including those for object stores that were deleted during transaction, run these substeps:
1. Set handle’s name to its object store's name.
2. Set handle’s index set to the set of indexes that reference its object store.
This reverts the values of name and indexNames returned by related IDBObjectStore objects.
Although script cannot access an object store by using the objectStore() method on an IDBTransaction instance after the transaction is aborted, it may still have references to IDBObjectStore instances where the name and indexNames properties can be queried.
For each index handle handle associated with transaction, including those for indexes that were deleted during transaction, run these substeps:
1. Set handle’s name to its index's name.
This reverts the value of name returned by related IDBIndex objects.
Although script cannot access an index by using the index() method on an IDBObjectStore instance after the transaction is aborted, it may still have references to IDBIndex instances where the name property can be queried.

The name property of the IDBDatabase instance is not modified, even if the aborted upgrade transaction was creating a new database.

5.9. Firing a success event

To fire a success event at a request, the implementation must run the following steps:

Set transaction to the transaction associated with the source.
Set the active flag of transaction.
Dispatch an event at request. The event must use the Event interface and have its type set to "success". The event does not bubble and is not cancelable.
Unset the active flag of transaction.
If an exception was propagated out from any event handler while dispatching the event in step 3, abort the transaction by following the steps for aborting a transaction with transaction and a newly created AbortError.

5.10. Firing an error event

To fire an error event at a request, the implementation must run the following steps:

Set transaction to the transaction associated with the source.
Set the active flag of transaction.
Dispatch an event at request. The event must use the Event interface and have its type set to "error". The event bubbles and is cancelable.
Unset the active flag of transaction.
If an exception was propagated out from any event handler while dispatching the event in step 3, abort the transaction by following the steps for aborting a transaction with transaction and a newly created AbortError and terminate these steps. This is done even if the event’s canceled flag is not set.

This means that if an error event is fired and any of the event handlers throw an exception, transaction’s error property is set to an AbortError rather than request’s error, even if preventDefault() is never called.
If the event’s canceled flag is not set, run the steps for aborting a transaction using transaction and request's error.

6. Database operations

This section describes various operations done on the data in object stores and indexes in a database. These operations are run by the steps for asynchronously executing a request.

6.1. Object Store Storage Operation

The steps for storing a record into an object store with store, value, an optional key, and a no-overwrite flag are as follows.

If store uses in-line keys, run these substeps:
1. Let kpk be the result of running the steps to extract a key from a value using a key path with value and store’s key path.
2. Assert: kpk will not be invalid or an exception.
3. If kpk is not failure, let key be kpk.
If store uses a key generator, run these substeps:
1. If key is undefined, run these substeps:
  1. If the key generator's current number is greater than 2⁵³ (9007199254740992), then this operation failed with a ConstraintError. Abort this algorithm without taking any further steps.
  2. Set key to the key generator's current number
  3. Increase the key generator's current number by 1.
  4. If store also uses in-line keys, then run the steps to inject a key into a value using a key path with value, key and store’s key path.
2. Otherwise, if the type of key is number and the value is greater than or equal to the key generator's current number, set the current number to lowest integer greater than key.
If the no-overwrite flag was given to these steps and is set, and a record already exists in store with its key equal to key, then this operation failed with a ConstraintError. Abort this algorithm without taking any further steps.
If a record already exists in store with its key equal to key, then remove the record from store using the steps for deleting records from an object store.
Store a record in store containing key as its key and value as its value. The record is stored in the object store’s list of records such that the list is sorted according key of the records in ascending order.
For each index which reference store, run these substeps:
1. Let index key be the result of running the steps to extract a key from a value using a key path with value, index’s key path, and index’s multiEntry flag.
2. If index key is an exception, or invalid, or failure, take no further actions for this index, and continue these substeps for the next index.
  
  An exception thrown in this step is not rethrown.
3. If index’s multiEntry flag is unset, or if index key is not an array key, and if index already contains a record with key equal to index key, and index has its unique flag set, then this operation failed with a ConstraintError. Abort this algorithm without taking any further steps.
4. If index’s multiEntry flag is set and index key is an array key, and if index already contains a record with key equal to any of the subkeys of index key, and index has its unique flag set, then this operation failed with a ConstraintError. Abort this algorithm without taking any further steps.
5. If index’s multiEntry flag is unset, or if index key is not an array key then store a record in index containing index key as its key and key as its value. The record is stored in index’s list of records such that the list is sorted primarily on the records keys, and secondarily on the records values, in ascending order.
6. If index’s multiEntry flag is set and index key is an array key, then for each subkey of the subkeys of index key store a record in index containing subkey as its key and key as its value. The records are stored in index’s list of records such that the list is sorted primarily on the records keys, and secondarily on the records values, in ascending order.
  
  It is valid for there to be no subkeys. In this case no records are added to the index.
  
  Even if any member of subkeys is an array key, the member is used directly as the key for the index record. Nested array keys are not flattened or "unpacked" to produce multiple rows; only the outer-most array key
Return key.

6.2. Object Store Retrieval Operations

The steps for retrieving a value from an object store with store and range are as follows:

Let record be the first record in store’s list of records whose key is in range, if any.
If record was not found, return undefined.
Return a structured clone of record’s value.

The steps for retrieving multiple values from an object store with store, range and optional count are as follows:

If count is not given or is 0 (zero), let count be infinity.
Let records be a list containing the first count records in store’s list of records whose key is in range.
Let array be a new Array object.
Let index be 0.
For each record in records, run these substeps:
1. Let entry be a structured clone of record’s value.
2. Let status be CreateDataProperty(array, index, entry).
3. Assert: status is true.
4. Increase index by 1.
Return array.

The steps for retrieving a key from an object store with store and range are as follows:

Let record be the first record in store’s list of records whose key is in range, if any.
If record was not found, return undefined.
Return record’s key.

The steps for retrieving multiple keys from an object store with store, range and optional count are as follows:

If count is not given or is 0 (zero), let count be infinity.
Let records be a list containing the first count records in store’s list of records whose key is in range.
Let array be a new Array object.
Let index be 0.
For each record in records, run these substeps:
1. Let entry be the result of running the steps to convert a key to a value with record’s key.
2. Let status be CreateDataProperty(array, index, entry).
3. Assert: status is true.
4. Increase index by 1.
Return array.

6.3. Index Retrieval Operations

The steps for retrieving a referenced value from an index with index and range are as follows.

Let record be the first record in index’s list of records whose key is in range, if any.
If record was not found, return undefined.
Return a structured clone of record’s referenced value.

The steps for retrieving multiple referenced values from an index with index, range and optional count are as follows:

If count is not given or is 0 (zero), let count be infinity.
Let records be a list containing the first count records in index’s list of records whose key is in range.
Let array be a new Array object.
Let index be 0.
For each record in records, run these substeps:
1. Let entry be a structured clone of record’s referenced value.
2. Let status be CreateDataProperty(array, index, entry).
3. Assert: status is true.
4. Increase index by 1.
Return array.

The steps for retrieving a value from an index with index and range are as follows.

Let record be the first record in index’s list of records whose key is in range, if any.
If record was not found, return undefined.
Return record’s value.

The steps for retrieving multiple values from an index with index, range and optional count are as follows:

If count is not given or is 0 (zero), let count be infinity.
Let records be a list containing the first count records in index’s list of records whose key is in range.
Let array be a new Array object.
Let index be 0.
For each record in records, run these substeps:
1. Let entry be the result of running the steps to convert a key to a value with record’s value.
2. Let status be CreateDataProperty(array, index, entry).
3. Assert: status is true.
4. Increase index by 1.
Return array.

6.4. Object Store Deletion Operation

The steps for deleting records from an object store with store and range are as follows.

Remove all records, if any, from store’s list of records with key in range.
For each index which references store, remove every record from index’s list of records whose value is in range, if any such records exist.
Return undefined.

6.5. Record Counting Operation

The steps to count the records in a range with source and range are as follows:

Let count be the number of records, if any, in source’s list of records with key in range.
Return count.

6.6. Object Store Clear Operation

The steps for clearing an object store with store are as follows.

Remove all records from store.
In all indexes which reference store, remove all records.
Return undefined.

6.7. Cursor Iteration Operation

The steps for iterating a cursor with cursor, an optional key and primaryKey to iterate to, and an optional count are as follows.

Let source be cursor’s source.
Let direction be cursor’s direction.
Assert: if primaryKey is given, source is an index and direction is "next" or "prev".
Let records be the list of records in source.

records is always sorted in ascending key order. In the case of source being an index, records is secondarily sorted in ascending value order (where the value in an index is the key of the record in the referenced object store).
Let range be cursor’s range.
Let position be cursor’s position.
Let object store position be cursor’s object store position.
If count is not given, let count be 1.
While count is greater than 0, run these substeps:
1. Switch on direction:
  "next"
  Let found record be the first record in records which satisfy all of the following requirements:
  - If key is defined, the record’s key is greater than or equal to key.
  - If primaryKey is defined, the record’s key is equal to key and the record’s value is greater than or equal to primaryKey, or the record’s key is greater than key.
  - If position is defined, and source is an object store, the record’s key is greater than position.
  - If position is defined, and source is an index, the record’s key is equal to position and the record’s value is greater than object store position or the record’s key is greater than position.
  - The record’s key is in range.
  "nextunique"
  Let found record be the first record in records which satisfy all of the following requirements:
  - If key is defined, the record’s key is greater than or equal to key.
  - If position is defined, the record’s key is greater than position.
  - The record’s key is in range.
  "prev"
  Let found record be the last record in records which satisfy all of the following requirements:
  - If key is defined, the record’s key is less than or equal to key.
  - If primaryKey is defined, the record’s key is equal to key and the record’s value is less than or equal to primaryKey, or the record’s key is less than key.
  - If position is defined, and source is an object store, the record’s key is less than position.
  - If position is defined, and source is an index, the record’s key is equal to position and the record’s value is less than object store position or the record’s key is less than position.
  - The record’s key is in range.
  "prevunique"
  Let temp record be the last record in records which satisfy all of the following requirements:
  - If key is defined, the record’s key is less than or equal to key.
  - If position is defined, the record’s key is less than position.
  - The record’s key is in range.
  If temp record is defined, let found record be the first record in records whose key is equal to temp record’s key.
  
  Iterating with "prevunique" visits the same records that "nextunique" visits, but in reverse order.
2. If found record is not defined, run these substeps:
  1. Set cursor’s key to undefined.
  2. If source is an index, set cursor’s object store position to undefined.
  3. If cursor’s key only flag is unset, set cursor’s value to undefined.
  4. Return null.
3. Let position be found record’s key.
4. If source is an index, let object store position be found record’s value.
5. Decrease count by 1.
Set cursor’s position to position.
If source is an index, set cursor’s object store position to object store position.
Set cursor’s key to found record’s key.
If cursor’s key only flag is unset, set cursor’s value to a structured clone of found record’s referenced value.
Set cursor’s got value flag.
Return cursor.

7. ECMAScript binding

This section defines how key values defined in this specification are converted to and from ECMAScript values, and how they may be extracted from and injected into ECMAScript values using key paths. This section references types and algorithms from the ECMAScript Language Specification. [ECMA-262]

7.1. Extract a key from a value

The steps to extract a key from a value using a key path with value, keyPath and an optional multiEntry flag are as follows. The result of these steps is a key, invalid, or failure, or the steps may throw an exception.

Let r be the result of running the steps to evaluate a key path on a value with value and keyPath. Rethrow any exceptions.
If r is failure, return failure.
Let key be the result of running the steps to convert a value to a key with r if the multiEntry flag is unset, and the result of running the steps to convert a value to a multiEntry key with r otherwise. Rethrow any exceptions.
If key is invalid, return invalid.
Return key.

The steps to evaluate a key path on a value with value and keyPath are as follows. The result of these steps is an ECMAScript value or failure, or the steps may throw an exception.

If keyPath is a sequence<DOMString>, run these substeps:
1. Let result be a new Array ECMAScript object.
2. For each item in the keyPath sequence, run these substeps:
  1. Let key be the result of recursively running the steps to extract a key from a value using a key path using item as keyPath and value as value.
  2. ReturnIfAbrupt(key)
  3. If key is failure, abort the overall algorithm and return failure.
  4. Append the result of the first sub-step to end of result.
3. Return result.
  
  This will only ever "recurse" one level since key path sequences can’t ever be nested.
If keyPath is the empty string, return value and skip the remaining steps.
Let identifiers be the result of strictly splitting the string keyPath on U+002E FULL STOP characters (.).
For each identifier in identifiers, run these substeps:
1. If Type(value) is String, and identifier is the last item in identifiers, and identifier is "length", return a Number equal to the number of elements in value.
2. If Type(value) is not Object, return failure.
3. Let value be value.[[Get]](identifier, value)
4. ReturnIfAbrupt(value)
5. If value is Undefined, return failure.
Return value.

7.2. Inject a key into a value

The steps to inject a key into a value using a key path are as follows. The algorithm takes a value, a key and a keyPath.

Let identifiers be the result of strictly splitting the string keyPath on U+002E FULL STOP characters (.).
Assert: identifiers is not empty.
Let last be the last member of identifiers and remove it from the list.
For each remaining identifier in identifiers, run these substeps:
1. If value is not an Object object or an Array object (see structured clone algorithm [HTML]), then throw a DataError.
2. Let hop be HasOwnProperty(value, identifier)
3. Assert: hop is not an abrupt completion.
4. If hop is false, run these substeps:
  1. Let o be a new Object.
  2. Let status be CreateDataProperty(value, identifier, o)
  3. Assert: status is true
5. Let value be value.[[Get]](identifier, value)
6. Assert: value is not an abrupt completion.
Assert: value is an Object or an Array.
Let keyValue be the result of running the steps to convert a key to a value.
Let status be CreateDataProperty(value, last, keyValue)
Assert: status is true

7.3. Convert a key to a value

The steps to convert a key to a value are as follows. These steps take one argument, key, and return an ECMAScript value.

Let type be key’s type.
Let value be key’s value.
Switch on type:
number
Return an ECMAScript Number value equal to value
string
Return an ECMAScript String value equal to value
date
1. Let date be the result of executing the ECMAScript Date constructor with the single argument value
2. Assert: date is not an abrupt completion.
3. Return date
binary
1. Let len be the length of value.
2. Let buffer be the result of executing the ECMAScript ArrayBuffer constructor with len.
3. Assert: buffer is not an abrupt completion.
4. Set the entries in buffer’s [[ArrayBufferData]] internal slot to the entries in value.
5. Return buffer
array
1. Let array be the result of executing the ECMAScript Array constructor with no arguments.
2. Assert: array is not an abrupt completion.
3. Let len be the length of value.
4. Let index be 0.
5. While index is less than len, run these substeps:
  1. Let entry be the result of running the steps to convert a key to a value with the indexth entry of value as input.
  2. Let status be CreateDataProperty(array, index, entry).
  3. Assert: status is true.
  4. Increase index by 1.
6. Return array

7.4. Convert a value to a key

The steps to convert a value to a key are as follows. These steps take two arguments, an ECMAScript value input, and an optional set seen. The result of these steps is a key or invalid, or the steps may throw an exception.

If seen was not given, let seen be a new empty set
If input is in seen return invalid
Jump to the appropriate step below:
If Type(input) is Number
1. If input is NaN then return invalid.
2. Otherwise, return a new key with type number and value input
If input has an [[DateValue]] internal slot
1. Let ms be the value of input’s [[DateValue]] internal slot.
2. If ms is NaN then return invalid.
3. Otherwise, return a new key with type date and value ms.
If Type(input) is String
1. Return a new key with type string and value input.
If input has an [[ArrayBufferData]] internal slot or an [[ViewedArrayBuffer]] internal slot
1. Let octets be the result of running the steps for getting a copy of the bytes held by a buffer source with value. Rethrow any exceptions.
2. Return a new key with type binary and value octets.
If IsArray(input)
1. Let len be the ToLength(Get(input, "length"))
2. Assert: len will never an abrupt completion.
3. Add input to seen
4. Let keys be a new empty list
5. Let index be 0
6. While index is less than len, run these substeps:
  1. Let entry be input.[[Get]](index, input)
  2. ReturnIfAbrupt(entry)
  3. Let key be the result of running the steps to convert a value to a key with arguments entry and seen
  4. ReturnIfAbrupt(key)
  5. If key is invalid or an exception, then abort these steps and return key.
  6. Append key to keys
  7. Increase index by 1
7. Return a new array key with value keys.
Otherwise
Return invalid

The steps to convert a value to a multiEntry key are as follows. These steps take one argument, an ECMAScript value input. The result of these steps is a key or invalid, or the steps may throw an exception.

If IsArray(input), then:
1. Let len be the ToLength(Get(input, "length")).
2. Assert: len will never an abrupt completion.
3. Let seen be a new set containing only input.
4. Let keys be a new empty set.
5. Let index be 0.
6. While index is less than len, run these substeps:
  1. Let entry be input.[[Get]](index, input)
  2. If entry is not an exception, run these substeps:
    1. Let key be the result of running the steps to convert a value to a key with arguments entry and seen
    2. If key is not invalid or an exception, add key to keys if there are no other members of keys equal to key
  3. Increase index by 1
Return a new array key with value set to a list of the members of keys.
Otherwise, return the result of running the steps to convert a value to a key with argument input.

8. Privacy Considerations

This section is non-normative.

8.1. User tracking

A third-party host (or any object capable of getting content distributed to multiple sites) could use a unique identifier stored in its client-side database to track a user across multiple sessions, building a profile of the user’s activities. In conjunction with a site that is aware of the user’s real id object (for example an e-commerce site that requires authenticated credentials), this could allow oppressive groups to target individuals with greater accuracy than in a world with purely anonymous Web usage.

There are a number of techniques that can be used to mitigate the risk of user tracking:

Blocking third-party storage

User agents may restrict access to the database objects to scripts originating at the domain of the top-level document of the browsing context, for instance denying access to the API for pages from other domains running in iframes.

Expiring stored data

User agents may automatically delete stored data after a period of time.

This can restrict the ability of a site to track a user, as the site would then only be able to track the user across multiple sessions when she authenticates with the site itself (e.g. by making a purchase or logging in to a service).

However, this also puts the user’s data at risk.

Treating persistent storage as cookies

User agents should present the database feature to the user in a way that associates them strongly with HTTP session cookies. [COOKIES]

This might encourage users to view such storage with healthy suspicion.

Site-specific white-listing of access to databases

User agents may require the user to authorize access to databases before a site can use the feature.

Origin-tracking of stored data

User agents may record the origins of sites that contained content from third-party origins that caused data to be stored.

If this information is then used to present the view of data currently in persistent storage, it would allow the user to make informed decisions about which parts of the persistent storage to prune. Combined with a blacklist ("delete this data and prevent this domain from ever storing data again"), the user can restrict the use of persistent storage to sites that she trusts.

Shared blacklists

User agents may allow users to share their persistent storage domain blacklists.

This would allow communities to act together to protect their privacy.

While these suggestions prevent trivial use of this API for user tracking, they do not block it altogether. Within a single domain, a site can continue to track the user during a session, and can then pass all this information to the third party along with any identifying information (names, credit card numbers, addresses) obtained by the site. If a third party cooperates with multiple sites to obtain such information, a profile can still be created.

However, user tracking is to some extent possible even with no cooperation from the user agent whatsoever, for instance by using session identifiers in URLs, a technique already commonly used for innocuous purposes but easily repurposed for user tracking (even retroactively). This information can then be shared with other sites, using using visitors' IP addresses and other user-specific data (e.g. user-agent headers and configuration settings) to combine separate sessions into coherent user profiles.

If the user interface for persistent storage presents data in the persistent storage features described in this specification separately from data in HTTP session cookies, then users are likely to delete data in one and not the other. This would allow sites to use the two features as redundant backup for each other, defeating a user’s attempts to protect his privacy.

8.3. Sensitivity of data

User agents should treat persistently stored data as potentially sensitive; it is quite possible for e-mails, calendar appointments, health records, or other confidential documents to be stored in this mechanism.

To this end, user agents should ensure that when deleting data, it is promptly deleted from the underlying storage.

9. Security Considerations

9.1. DNS spoofing attacks

Because of the potential for DNS spoofing attacks, one cannot guarantee that a host claiming to be in a certain domain really is from that domain. To mitigate this, pages can use SSL. Pages using SSL can be sure that only pages using SSL that have certificates identifying them as being from the same domain can access their databases.

9.2. Cross-directory attacks

Different authors sharing one host name, for example users hosting content on geocities.com, all share one set of databases.

There is no feature to restrict the access by pathname. Authors on shared hosts are therefore recommended to avoid using these features, as it would be trivial for other authors to read the data and overwrite it.

9.3. Implementation risks

The two primary risks when implementing these persistent storage features are letting hostile sites read information from other domains, and letting hostile sites write information that is then read from other domains.

Letting third-party sites read data that is not supposed to be read from their domain causes information leakage, For example, a user’s shopping wish list on one domain could be used by another domain for targeted advertising; or a user’s work-in-progress confidential documents stored by a word-processing site could be examined by the site of a competing company.

Letting third-party sites write data to the persistent storage of other domains can result in information spoofing, which is equally dangerous. For example, a hostile site could add records to a user’s wish list; or a hostile site could set a user’s session identifier to a known ID that the hostile site can then use to track the user’s actions on the victim site.

Thus, strictly following the origin model described in this specification is important for user security.

10. Revision History

The following is an informative summary of the changes since the last publication of this specification. A complete revision history can be found here. For the revision history of the First Edition, see that document’s Revision History.

Address comparison of empty arrays. (bug #27712)
Added openKeyCursor() on IDBObjectStore. (bug #19955)
Correct source used for get(), getKey() and openKeyCursor() on IDBIndex.
Added details around garbage collection of IDBDatabase objects. (bug #25223)
Added [Exposed=(Window,Worker)] annotations to interfaces.
Added forced flag to the steps for closing a database connection, described the firing of a "close" event, and onclose. (bug #22540)
Converted specification to a more algorithmic style, and define abstract types such as key more rigorously. (bug #17681)
Added getAll() and getAllKeys() on IDBObjectStore, and getAll() and getAllKeys() on IDBIndex. (bug #16595)
Replaced DOMError with DOMException. (bug #16)
Added objectStoreNames on IDBTransaction. (bug #18)
Added binary keys, including comparisons and ECMAScript bindings. (bug #21)
Allow renaming stores and indexes via IDBObjectStore's name and IDBIndex's name attribute setters. (bug #22)
Added continuePrimaryKey() on IDBCursor. (bug #14)
Added includes() on IDBKeyRange. (bug #41)
Added getKey() on IDBObjectStore. (bug #26)
Clarified when a transaction can attempt to commit. (bug #77)
Clarified open request / connection queue processing. (bug #9, bug #78, bug #79, bug #81)
Added DOMStringList. (bug #28)

11. Acknowledgements

Special thanks to Nikunj Mehta, the original author of the first edition, and Jonas Sicking, Eliot Graff, Andrei Popescu, and Jeremy Orlow, additional editors of the First Edition.

Garret Swart was extremely influential in the design of this specification.

Thanks to Tab Atkins, Jr. for creating and maintaining Bikeshed, the specification authoring tool used to create this document.

Special thanks to Chris Anderson, Pablo Castro, Kristof Degrave, Jake Drew, Ben Dilts, João Eiras, Alec Flett, Dana Florescu, David Grogan, Israel Hilerio, Kyle Huey, Laxminarayan G Kamath A, Anne van Kesteren, Adam Klein, Tobie Langel, Kang-Hao Lu, Andrea Marchesini, Glenn Maynard, Ms2ger, Odin Omdal, Danillo Paiva, Olli Pettay, Simon Pieters, Anthony Ramine, Yonathan Randolph, Arun Ranganathan, Margo Seltzer, Maciej Stachowiak, Ben Turner, Kyaw Tun, Hans Wennborg, Shawn Wilsher, Boris Zbarsky, Zhiqiang Zhang, and Kris Zyp, all of whose feedback and suggestions have led to improvements to this specification.

Indexed Database API 2.0

W3C First Public Working Draft, 18 August 2016

Abstract

Status of this document

1. Introduction

2. Constructs

2.1. Database

2.1.1. Database Connection

2.2. Object Store

2.2.1. Object Store Handle

2.3. Values

2.4. Keys

2.5. Key Path

2.6. Index

2.6.1. Index Handle

2.7. Transactions

2.7.1. Transaction Lifetime

2.7.2. Upgrade Transactions

2.8. Requests

2.8.1. Open Requests

2.9. Key Range

2.10. Cursor

2.11. Key Generators

3. Exceptions

4. API

4.1. The IDBRequest interface

4.2. Event interfaces

4.3. The IDBFactory interface

4.4. The IDBDatabase interface

4.5. The IDBObjectStore interface

4.6. The IDBIndex interface

4.7. The IDBKeyRange interface

4.8. The IDBCursor interface

4.9. The IDBTransaction interface

4.10. The DOMStringList interface

5. Algorithms

5.1. Opening a database

5.2. Closing a database

5.3. Deleting a database

5.4. Committing a transaction

5.5. Aborting a transaction

5.6. Asynchronously executing a request

5.7. Running an upgrade transaction

5.8. Aborting an upgrade transaction

5.9. Firing a success event

5.10. Firing an error event

6. Database operations

6.1. Object Store Storage Operation

6.2. Object Store Retrieval Operations

6.3. Index Retrieval Operations

6.4. Object Store Deletion Operation

6.5. Record Counting Operation

6.6. Object Store Clear Operation

6.7. Cursor Iteration Operation

7. ECMAScript binding

7.1. Extract a key from a value

7.2. Inject a key into a value

7.3. Convert a key to a value

7.4. Convert a value to a key

8. Privacy Considerations

8.1. User tracking

8.2. Cookie resurrection

8.3. Sensitivity of data

9. Security Considerations

9.1. DNS spoofing attacks

9.2. Cross-directory attacks

9.3. Implementation risks

10. Revision History

11. Acknowledgements

Conformance

Document conventions

Conformant Algorithms

Index

Terms defined by this specification

Terms defined by reference

References

Normative References

Informative References

IDL Index

Issues Index

4.1. The `IDBRequest` interface

4.3. The `IDBFactory` interface

4.4. The `IDBDatabase` interface

4.5. The `IDBObjectStore` interface

4.6. The `IDBIndex` interface

4.7. The `IDBKeyRange` interface

4.8. The `IDBCursor` interface

4.9. The `IDBTransaction` interface

4.10. The `DOMStringList` interface