Closed ghost closed 9 years ago
IndexedDB has a buggy implementation on Safari when it comes to multiple object stores. I've tried to do my best to work around some of the bugs. One of the bugs is that multiple stores cannot have primary keys that collide. This is something that could be worked around, but not as part of Dexie because it would bloat the library.
However, if I get you correct, you cannot even define multiple object stores. This is something that could be fixed I believe. Could you see at which line in Dexie.js it fails? (If you see a stack on the catched error, or if you could debug it and see if it throws an exception somewhere)
The error says: The error that comes up is NotFoundError: DOM IDBBatabase Exception 8, line 529, column 87
Which appears to be this line: adjustToExistingIndexNames(globalSchema, idbdb.transaction(safariMultiStoreFix(idbdb.objectStoreNames), READONLY));
I've tried using the polyfill shim as well and force use on safari using
window.shimIndexedDB.__useShim()
With no luck. Is there an issue with using the shim with Dexie.js or is safari just hopelessly bugged?
Need to adjust the polyfill as describe in Issue #63 to make it work.
Not needed to adjust the IndexedDBShim anymore. See #77 !
I seem to be struggling with Dexie.js on an iPad. Can anyone please help me figure out why this code is seems fine on chrome but won't work on an ipad? If i comment out the folder store, it seems to work fine. I've even tried with the newest version uploaded 3 days ago without any luck.
The error that comes up is NotFoundError: DOM IDBBatabase Exception 8, line 529, column 87