| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | Alfonso Afonso <aafonsoc(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Emulating trigger BEFORE SELECT behavior |
| Date: | 2013-04-18 14:02:28 |
| Message-ID: | CAOeZVifuoQP3mS20JL5NQZK_BJ8aV-+EWJQX2KcO7iG0dwok5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> How about a RULE:
>
> http://www.postgresql.org/docs/9.2/interactive/sql-createrule.html
>
> Rules can be tricky, so I would at least skim through:
>
> http://www.postgresql.org/docs/9.2/interactive/rules.html
Thanks.
It looks like that it is another way to create a view, which is
probably not I want(I need to store some data per SELECT query in
another table).
One way I was thinking of was creating an updatable view, which is
initialized to NULL. As SELECT queries take place, I can update the
view to include the new rows.
What say?
Atri
--
Regards,
Atri
l'apprenant
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2013-04-18 14:13:56 | Re: Emulating trigger BEFORE SELECT behavior |
| Previous Message | ascot.moss@gmail.com | 2013-04-18 13:40:04 | Re: How to build my own 9.2.4 installer package for IBM Power System ppc64 |