> Better, mark this view (or particular rows if it's not too > expensive) as "dirty" and recompute it only on access, you > may spare few cycles...
That sort of depends on what you're going for. Typically materialized views are used for summarizations of hypercubes for OLAP systems (data marts / data warehouses). You want access to these views to be as fast as possible as they're often accessed by interactive programs (reporting UI). Recomputing when the change happens is desirable because slowing down that change just a tiny bit generally won't be a huge deal, as the thing doing the change is going to be your ETL process which is generally non-interactive anyway. -JF -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
