materialized-views

I'm trying to optimize a query which uses a view in MySQL 5.1. It seems that even if I select 1 column from the view it always does a full table scan. Is that the expected behaviour? The view is just a SELECT "All Columns From These Tables - NOT *" for the tables I have specified in the first query below. This is my explain output from when i select the indexed column PromotionID from the query which makes up the view. As you can see it is vastly different from the output on the view. EXPLAIN SELECT pb.PromotionID FROM PromotionBase pb INNER JOIN PromotionCart pct ON pb.PromotionID = pct

What is the difference between Views and Materialized Views in Oracle? dacracot Materialized views are disk based and are updated periodically based upon the query definition. Views are virtual only and run the query definition each time they are accessed. Mike Williamson Views They evaluate the data in the tables underlying the view definition at the time the view is queried . It is a logical view of your tables, with no data stored anywhere else. The upside of a view is that it will always return the latest data to you . The downside of a view is that its performance depends on how good a

I found a posting on the MySQL forums from 2005 , but nothing more recent than that. Based on that, it's not possible. But a lot can change in 3-4 years. What I'm looking for is a way to have an index over a view but have the table that is viewed remain unindexed. Indexing hurts the writing process and this table is written to quite frequently (to the point where indexing slows everything to a crawl). However, this lack of an index makes my queries painfully slow. I don't think MySQL supports materialized views which is what you would need, but it wouldn't help you in this situation anyway.

I have a materialized view on a PostgreSQL 9.3 database which seldom changes (about twice a day). But when it does, I'd like to update its data promptly. Here is what I was thinking about so far: There is a materialized view mat_view which gets its data from tables table1 and table2 using some join statement. Whenever something in table1 or table2 changes, I already have a trigger wich updates a little configuration table config consisting of table_name | mat_view_name | need_update -----------+---------------+------------ table1 | mat_view | TRUE/FALSE table2 | mat_view | TRUE/FALSE So if