This question is locked. New answers and comments are not allowed.
Good day. May I have some links showing how to deal with concurrency problems? yes i have read a couple of articles but it doest show where to put this and that when and how to use this and that. can we have a sample application that uses all of the concurrency features provided by Opneaccess?
Added: Also how can i append the version number of a record that i wanted to update? because what the forums says is "OpenAccess ORM uses this method by default for optimistic concurrency control. It uses a version column to detect concurrent updates. The version number is incremented on every update and the previous version number is included in the where clause. This is the fastest and safest optimistic concurrency control mode." I want to try the version optimistic concurrency control. can the telerik team explain where, when and how we can accomplish this? pls provide as a sample project. tnx
Added: I had found this thread http://www.telerik.com/help/openaccess-orm/concurrency-control-optimistic.html it says on the Lost Update Section that scope2 will product an error. But when i tried to replicate it by setting the trasaction properties of the scope into no_lost_update my second application still continue to commits and no OptimisticVerificationException was thrown. I think this is what we needed in our current project that is to detect if another user were about to update an updated data then prompt the user 2 that another user already updated the data and if user 2 wants to overwrite it displaying all of the modifed data made by the first user againts the second user. Can you provide us a sample Lost Update Section project pls? ive been waiting for a reply for two days and still no luck.. tnx
Added: Also how can i append the version number of a record that i wanted to update? because what the forums says is "OpenAccess ORM uses this method by default for optimistic concurrency control. It uses a version column to detect concurrent updates. The version number is incremented on every update and the previous version number is included in the where clause. This is the fastest and safest optimistic concurrency control mode." I want to try the version optimistic concurrency control. can the telerik team explain where, when and how we can accomplish this? pls provide as a sample project. tnx
Added: I had found this thread http://www.telerik.com/help/openaccess-orm/concurrency-control-optimistic.html it says on the Lost Update Section that scope2 will product an error. But when i tried to replicate it by setting the trasaction properties of the scope into no_lost_update my second application still continue to commits and no OptimisticVerificationException was thrown. I think this is what we needed in our current project that is to detect if another user were about to update an updated data then prompt the user 2 that another user already updated the data and if user 2 wants to overwrite it displaying all of the modifed data made by the first user againts the second user. Can you provide us a sample Lost Update Section project pls? ive been waiting for a reply for two days and still no luck.. tnx
1 Answer, 1 is accepted
0
Hello Joebet,
Regards,
Damyan Bogoev
the Telerik team
Regards,
Damyan Bogoev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items