是否应该有读取查询的事务?

Should there be a Transaction for Read Queries?(是否应该有读取查询的事务?)
本文介绍了是否应该有读取查询的事务?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我一直在读到一些开发人员/dbas 建议在所有数据库调用中使用事务,甚至是只读调用.虽然我理解在事务中插入/更新,但在事务中读取有什么好处?

I've been reading that some devs/dbas recommend using transactions in all database calls, even read-only calls. While I understand inserting/updating within a transaction what is the benefit of reading within a transaction?

推荐答案

因此您可以获得一致的数据库视图.想象一下,您有两个相互链接的表,但出于某种原因,您在伪代码中执行了 2 个选择...:

So you get a consistent view of the database. Imagine you have two tables that link to each other, but for some reason you do 2 selects... in pseuodocode:

myRows = query(SELECT * FROM A)
moreRows = query(SELECT * FROM B WHERE a_id IN myRows[id])

如果在两次查询之间,有人更改了 B 以删除一些行,您就会遇到问题.

If between the two queries, someone changes B to delete some rows, you're going to have a problem.

这篇关于是否应该有读取查询的事务?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

Execute complex raw SQL query in EF6(在EF6中执行复杂的原始SQL查询)
SSIS: Model design issue causing duplications - can two fact tables be connected?(SSIS:模型设计问题导致重复-两个事实表可以连接吗?)
SQL to Generate Periodic Snapshots from Transactions Table(用于从事务表生成定期快照的SQL)
SQL Server Graph Database - shortest path using multiple edge types(SQL Server图形数据库-使用多种边类型的最短路径)
Invalid column name when using EF Core filtered includes(使用EF核心过滤包括时无效的列名)
How should make faster SQL Server filtering procedure with many parameters(如何让多参数的SQL Server过滤程序更快)