Add powersync_trigger_resync#166
Merged
Merged
Conversation
rkistner
reviewed
Feb 16, 2026
rkistner
left a comment
rkistner
left a comment
Contributor
There was a problem hiding this comment.
I think we should also clear the hasSynced status here. But the progress counts can stay as-is? I haven't thought through every scenario here yet.
Contributor
|
On second thought, that probably doesn't apply to all cases. Maybe that should be opt-in or a separate function call? |
Contributor
Author
I've added this as a parameter: |
rkistner
approved these changes
Feb 16, 2026
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
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.
This adds the
powersync_trigger_resyncfunction. It updatesps_bucketsto setlast_applied_op = 0on buckets. This causes the sync client to re-apply all changes the next time it receives a checkpoint-complete message, without throwing any local rows away. And unlike a soft-clear, this also doesn't clear the crud upload queue.This function is mainly useful when migrating raw tables, see this section for details.