How ADO.NET handles concurrent updates
This article mainly introduces ADO.NET how to deal with concurrent updates, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.
Set the concurrency mode
Entity Framework implements an optimistic concurrency pattern (Optimistic Concurrency Model). By default, ADO.NET data does not check for concurrency when entity update data is submitted to the database. For high-frequency concurrency properties, you need to set the concurrency mode of the property to Fixed.
These attributes will be added to the WHERE clause section of the T-SQL script, and the ADO.NET data is used to compare the values on the client side with those on the database side, sample code:
Public void UpdateProduct ()
{
Product product = context.Product.FirstOrDefault (p = > p.ProductID = = 1004)
If (product! = null)
{
Product.Color = "White"
Product.StandardCost = 200
Product.ListPrice = 250
}
Context.SaveChanges ()
}
Thank you for reading this article carefully. I hope the article "how to deal with concurrent updates in ADO.NET" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!
