Namespace Opossum.Exceptions
Classes
- AppendConditionFailedException
Exception thrown when an append condition fails during event appending. This is the single exception type that represents an optimistic concurrency conflict as defined by the DCB specification.
ConcurrencyException is a subclass of this exception and is thrown by the file-system layer for internal ledger-level races. Callers should always catch AppendConditionFailedException — this covers both cases.
- ConcurrencyException
Exception thrown by the file-system event store for internal ledger-level concurrency conflicts (e.g. a stale AfterSequencePosition check).
This is a subclass of AppendConditionFailedException. Callers should catch AppendConditionFailedException rather than this type directly, unless they need to inspect the ExpectedSequence / ActualSequence properties for diagnostic purposes.
- ContextNotFoundException
Exception thrown when attempting to access a bounded context that doesn't exist or hasn't been configured
- EventNotFoundException
Exception thrown when expected events cannot be found in the event store
- EventStoreException
Base exception class for all Opossum Event Store exceptions
- InvalidQueryException
Exception thrown when a query is invalid or malformed