2 ms·
I try to avoid materialized views when I can due to the problem of keeping them up to date. If I see a materialized view I’d definitely go back to see if I cou
by Lio 2y ago
I try to avoid materialized views when I can due to the problem of keeping them up to date.
If I see a materialized view I’d definitely go back to see if I could eke out any other optimisation in a straight view rather than use it.
With regard to Scenic, I like the way it separates out SQL but I’ve always found how it versions view files with an iteration in the file name a pain.
I wish it had the option to just pick up changes in the source file without needing a migration to bump that version number.
On larger projects it’s easy to run into version number clashes in different pull requests.
- nesarkvechnep 2y agoYou can have multiple small materialised views, which get updated when appropriate and are composed by a regular view. It’s more convenient than a single large materialised view.
- bdcravens 2y agoOn projects I've used it, we're already running scheduled jobs anyways, so another job for refreshing wasn't a problem.