zeekayandHanzo Dev dfb9c57fc3 The page before a cursor is bounded in SQL, beside the LIMIT ...

A client pages a pool's history as "the N trades before this time". The bound
was applied by FilterResults after the database had already taken the newest N,
so every page after the first threw its rows away and came back empty. It sits
in the WHERE now, on the same index the pool does.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-16 12:40:39 -07:00

..

list_never_null_test.go

fix(storage): an empty list is [], not null

2026-08-06 14:03:37 -07:00

poolindex_test.go

The page before a cursor is bounded in SQL, beside the LIMIT

2026-08-16 12:40:39 -07:00

replicate.go

Initial commit: Lux Graph Engine

2026-04-11 13:47:05 -07:00

series_test.go

Give a chart something to draw: a day series over the trades already indexed

2026-08-11 11:17:16 -07:00

store_memory.go

A pool's volume and the protocol's come from one answer

2026-08-14 07:39:56 -07:00

store_sqlite.go

The page before a cursor is bounded in SQL, beside the LIMIT

2026-08-16 12:40:39 -07:00

store_test.go

A pool's trades are its own, not whatever survived the limit

2026-08-13 20:45:05 -07:00

store.go

A supply is whole tokens, and a named row is not a finished one

2026-08-13 15:03:47 -07:00

swapvalue_test.go

Say how many trades were priced

2026-08-11 17:25:07 -07:00

traded_test.go

A pool's volume and the protocol's come from one answer

2026-08-14 07:39:56 -07:00

valuecost_test.go

Say how many trades were priced

2026-08-11 17:25:07 -07:00