expose sync rollback as a private api method #1230
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
fredr
added a commit
to encoredev/encore
that referenced
this pull request
Apr 9, 2025
Adds support for transactions in runtimes/core and runtimes/js We should probably merge encoredev/rust-postgres#1 and update Cargo.toml again. (suggested that change upstream as well sfackler/rust-postgres#1230)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Don't know if this is the correct approach, I just saw that sync close was exposed the same way.
It would be useful to have this exposed so that one can implement their own transaction type with a drop implementation that rolls back.
The reason I would like to implement my own transaction type is that I want to expose it to nodejs via napi-rs, and it is not possible to share things that have a lifetime over that boundary.