I agree, that would be nice. Since the concept of partitioning is
fundamental you could materialize in small chunks, that could keep
materialization times down. You're especially lucky If one of the
partition dimensions is time-based because you're highly likely to
only materialize new data in that case.
One problem I run into a lot is that I have to aggregate into some
intermediate table to then do some kind of final output. It would be
nice to have that intermediate table always materialized. Right now I
just run them on hourly or daily schedules.
I think the main thing right now is just to get all the normal bugs
worked out, I feel like when I just create random queries it's a toss
up as to whether it will work or not..:) I'd like to fix that.
Josh
On Dec 15, 2008, at 7:10 PM, David Phillips wrote:
On Mon, Dec 15, 2008 at 1:15 PM, Ashish Thusoo
<[email protected]> wrote:
There is a lot of work done on a technology called materialized
views which
can provide a lot of these benefits in a very useable manner,
though at the
expense of using more disk storage. Essentially, the idea is to
materialize
views of data and keep them updated when data changes.
The other part is how they are used. The database can rewrite queries
to use the materialized view instead of the base tables. This rewrite
happens automatically, without any code changes or requiring users to
know about the materialized views. A database tool can analyze
queries and suggest materialized views to create.
