Skip to main content

Module store

Module store 

Source
Expand description

Persistence of the combat event log in Postgres, shared by every instance of the service.

Structs§

ListFilter
Which combats to list.
Notice
Payload of a notification on CHANNEL: the combat’s log now reaches seq. Events themselves are read from the table, which keeps notifications small and lets a listener that missed some catch up.
Store
Combats, their logs and planned encounters, in Postgres.

Constants§

CHANNEL
The Postgres channel on which every appended event is announced, so all instances can push it to their connected clients.

Functions§

now
The current time at the precision Postgres stores, so an event read back from the log equals the one that was written.

Type Aliases§

Tx
A transaction on the combats’ database.