Skip to main content

XPClassInfo.OptimisticLockingReadBehavior Property

Specifies how XPO behaves when reloading a changed object.

Namespace: DevExpress.Xpo.Metadata

Assembly: DevExpress.Xpo.v24.2.dll

NuGet Package: DevExpress.Xpo

#Declaration

public OptimisticLockingReadBehavior OptimisticLockingReadBehavior { get; }

#Property Value

Type Description
OptimisticLockingReadBehavior

An OptimisticLockingReadBehavior enumeration value that specifies how XPO behaves when reloading changed objects (objects with different versions).

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.

#Remarks

For details, see the Session.OptimisticLockingReadBehavior topic.

See Also