[Idea/Request] Add num_event_logs and num_trace_calls Fields to transactions Tables

[MSilb7]

One method I've used to try to filter to "app-like" transactions is if there's either 1 internal transaction (2 traces) or any event logs emitted.

It's super computationally intensive to find transactions that do this (my method is to generate a list of txs in a CTE, versus doing two joins within the main query.

Ideas on how to solve:

1. An "Augmented transactions" table spell and/or add columns to a materialized evms transactions table - Likely a huge drag on spellbook compute/capacity.
2. In ingestion, count how many instances of the tx_hash there are in logs and traces, and add num_event_logs and num_trace_calls colums.
3. Some fancy query magic that makes this easy? Ideally I'd be able to generate / filter on a count

[jeff-dude]

fyi @hawkaa @dsalv @a-monteiro

[hawkaa]

Hi guys! Sorry I never responded in the ticket!

I truly understand the usecase, but we cannot add num_event_logs and num_trace_calls at this time. Adding a field and reprocessing all tables to add that field is currently not a trivial operation for us.

Do you have any options with matviews or spells?