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

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.

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