[jeremydmiller]

Closes #5723.

DocumentSessionBase.ProjectionStorage.StoreProjection cast both values through int before assigning them to the long Revision:

r.Revision = scope == AggregationScope.SingleStream ? (int)lastEvent.Version : (int)lastEvent.Sequence;

A multi-stream projection's revision is the global seq_id, so once that passed int.MaxValue the revision wrapped negative in memory. That defeated #4526's advice to put such documents on ILongVersioned with a bigint column. Both casts are gone. An int IRevisioned member is still narrowed where the value is written back to the document; the #4614 tests pass, 9/9.

Test

EventSourcingTests.Bugs.Bug_5723_multi_stream_long_revision restarts mt_events_sequence past int.MaxValue and runs an async MultiStreamProjection over an ILongVersioned document through the continuous daemon:

• master: Version = -2147483549;
• here: 2147483747.

Noticed, not changed

An inline multi-stream projection does not go through StoreProjection at all. JasperFx's ApplyInline calls Store(), which auto-increments the revision instead of taking it from the event. So an inline projection's revision is a write count, not the sequence. It is pre-existing, and probably intended, but worth knowing if anyone reads ILongVersioned.Version as a sequence on an inline projection.

🤖 Generated with Claude Code