Concurrency Checking


Author
Message
StrataFrame Team
S
StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)StrataFrame Developer (6.5K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
Actually, the documentation didn't change with the last update, but the StrataFrame proprietary concurrency was removed from the last version. It was inefficient and wasn't as fast as it should have been. It has been replaced with the GetServerValuesOnConcurrencyException property. So, if you're using the timestamp concurrency, and there is a concurrency exception, the DataLayer will retrieve the server values (so you can compare them and re-save the row) when you get a concurrency exception.
Larry Caylor
Larry Caylor
StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)StrataFrame VIP (1.8K reputation)
Group: Awaiting Activation
Posts: 592, Visits: 3.7K
Does the UpdateConcurrencyType on an object at the form level override the AutoHandleCollisions setting? In other words if UpdateConcurrencyType is set to OptimisticTimeStamp for an object on a form and AutoHandleCollisions is set to true, which type of concurrency is enforced on the object, OptimisticTimeStamp or StrataFrame Proprietary?
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search