Skip to main content

Module row_placement

Module row_placement 

Source
Expand description

Placing scan frontiers in public ledger coordinates.

Every list and subscription frame carries its resume point as a LedgerPoint (Watermark.cursor_position). Cursors name the same boundaries by tx_seq, which stays private, and carry the public position of their coordinate (Position::public_position), so a server places any cursor without a read. A scan frontier is placed by the index row (checkpoint and position in it) of one transaction the scan already reads: RowPlacement says which one, and how its row places the boundary. Checkpoint boundaries, the request’s own fields, and items need no read.

Structs§

RowPlacement
Which transaction’s index row places a transaction- or event-lane boundary, and how. A scan boundary is placed by the transaction on its covered side: ascending, the last transaction before it (or the transaction it lies inside); descending, the transaction right after it. That transaction lies in the scanned, indexed part of the ledger whenever the scan reached the boundary, including a boundary at the indexed tip.