Table of Contents

Enum ProjectionRefoldOutcome

Namespace
Excalibur.EventSourcing
Assembly
Excalibur.EventSourcing.Abstractions.dll

What a re-fold did — rewriting a projection's state at the position it already holds.

public enum ProjectionRefoldOutcome

Fields

Applied = 0

The state was rewritten. The position is unchanged.

RequiresRebuild = 3

The row's position cannot be matched, so the state's relationship to the stream is unknown and no re-fold can be placed against it. The projection must be rebuilt.

Terminal: retrying is futile because nothing about the row will change on its own. The caller escalates rather than looping.

Superseded = 1

The stored position is not the one the caller named, so nothing was written.

For a re-fold this is NEVER settled, whatever position the store holds. See ProjectionRefoldResult.

Vanished = 2

The projection does not exist, and a re-fold MUST NOT create it.

Deletion is how erasure removes personal data. Re-creating the row from a replay would reinstate the data the deletion removed, so a vanished row is left alone and the caller stops.

Remarks

Same member names as ProjectionAdvanceOutcome on purpose: they describe the same store decisions. They are a separate enum because they are consumed by a different settle rule, and ProjectionRefoldResult exists to make mixing the two a compile error rather than a silent compliance failure. See that type's remarks.