This repository has been archived by the owner on Jan 13, 2022. It is now read-only.
bad keyPath for indices created from WebSQL data #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
i think this was a mistake, as erroring reporting fails.
keypaths for indices were fine when they were initially created (via createIndex), but when they are regenerated from WebSQL they were unparsed JSON strings.
|
oh hell, looking at issue #3 would have saved me some time and headaches - this is the same problem |
Cache native WebSQL database objects
|
Facebook is no longer actively maintaining or supporting this repo, and we are closing its old and outstanding pull requests. Many, many thanks for your support of the project. If you have any further questions, please don't hesitate to let us know. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Indices generated from WebSQL data have unparsed JSON for keyPath.
If the index was created via
IDBObjectStore.createIndex, then it is fine. However once the page is reloaded and the index is recreated viaIDBDatabase._loadObjectStoresthen it has the wrong keyPath. No error is reported, but the index is never updated for new and updated records.