-
Notifications
You must be signed in to change notification settings - Fork 11
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
Transaction strategy fails with Sequel #2
Comments
I just ran into the same problem. In my case it's because Thus I simply had to initialise the connection to my database before calling |
Ran into this as well. Updated implementation and it is working as expected:
|
@jeffvincent It sounds like maybe this situation could be addressed in the README? What do you think? |
Totally agree! tbh, I wasn't confident enough in my solution. Was expecting to hear about all kinds of terrible externalities I caused by doing things this way :) An update to the README would certainly help future-me. I'm happy to create PR, if you think that's a good idea. |
@jeffvincent Yes, please do! |
Backtrace:
Multiple threads being used
The text was updated successfully, but these errors were encountered: