Is this like materialized views, but in the application instead of the database?
Is that how materialized views work? I haven’t touched them for years.
I’m not sure about the implementation, it just sounded to me like the problem they’re addressing is very similar.
Hi. I added some FAQ to the readme where there is also an answer to the difference between materialized views.
This gives a two-sentence idea of how a materialized view is created and refreshed.
Thanks! Sounds like a materialized view, at least for this version of postgresql is like a table copy, that can later be refreshed. If so, I don’t think this algorithm is similar at all.