xpo-devexpress-dot-xpo-dot-xpodefault-9d0aa79e.md
Gets or sets a value which specifies how XPO behaves by default when reloading changed objects (objects with different versions).
Namespace : DevExpress.Xpo
Assembly : DevExpress.Xpo.v25.2.dll
NuGet Package : DevExpress.Xpo
public static OptimisticLockingReadBehavior OptimisticLockingReadBehavior { get; set; }
Public Shared Property OptimisticLockingReadBehavior As OptimisticLockingReadBehavior
| Type | Description |
|---|---|
| OptimisticLockingReadBehavior |
An OptimisticLockingReadBehavior enumeration value which specifies how XPO behaves when reloading changed objects.
|
Available values:
| Name | Description |
|---|---|
| Default |
The default behavior can be changed by setting the XpoDefault.OptimisticLockingReadBehavior property.
| | Ignore |
The changed objects are not reloaded.
| | ReloadObject |
The changed objects are automatically reloaded.
| | Mixed |
If a transaction has been started, the changed objects are not reloaded. Otherwise, the changed objects are automatically reloaded. For example, transaction starts after you modify objects in the session.
| | ThrowException |
An exception is thrown.
| | MergeCollisionIgnore |
When the client-side and database values of a property are different, the client-side value persists. When field-level tracking is disabled (see Session.TrackPropertiesModifications), this value is treated like Mixed.
| | MergeCollisionThrowException |
When the client-side and database values of a property are different, an exception is thrown. When field-level tracking is disabled (see Session.TrackPropertiesModifications), this value is treated like the Mixed.
| | MergeCollisionReload |
When the client-side and database values of a property are different, the database value is reloaded. When field-level tracking is disabled (see Session.TrackPropertiesModifications), this value is treated like Mixed.
|
The default value for XpoDefault.OptimisticLockingReadBehavior is OptimisticLockingReadBehavior.Mixed.
See Also