-
-
Notifications
You must be signed in to change notification settings - Fork 120
Add ability to control transactions #520
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #520 +/- ##
==========================================
+ Coverage 43.48% 46.70% +3.21%
==========================================
Files 109 98 -11
Lines 6057 5548 -509
==========================================
- Hits 2634 2591 -43
+ Misses 3423 2957 -466
Flags with carried forward coverage won't be shown. Click here to find out more. |
gwynne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but can we add a documentation comment on the protocol itself warning about the caveats of using it?
|
Yes adding docs would actually be useful 🤦 |
gwynne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of grammar and style nits, but otherwise LGTM
Co-authored-by: Gwynne Raskind <gwynne@vapor.codes>
|
These changes are now available in 1.31.0 |
Adds the ability to control starting, committing and rolling back transactions outside of the main Fluent API. This could be used for setting up tests or when you need more control over a transaction.
Introduces a new
TransactionControlDatabaseprotocol to implement, that conforms toDatabase