Sql.transaction is unnecessary
See original GitHub issueIf we create a transaction using connection.BeginTransaction(), then the connection is attached to the transaction. Therefore, we can just use Sql.existingConnection in every sql statements afterward. Moreover, we can remove Transaction from ExecutionTarget.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Is a bad practice to create a transaction always? [duplicate]
You should never have a transaction unless you are changing data in the database. Read uncommitted isolation level is also a very poor...
Read more >A Primer on SQL Transactions | Linode Docs
SQL transactions help maintain database integrity. This guide outlines some transaction benefits and ... Why are SQL Transactions Necessary?
Read more >Remove Unnecessary SQL Server Transaction Log Files
Learn how to determine SQL Server Transaction Log usage and how to remove unnecessary SQL Server transaction log files.
Read more >Why would you want to name a transaction?
transaction_name is always case sensitive, even when the instance of SQL Server is not case sensitive. The full list is: A Mess of...
Read more >Deferred Transactions (SQL Server)
In SQL Server Enterprise, a corrupted transaction can become deferred if data required by rollback (undo) is offline during database startup. A ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I agree that
Sql.transactionis redundant. I think we can deprecate it (not entirely remove it) in the next major version but I will probably need to add a proper documentation website to showcase the different scenarios and how to properly work with transactions.Removed as of v4.0