pending/deleted index/store behavior (renaming, recreating, etc.) #276
Comments
brettz9
added a commit
to brettz9/IndexedDBShim
that referenced
this issue
Mar 30, 2017
…-create an object store that was deleted")
- Fix: Distinguish deleted and pending deleted stores and indexes;
for insertion operations, do index checks independent of
`indexNames` in case subsequently deleted by `deleteIndex` (indexeddbshim#276)
- Testing (Grunt): Make QUnit tasks more granular
- Testing (QUnit): Avoid origin-checking
brettz9
added a commit
to brettz9/IndexedDBShim
that referenced
this issue
Mar 31, 2017
for insertion operations, do index checks independent of
`indexNames` in case subsequently deleted by `deleteIndex` (indexeddbshim#276)
- Fix: Ensure same index instance object returned for same store object and
index name
- Fix: Better error reporting for `IDBRequest.error` or `IDBRequest.result`
errors.
- Testing (Grunt): Make QUnit tasks more granular
- Testing (QUnit): Avoid origin-checking
- Testing (W3C): Report on bad files not expected to be such (not in the list)
- Testing (Mocha): Add test for index instance clones
Current IndexedDB (and domstringlist) test statuses
'Pass': 1102, (including 4 domstringlist tests but avoiding exclusions)
'Fail': 69,
'Timeout': 4,
'Not Run': 2,
'Total tests': 1177 (including 4 domstringlist tests but avoiding exclusions)
322 normal files (including 1 domstringlist file):
288 are all good, 30 have at least some bad, 4 time out, 2 do not run
7 excluded files (uncaught exceptions during testing)
|
Fixed in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was already mentioned in the Version 3.0.0 goals, but I wanted a separate issue for this. We need to take a particular look at:
w3c/IDBObjectStore.createIndex.jsIDBObjectStorehandle instancesThe text was updated successfully, but these errors were encountered: