-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to rollback transaction when using compose #384
Comments
Yup, I remember you. 😃 I switched the code a while back from It seems like the prudent thing to do is switch that back. |
Yeah, sounds like we should revert #326. I didn't think of transactions at the time. |
Just thow in some idea: would having both |
I think we can just throw the error. I don't think this is something the user needs to concern themselves with. It should just work. I have a fix, I'm just working on writing a test for it. It should be out soon. |
Thanks! |
Is it possible to rollback if I use
compose
and outcome is invalid?Currently
compose
would throw us out of the transaction when outcome is invalid, thus not rolling back.My work around is to have a variation of
compose
, so execution continues.Oh and thanks for the hard work! I met you at lunch in RubyKaigi last month :)
The text was updated successfully, but these errors were encountered: