Views and Materialized Views

Queries that join multiple tables tend to get reused. A dashboard needs artist stats, a report needs track details, an API endpoint needs user activity summaries. Writing the same five-table join in every place is tedious and error-prone.

Views solve this by storing a query definition that you can reference like a table. Materialized views take it further by storing the query's results on disk, so expensive aggregations don't re-run on every read.