我什么时候应该使用 SQLTransaction
什么时候使用 SQLTransaction 合适？
我将它们用于所有我的 INSERT、UPDATE 和 DELETE 语句。
这是正确的用法还是我做得有点过分了？
What is the appropriate time to use a SQLTransaction?
I use them for all of my INSERT, UPDATE and DELETE statements.
Is this the correct usage or am I doing a bit of overkill?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
当您希望以原子方式处理一系列语句时，请使用事务 - 也就是说，它们要么全部成功并提交，要么全部回滚。
由于简单的语句已经是原子的，因此您不需要围绕每个单独的语句显式创建事务。
Use a transaction when you want a series of statements to be treated atomically - that is either they all succeed and are committed, or they are all rolled back.
Since simple statements are already atomic you don't need to explicitly create a transaction around each and every individual statement.
如果您的命令仅发出一次，而不是一组，那么它可能是多余的。事务用于将 sql 命令分组在一起，该组必须所有成员都成功，或者根本没有成员成功。
http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29
If your commands are only single issued, and not a group, then it is probably overkill. Transactions are used to group sql commands together, a group that must have all members succeed, or none at all.
http://en.wikipedia.org/wiki/Atomicity_%28database_systems%29
仅当您计划执行多个语句时才需要事务，并且计划在某处发生错误时回滚由语句导致的所有数据更改。不需要包装单个更新/删除语句。如果单个命令发生错误，只需在前端代码中捕获并处理错误即可。
You only need a transaction if you plan to do multiple statements, and plan to rollback all of the data changes that resulted from the statements if an error somewhere down the line occurs. Wrapping single update/delete statements is not needed. If an error occurs with a single command, simply catch and handle the error in your front-end code.