You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 6-data-storage/03-indexeddb/article.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ let openRequest = indexedDB.open(name, version);
34
34
We can have many databases with different names, but all of them exist within the current origin (domain/protocol/port). Different websites can't access each other's databases.
35
35
36
36
The call returns `openRequest` object, we should listen to events on it:
37
-
-`success`: database is ready, there's the "database object" in `openRequest.result`, that we should use it for further calls.
37
+
-`success`: database is ready, there's the "database object" in `openRequest.result`, we should use it for further calls.
38
38
-`error`: opening failed.
39
39
-`upgradeneeded`: database is ready, but its version is outdated (see below).
40
40
@@ -117,7 +117,7 @@ Let's say:
117
117
2. Then we rolled out an update, so our code is newer.
118
118
3. And then the same visitor opens our site in another tab.
119
119
120
-
So there's a tab with an open connection to DB version `1`, while the second tab one attempts to update it to version `2` in its `upgradeneeded` handler.
120
+
So there's a tab with an open connection to DB version `1`, while the second one attempts to update it to version `2` in its `upgradeneeded` handler.
121
121
122
122
The problem is that a database is shared between two tabs, as it's the same site, same origin. And it can't be both version `1` and `2`. To perform the update to version `2`, all connections to version 1 must be closed, including the one in the first tab.
// this event shouldn't trigger if we handle onversionchange correctly
154
154
155
155
// it means that there's another open connection to same database
156
-
// and it wasn't closed after db.onversionchange triggered for them
156
+
// and it wasn't closed after db.onversionchange triggered for it
157
157
};
158
158
*/!*
159
159
```
@@ -687,7 +687,7 @@ Whether there are more values matching the cursor or not -- `onsuccess` gets cal
687
687
688
688
In the example above the cursor was made for the object store.
689
689
690
-
But we also can make a cursor over an index. As we remember, indexes allow to search by an object field. Cursors over indexes to precisely the same as over object stores -- they save memory by returning one value at a time.
690
+
But we also can make a cursor over an index. As we remember, indexes allow to search by an object field. Cursors over indexes do precisely the same as over object stores -- they save memory by returning one value at a time.
691
691
692
692
For cursors over indexes, `cursor.key` is the index key (e.g. price), and we should use `cursor.primaryKey` property for the object key:
0 commit comments