Thrown to signal that the lock constraints of the locking semantics used was violated.
For a list of all members of this type, see LockViolationException Members.
For OptimisticLockingSemantics a LockViolationException signals that the Object could not be commited because the server version of the object has been changed. For PessimisticLockingSemantics a LockViolationException signals that the Object could not be locked by a call to Context.Lock because the object is already exclusively locked in an other Context.
Assembly: TechTalk.Genome (in TechTalk.Genome.dll)
Editions: Professional, Evaluation, Express
Database Platforms: Microsoft SQL Server 2000, Microsoft SQL Server 2005, Orcale 9i Release 2, Oracle 10g Release 2