expose db state to updates
laforge49 opened this issue · comments
Updates to calf and yearling should work with the db state, not the app map. Further, the api for queries should work with db state rather than the opts map. This does 2 things:
- The api for queries and updates are unified, and
- The query api (like get transaction count) now work with past state.
Once this is done, it will be trivial to drop the dynamic variables from yearling.
Calf now exposes db-state. See https://github.com/laforge49/aatree/wiki/Calf
Yearling now exposes db-state. See https://github.com/laforge49/aatree/wiki/Yearling
Updated wiki: https://github.com/laforge49/aatree/wiki/Db-Agent
Replaced get-sorted-map with an enhanced db-get-state
Dropped db-transaction-count.