powersync-sqlite-core 0.3.0 #14
Merged
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
10 tasks
stevensJourney
approved these changes
Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Copied release notes from powersync-sqlite-core:
This release removes major performance bottlenecks during incremental sync. Previously, incremental sync would have overhead proportional to the number of synced rows, which typically caused noticeable latency when syncing around 10-100k+ rows. Now, the overhead is only proportional to the number of buckets synced.
The performance improvements required a restructure in the data storage format. Data is migrated automatically, and an app can downgrade back to v0.2.0 or v0.2.1 of powersync-sqlite-core.
Changes:
powersync_init()instead of extension init, to support SQLCipher.See: powersync-ja/powersync-sqlite-core#29