Optimize queries involving (tx-ids) and (tx-data) #219

Open
opened 2020-08-06 16:56:51 +00:00 by gburd · 0 comments
gburd commented 2020-08-06 16:56:51 +00:00 (Migrated from github.com)

#640 implements the tx-* log API, and one of the tests uses both (tx-ids) and (tx-data). This leads to two walks of the transactions table, which could be coalesced into one walk. This is a specific case of a more general optimization pattern where-by known combinations of functions and binding forms can be transformed.

#640 implements the `tx-*` log API, and one of the tests uses both `(tx-ids)` and `(tx-data)`. This leads to two walks of the `transactions` table, which could be coalesced into one walk. This is a specific case of a more general optimization pattern where-by known combinations of functions and binding forms can be transformed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: greg/mentat#219
No description provided.