Show monthly/task totals on tracker show page #183

edwardloveall commented 2026年07月08日 22:41:06 +02:00

TrackerTotals is similar to RecentTaskLogTotals. It sums and groups task log
totals by month and task, instead of RecentTaskLogTotals which does it by
month and food taxonomy.

For styling, I reused the sites table because it looks similar to the list-table
styles, but can work better with variable columns. Because we're using tasks as
the columns, these tables can get large. So I also wrapped the table in a
scrolling container. There's a nice side benefit that we get that we can make a
minimum column width (only if table-layout: auto;) so that they don't get
squished too much.

Screen Shot 2026年07月08日 at 16.40.14-fullpage

`TrackerTotals` is similar to `RecentTaskLogTotals`. It sums and groups task log totals by month and task, instead of `RecentTaskLogTotals` which does it by month and food taxonomy. For styling, I reused the sites table because it looks similar to the list-table styles, but can work better with variable columns. Because we're using tasks as the columns, these tables can get _large_. So I also wrapped the table in a scrolling container. There's a nice side benefit that we get that we can make a minimum column width (only if `table-layout: auto;`) so that they don't get squished too much. 

edwardloveall commented 2026年07月08日 22:53:11 +02:00

@thetizzo wrote in #183 (comment):

The idea behind using DB views instead of tables is because these are somewhat transient datasets that would need to have some mechanism to keep them up to date in a normal table and using views removes the need for building an updating system?

Yes, and also the views are:

• a nice abstraction
• sooooo much faster to calculate than anything I could put together with ActiveRecord

The amount of complex grouping and summing logic would be untenable for any AR query. I did a similar thing in #178 where the old ruby version was fine speed-wise, until I switched a new data layout which AR + Ruby could not calculate in any reasonable time.

@thetizzo wrote in https://codeberg.org/rootable/tomato/pulls/183#issuecomment-18827540: > The idea behind using DB views instead of tables is because these are somewhat transient datasets that would need to have some mechanism to keep them up to date in a normal table and using views removes the need for building an updating system? Yes, and also the views are: - a nice abstraction - sooooo much faster to calculate than anything I could put together with ActiveRecord The amount of complex grouping and summing logic would be untenable for any AR query. I did a similar thing in https://codeberg.org/rootable/tomato/pulls/178 where the old ruby version was fine speed-wise, until I switched a new data layout which AR + Ruby could not calculate in any reasonable time.