perf: bound the banking list RPCs — pagination for listBankTransactions / listBankAccounts #55
Labels
No labels
bug
enhancement
pr-split
question
security
transaction-matcher
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
momsse/octant#55
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The banking read RPCs (
listBankTransactions,listBankAccounts) query their full read tables with noLIMIT/cursor (e.g.SELECT … FROM read.bank_transactions ORDER BY value_date ASC). A real account with years of history loads every row into one RPC response and decodes it client-side; the backoffice list atom iskeepAlive, so the snapshot stays resident.Read-side analogue of #52 (reconciliation list). Proposed: introduce pagination params on the banking list RPCs (
payload: Schema.Void→ aPaginationParamspayload) and a cursor/limit in the query adapters; the/bankingpage passes page/cursor through. Doing the RPC-schema part early avoids a breaking change later.Surfaced in the #41 banking read-surface review (PR #119).