Update sqlite3 and sqlite3_web, deprecate flush parameter#153
Open
simolus3 wants to merge 2 commits into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This updates
sqlite3andsqlite3_webdependencies. Mainly, these updates improve IndexedDB support to always batch up changes made during awriteLockcall and commit them in the end in a single IndexedDB transaction. Because that is more efficient,sqlite3_webwill also auto-flush writes to IndexedDB at the end ofwriteLockcalls. Thus, theflushparameter is no longer necessary and we can mark it as deprecated.