asp.net - Time Stamp in DBML is solving concurrency issues...why? -


We use LINQ our ASP to run the database. Questions and commands We have been having unified problems on the updates of tables in which we update the value of a date area, especially if two users click on a button at the exact same time and If the code tries to update a date field in the database, then the underlying optimistic concurrency fails to do its job and throws users an A Dispute

If we go to dbml and set the field's time stamp to the right property and run the unit tests then this is a strange part. Just works fine ... no clear locks are needed

We would like to understand it a bit more before implementing it in the whole system. Does anybody understand why it works?

Without knowing the details of my system, I suppose that because the SQL Server DATETIME resolution 3 is the most Good MS, giving a high likelihood of conflict. TIMESTAMP is a counter in desquise and can not fight.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -