blocks|key|1231915|text|当不是无状态工作时(如webservices工作)，你可以尝试悲观锁定；更多信息在这里(尽管是VB示例)：https://web.archive.org/web/1/http://articles.techrepublic%252ecom%252ecom/5100-10878_11-1049842.html|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1231916|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/1/http://articles.techrepublic%252ecom%252ecom/5100-10878_11-1049842.html^0|1H|2P|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

When not working stateless (like webservices work), you could try pessimistic locking; more info here (VB example though): <a href="https://web.archive.org/web/1/http://articles.techrepublic%2ecom%2ecom/5100-10878_11-1049842.html" rel="nofollow noreferrer">https://web.archive.org/web/1/http://articles.techrepublic%2ecom%2ecom/5100-10878_11-1049842.html</a>

blocks|key|1931696|text|您至少需要使用乐观锁定。请看这里：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1931697|Optimistic+Locking|offset|length|1931698|基本上，这意味着您在更新过程中检查所有字段的值。例如，假设您第一次读取记录1时，bar等于0：|1931699|UPDATE+FOO+SET+BAR=1+WHERE+ID=1+AND+BAR=0|code-block|syntax|javascript|1931700|这个想法是，如果记录发生变化，更新将失败。这将解决您的问题。|1931701|entityMap|0|LINK|mutability|MUTABLE|url|http://davidhayden.com/blog/dave/archive/2005/10/05/2503.aspx^0|0|0|I|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

You need to use, at the very least, optimistic locking. See here:

<a href="http://davidhayden.com/blog/dave/archive/2005/10/05/2503.aspx" rel="nofollow noreferrer">Optimistic Locking</a>

Basically, this says that you check the values of all fields during the update. So you say, for example assuming when you first read record 1, bar was equal to 0:

<pre><code>UPDATE FOO SET BAR=1 WHERE ID=1 AND BAR=0
</code></pre>

The idea is, if the record changes, the update will fail. This will solve your problem.

blocks|key|1229057|text|我还发现乐观并发是最好的方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1229058|应该只决定使用哪个数据库字段作为更新失败的标准。这取决于您情况，但有一种通用的方法来实现它。我个人使用MS+SQL+Server，因此更喜欢在数据库的所有表中插入不可为空的rowversion字段(别名timestamp)+(每个表一个字段)。因此，表中的每一行都将有一个"rowversion“，它将自动更新，当有人更新行的字段时，就会自动更新。因此，您应该只使用此字段作为更新失败的标准。另请参阅我以前的答案Concurrency+handling+of+Sql+transactrion，了解关闭信息。|CODE|1229059|更新了：因为您使用SqlDataAdapter访问数据库，所以您也可以对此链接感兴趣：|1229060|https://web.archive.org/web/1/http://articles.techrepublic%252ecom%252ecom/5100-10878_11-1050108.html|1229061|在下一个页面上只需搜索DataRowVersion|1229062|http://msdn.microsoft.com/en-us/library/ww3k31w0(VS.71).aspx、http://msdn.microsoft.com/en-us/library/bbw6zyha(VS.80).aspx、http://msdn.microsoft.com/en-us/library/ms971491.aspx、http://msdn.microsoft.com/en-us/magazine/cc163908.aspx|1229063|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2658443/concurrency-handling/2663654#2663654|1|https://web.archive.org/web/1/http://articles.techrepublic%252ecom%252ecom/5100-10878_11-1050108.html|2|http://msdn.microsoft.com/en-us/library/ww3k31w0(VS.71).aspx)|3|http://msdn.microsoft.com/en-us/library/bbw6zyha(VS.80).aspx)|4|http://msdn.microsoft.com/en-us/library/ms971491.aspx|5|http://msdn.microsoft.com/en-us/magazine/cc163908.aspx^0|4|4|0|2E|A|2T|9|3T|A|5Q|14|0|0|0|3|9|E|0|0|2P|1|0|B|E|0|0|1O|2|1P|1O|3|3E|1H|4|4W|1I|5|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1B|8|@$9|1C|A|1D|B|H]|$9|1E|A|1F|B|H]|$9|1G|A|1H|B|H]]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|I|3|J|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|H]]|D|@]|E|$]]|$1|K|3|L|5|6|7|1Q|8|@]|D|@$9|1R|A|1S|1|1T]]|E|$]]|$1|M|3|N|5|6|7|1U|8|@$9|1V|A|1W|B|H]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1X|8|@]|D|@$9|1Y|A|1Z|1|20]|$9|21|A|22|1|23]|$9|24|A|25|1|26]|$9|27|A|28|1|29]]|E|$]]|$1|Q|3|-4|5|6|7|2A|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]|10|$5|T|U|V|E|$W|11]]|12|$5|T|U|V|E|$W|13]]|14|$5|T|U|V|E|$W|15]]|16|$5|T|U|V|E|$W|17]]]]

I also find Optimistic Concurrency as the best way.

One should only decide which database field use as a criteria of update fails. It's depend on your situation, but there are one universal way to implement this. I personally use MS SQL Server and so prefer inserting not nullable <code>rowversion</code> fields (alias <code>timestamp</code>) in all tables of database (one field per table). So every row in your table will have a "<code>rowversion</code>" which will be updated automatically is somebody update a field of the row. So you just should use this field as a criteria of update fails. See also my old answer <a href="https://stackoverflow.com/questions/2658443/concurrency-handling/2663654#2663654">Concurrency handling of Sql transactrion</a> for the close information.

UPDATED: Because you use <code>SqlDataAdapter</code> to access the database, this links can be also interesting for you:

<a href="https://web.archive.org/web/1/http://articles.techrepublic%2ecom%2ecom/5100-10878_11-1050108.html" rel="nofollow noreferrer">https://web.archive.org/web/1/http://articles.techrepublic%2ecom%2ecom/5100-10878_11-1050108.html</a>

and on the next one just search for <code>DataRowVersion</code>:

<a href="http://msdn.microsoft.com/en-us/library/ww3k31w0(VS.71).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ww3k31w0(VS.71).aspx</a>,
<a href="http://msdn.microsoft.com/en-us/library/bbw6zyha(VS.80).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/bbw6zyha(VS.80).aspx</a>,
<a href="http://msdn.microsoft.com/en-us/library/ms971491.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ms971491.aspx</a>,
<a href="http://msdn.microsoft.com/en-us/magazine/cc163908.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/magazine/cc163908.aspx</a>

blocks|key|1931782|text|我遇到了和你类似的情况。它涉及一个SqlDataAdapter、一个连接到它的SqlCommandBuilder和一个DataTable对象。我所做的更改始终保存失败，但没有给出错误。事实证明，DataTable对象中的一列命名错误。一旦我纠正了它，它就开始完美地工作了。我仍然不知道为什么这不会引发错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1931783|entityMap^0|H|E|13|H|1N|9|2P|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I ran into a situation similar to yours. It involved an <code>SqlDataAdapter</code>, an <code>SqlCommandBuilder</code> connected to it, and a <code>DataTable</code> object. Changes I made consistently failed to save, but giving no error. It turned out that one of the columns in the <code>DataTable</code> object was misnamed. Once I corrected it, it started working perfectly. I still have no idea why this didn't raise an error.

If userA deleted OrderA while userB is modifying OrderA, then userB saves OrderA then there is no order in the database to be updated. My problem is there is no error! The SqlDataAdapter.Update succeeds and returns a "1" indicating a record was modified when this is not true. Does anybody know how this is supposed to work, thanks.

Database concurrency issue in .NET application

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如果userA在userB修改OrderA时删除了OrderA，则userB将保存OrderA，则数据库中没有要更新的订单。我的问题是没有错误！SqlDataAdapter.Update成功并返回"1“，表示记录已被修改，但这不是真的。有谁知道这是怎么回事吗，谢谢。

问.NET应用程序中的数据库并发问题
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET应用程序中的数据库并发问题EN