The comparison you see in the WHERE
clause of the SQL
statement is done because the concurrency control strategy you have for the persistent type mapped to table T
is different from "version", "backend" or "timestamp". The concurrency control strategy determines exactly what properties are compared for conflicts during updates and the default one is "changed". There are a few articles in our documentation that although scattered shed some light on the topic with the concurrency modes. You can find information about the "none", "version", "changed" and "timestamp" concurrency modes on this page
. Additional information regarding the "backend" mode can be found here
. The topics are still under the classic wizards sections, however, we are in a process of updating our documentation and you can expect to see numerous improvements in the near future.
The "version" concurrency strategy enables you to select a single property that will be used to resolve conflicts during updates and will remove the need for comparison of multiple columns in the database. The version field should be int or long and its value is automatically calculated by OpenAccess on inserts and updates. To view or change the concurrency control mode you can select a persistent type in the designer, press F4 and look at the Concurrency Mode
If you have further questions, do not hesitate to contact us back.
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?
Telerik Public Issue Tracking
system and vote to affect the priority of the items