| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: 2 million row database from hell! help a newbie in over his head.
The post indicated that MySQL was being used. I didn't realize that MySQL supports materialized views. I don't understand what you mean by "More advanced (and more relational) solution would be using index".
Carl
"Mikito Harakiri" <nospam_at_newsranger.com> wrote in message
news:wRQg7.10654$2u.76220_at_www.newsranger.com...
> In article <lcHg7.182793$%a.7691942_at_news1.rdc1.sdca.home.com>, Carl
says...
>
> >If you have a very "popular" query, such as average rainfall for last
year
> >per region, create a table for this.
>
> If you have a very popular query, such as average rainfall for last year
> per region, create a materialized view (snapshot) for this. More advanced
(and
> more relational) solution would be using index. I'm not sure if built-in
indexes
> for "group by" are readily available yet off the shelf, but with extending
> indexing feature you can certainly program one.
>
>
>
Received on Wed Aug 22 2001 - 21:58:17 CDT
![]() |
![]() |