Re: UPDATEABLE VIEWS ... Examples?

From: David Pradier <dpradier(at)apartia(dot)fr>
To: Michael Glaesemann <grzm(at)myrealbox(dot)com>
Cc: postgresql sql list <pgsql-sql(at)postgresql(dot)org>
Subject: Re: UPDATEABLE VIEWS ... Examples?
Date: 2005-06-20 07:56:31
Message-ID: 20050620075631.GD15942@apartia.fr
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

> >This is maybe a newbie question, but what is the difference with a
> >materialized view ?
>
> As I understand it (and that understanding may be wrong) a
> materialized view is a table that holds the values of a view from
> some point in time. A view is a "saved" subselect. Everything you
> call a view, the PostgreSQL backend re-evaluates the definition of
> the view. A materialized view is only as accurate as the last time it
> was updated. Things such as triggers can be used to keep the
> materialized view updated. The key issue with materialized views is
> to make sure it's always up-to-date with the evaluation of the view.

Thanks Michael, I already know what is a materialized view. I often use
them, systematically updated with some triggers.
It's an updatable view that i didn't knew.

It opens some perspectives in programmation, methinks :-)

Thanks all the same,
David

--
dpradier(at)apartia(dot)fr - tel: 01.46.47.21.33 - fax: 01.46.47.21.37

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Luca Rasconi 2005-06-20 09:33:51 FW: help with serial
Previous Message Michael Glaesemann 2005-06-20 07:37:57 Re: UPDATEABLE VIEWS ... Examples?