Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Like automatically refreshing materialized views, by which I mean when a base table is changed, the engine uses the definition of the materialized view to run triggers to update materialized view.


This is related to default implementation details, this behavior can be achieved using trigger/materialized view on PostgreSQL as well.


My entire point is that I shouldn't have to write the triggers myself. PostgreSQL figures out the triggers from my definition of the materialized view.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: