--- title: IDBIndex slug: Web/API/IDBIndex tags: - API - Database - IDBIndex - IndexedDB - Interface - NeedsTranslation - Reference - Storage - TopicStub translation_of: Web/API/IDBIndex ---
{{APIRef("IndexedDB")}}
IDBIndex interface of the IndexedDB API provides asynchronous access to an index in a database. An index is a kind of object store for looking up records in another object store, called the referenced object store. You use this interface to retrieve data.
You can retrieve records in an object store through the primary key or by using an index. An index lets you look up records in an object store using properties of the values in the object stores records other than the primary key
The index is a persistent key-value storage where the value part of its records is the key part of a record in the referenced object store. The records in an index are automatically populated whenever records in the referenced object store are inserted, updated, or deleted. Each record in an index can point to only one record in its referenced object store, but several indexes can reference the same object store. When the object store changes, all indexes that refers to the object store are automatically updated.
You can grab a set of keys within a range. To learn more, see {{domxref("IDBKeyRange")}}.
{{AvailableInWorkers}}
locale value of auto specified upon its creation (see createIndex()'s optionalParameters.)en-US, or pl) if it had a locale value specified upon its creation (see createIndex()'s optionalParameters.)true, there is one record in the index for each item in an array of keys. If false, then there is one record for each key that is an array.true, this index does not allow duplicate values for a key.Inherits from: EventTarget
key is an {{domxref("IDBKeyRange")}}.key is an {{domxref("IDBKeyRange")}}.key is an {{domxref("IDBKeyRange")}}.key is an {{domxref("IDBKeyRange")}}.In the following example we open a transaction and an object store, then get the index lName from a simple contacts database. We then open a basic cursor on the index using {{domxref("IDBIndex.openCursor")}} — this works the same as opening a cursor directly on an ObjectStore using {{domxref("IDBObjectStore.openCursor")}} except that the returned records are sorted based on the index, not the primary key.
Finally, we iterate through each record, and insert the data into an HTML table. For a complete working example, see our IDBIndex-example demo repo (View the example live.)
function displayDataByIndex() {
tableEntry.innerHTML = '';
var transaction = db.transaction(['contactsList'], 'readonly');
var objectStore = transaction.objectStore('contactsList');
var myIndex = objectStore.index('lName');
myIndex.openCursor().onsuccess = function(event) {
var cursor = event.target.result;
if(cursor) {
var tableRow = document.createElement('tr');
tableRow.innerHTML = '<td>' + cursor.value.id + '</td>'
+ '<td>' + cursor.value.lName + '</td>'
+ '<td>' + cursor.value.fName + '</td>'
+ '<td>' + cursor.value.jTitle + '</td>'
+ '<td>' + cursor.value.company + '</td>'
+ '<td>' + cursor.value.eMail + '</td>'
+ '<td>' + cursor.value.phone + '</td>'
+ '<td>' + cursor.value.age + '</td>';
tableEntry.appendChild(tableRow);
cursor.continue();
} else {
console.log('Entries all displayed.');
}
};
};
| Specification | Status | Comment |
|---|---|---|
| {{SpecName('IndexedDB', '#idl-def-IDBIndex', 'IDBIndex')}} | {{Spec2('IndexedDB')}} | |
| {{SpecName("IndexedDB 2", "#index-interface", "IDBIndex")}} | {{Spec2("IndexedDB 2")}} |
{{Compat}}