linq - Insert Queries Can Only Cause Concurrency Issues With Select Queries? -
It is just for my own understanding that how the issues of interaction work, I have an assembly statement that Runs as a select query at a time. If the insert statement occurs when the selection query is still running, will the selection query show a dispute because the number of rows that have been selected has changed?
Or is it that interactive conflicts can only occur when the rows are edited, the insert statement is completely harmless (in the context of concurrency conflict)?
Wikipedia article is very good for this:
But there is always data on concurrency issues which is using the transaction from another transaction.
So let's say I get the top 100 rows from the database. Someone else makes a change to 5 lines. Then I try to change line 5 based on this reading.
Or an inclusion case
Say I will pull all the children in a school, and to know how many names start with A. Then someone adds 10 more children starting with A. This is a concurrency issue.
You get bad things from being included to something that you were not expecting to be in the database.
For example:
John has an outstanding balance of $ 1000, he comes online to pay his bill, during which a transaction is the time of The reason is that he has to pay $ 100 (inclusive) ($ 1100 total). He pays his $ 1000 full, which sets all his outstanding balance to 0 (he pays all those we meet so that we say that Aihir sets everything just 0). This $ 100 transaction is now actually cleaned up without paying.
Comments
Post a Comment