| From: | Joel Burton <jburton(at)scw(dot)org> |
|---|---|
| To: | Lonnie Cumberland <lonnie_cumberland(at)yahoo(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Triggers on SELECT |
| Date: | 2001-04-12 18:47:29 |
| Message-ID: | Pine.LNX.4.21.0104121446150.1712-100000@olympus.scw.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Thu, 12 Apr 2001, Lonnie Cumberland wrote:
> Hello All,
>
> I have been reading on the uses of the Triggers from within the PL/pgSQL
> language and have seen that you can set up triggers for such things as UPDATE,
> and INSERT.
>
> I was just wondering why there was no trigger mechanicism for the SELECT
> statement?
You could use a RULE instead -- you might be able to get what you want
this way.
--
Joel Burton <jburton(at)scw(dot)org>
Director of Information Systems, Support Center of Washington
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Diehl, Jeffrey | 2001-04-12 18:50:24 | RE: DB porting questions... |
| Previous Message | David Olbersen | 2001-04-12 18:32:19 | DROP TABLE in transaction |