Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How can i achieve Optimistic Concurrency?

April 26, 2017achieve Concurrency Optimistic

0

Posted

How can i achieve Optimistic Concurrency?

1 Answer

0

Posted

In this mode container allows multiple transactions operate on same data at the same time. While this mode gives good performace, data integrity would be compromised. – UpdateAllFields With this option container issues an update on all fields, regardless of whether they were modified or not.Given a CMP bean with three fields: “key”, “value1” and “value2”, stored in a table called “MyTable”, the following update will be issued at the end of every transaction, regardless of whether the bean was modified or not: UPDATE MyTable SET (value1 = , value2 =) WHERE key = – UpdateModifiedFields This is the default setting. Issues an update only on the fields that were modified, or suppresses the update altogether if the bean was not modified. With the above bean, if only “value1” was modified,the following tuned update is issued: UPDATE MyTable SET (value1 = ) WHERE key = – VerifyModifiedFields In this mode, the CMP engine issues a tuned update while verifying