|Subject||feature request: materialized views|
>From: "Ann W. Harrison" <aharrison@...>Ok.
> At 12:28 PM 9/16/2004, Alexander Klenin wrote:
>>I am talking about SNAPSHOTs aka MATERIALIZED VIEWs. The syntax
>>(simplified from Oracle):
> Probably this issue should be discussed on the
>architecture list rather than here.
> My short answer is that materialized views are probably not the answer toThe issue of namespace is IMO completely orthogonal to the
> the question of how to distill data because they affect the global name
concept of cached view. It can be implemented as either
connection-local-temporary or database-global-permanent,
> and because their are either performance burdensWell, the fact that Oracle's implementation is perhaps
>to the underlying tables, or horribly inconsistent.
suboptimal does not, in itself, mean that Firebird is
unable to do better ;)
More to the point, I have used Oracle with some
respectable-sized databases and complex enough queries,
and I must say that, when applied correctly, MATERIALIZED
views can make a difference between an interactive
analytic application (responce time in seconds) and batch
report-generation one (response time in hours).
And all that with just a single word ;)
No doubt, this is not cure-all fit-all solution, but an
important tool for the right circumstances.
Professional hosting for everyone - http://www.host.ru