Rotorsoft / act-root / 33339638071

100%

push

github

fix(act-pg): exclude the boundary event from created_after (#1603)

Postgres stores `created` at microsecond resolution but hands back a JS
Date, which carries milliseconds. A row stamped ...976999 reads back as
...976, so `created > '...976'` compared the row against its own
timestamp and returned it. InMemory and SQLite both exclude it, so
Postgres was the odd one out, and the documented "scan since last time"
pattern re-delivered the boundary event there and nowhere else. With a
limit it returned the wrong event rather than one extra.

Millisecond is the resolution the contract is expressed in, since that is
all a Date carries, so strictly-after means "at least the next
millisecond". Advancing the bound rather than truncating the column fixes
rows already written at microsecond precision, needs no table rewrite on
an events table, and keeps the comparison a plain range scan on
(created, id).

The store TCK gains the case that would have caught it: both bounds must
exclude the event they are pinned to. Its existing window case is built
as `ts ± 60_000`, so no bound ever landed on an event's own timestamp.
Verified the new case fails on Postgres without this fix and passes on
InMemory and SQLite unchanged.

Closes #1595


Claude-Session: https://claude.ai/code/session_014Vfpx1bDy3t57oHBynvNPF

Co-authored-by: rotorsoft <rotorsoft@outlook.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

4332 of 4332 branches covered (100.0%)

Branch coverage included in aggregate %.

10 of 10 new or added lines in 2 files covered. (100.0%)

9302 of 9302 relevant lines covered (100.0%)

1178.88 hits per line