Graduate student in statistics at Duke University. Former dev.to employee. I like to blog about data science on my Medium publication, perplex.city, and on dev.to
awesome stuff. What happens as the time sensitivity of your data increases? perhaps GA enrollment data isn't the best example, but for something like finance or trading, does it make sense to update a view multiple times per second or at that point is it no better than just querying the original DB every time?
Thanks, Walker! :D If you need up-to-the-second results, I'd stay away from a materialized view and go with a regular ol' view and generate results on the fly. In my experience, materialized views are best for things that don't change often.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
awesome stuff. What happens as the time sensitivity of your data increases? perhaps GA enrollment data isn't the best example, but for something like finance or trading, does it make sense to update a view multiple times per second or at that point is it no better than just querying the original DB every time?
Thanks, Walker! :D If you need up-to-the-second results, I'd stay away from a materialized view and go with a regular ol' view and generate results on the fly. In my experience, materialized views are best for things that don't change often.