Victor Navarro(@vimtor):every product i've worked on ends up with 1–2 tables so large you need rollups functional indexes only get you so far, and triggers are clunky to maintain. you always end up adding some async work (events, cron jobs, etc.) i'm still surprised more databases don't handle this natively. all i want is a materialized view that updates as rows are inserted, without a full refresh i guess postgres has pg_ivm, but i haven't found an equivalent for mysql. there's probably a good reason why this isn't more common i'm not in the "db should do everything" camp, but the lack of a good abstraction for this still boggles my mind @BenjDicken any thoughts?

2026.09.17 12:29

every product i've worked on ends up with 1–2 tables so large you need rollups functional indexes only get you so far, and triggers are clunky to maintain. you always end up adding some async work (events, cron jobs, etc.) i'm still surprised more databases don't handle this natively. all i want is a materialized view that updates as rows are inserted, without a full refresh i guess postgres has pg_ivm, but i haven't found an equivalent for mysql. there's probably a good reason why this isn't more common i'm not in the "db should do everything" camp, but the lack of a good abstraction for this still boggles my mind @BenjDicken any thoughts?