Support tracking update hooks #120
Merged
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 support for tracking update hooks in the core extension, making it easier for us to build SDKs ontop of libraries that may not support update hooks natively. Another benefit is that, since the hook is installed in Rust, there's not as much of an interop cost from C -> the Rust hook compared to other languages.
Update hooks are optional and registered by calling
powersync_update_hook('install')
. After that call, we track updated table names after a transaction completes into a set. Callingpowersync_update_hook('get')
will clear that set and return affected table names.There's no way to unregister update hooks manually - instead, we rely on the
xDestroy
callback forpowersync_update_hook
to clear resources when the database is closing.