![]() ![]() User A SOQL for a record without FOR UPDATE statement and has long running transaction.I performed 4 experiments, take a look: Experiment 1 ![]() If I was to implement record locking, I would want to use optimistic locking. Anand claims the record locking is pessimistic, but cbarry9's quote from the unspecified manual is that other processes will wait, suggesting optimistic locking. There is a forum post which is 2.5 years old that as I read it has conflicting information. ![]() The Salesforce Docs are quite bare of any real information. 99 times out of a 100 everything is calculated as expected. The value is being correctly calculated on the grandparent and great grandparent, but on rare occasions for reasons unknown the parent value is not calculated correctly. The code in question is a trigger that rolls up (lookup relationships hence code needed) some numeric values onto a parent, grandparent and great grandparent object. The reason I am investigating the feature is a difficult random bug that has been discovered. I will admit I am quite a novice when it comes to the topic of record locking, and am not sure it is even going to solve my issue. I am looking for some more definitive and in depth information about record locking in Salesforce.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |