| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | Atri Sharma <atri(dot)jiit(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:13:56 |
| Message-ID: | 516FFFA4.4000004@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/18/2013 07:02 AM, Atri Sharma wrote:
>> 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).
My mistake, forgot ON SELECT only supports DO INSTEAD.
>
> 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?
So what would you run the SELECT against, another view or table?
>
> Atri
>
>
>
> --
> Regards,
>
> Atri
> l'apprenant
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2013-04-18 14:19:09 | Re: Emulating trigger BEFORE SELECT behavior |
| Previous Message | Atri Sharma | 2013-04-18 14:02:28 | Re: Emulating trigger BEFORE SELECT behavior |