| From: | Doug McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | sailesh(at)cs(dot)berkeley(dot)edu |
| Cc: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: System triggers |
| Date: | 2003-05-16 18:11:24 |
| Message-ID: | m3he7ubw37.fsf@varsoon.wireboard.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Sailesh Krishnamurthy <sailesh(at)cs(dot)berkeley(dot)edu> writes:
> >>>>> "Doug" == Doug McNaught <doug(at)mcnaught(dot)org> writes:
>
> Doug> Of course, what happens to the output (if any) from those
> Doug> triggers, given that the client probably doesn't expect it,
> Doug> is an interesting question...
>
> What are the actions of pgsql triggers ? I would have thought they
> result in Update/Delete/Insert operations on other tables. Why should
> that result in output for any client ?
They still (IIRC) return results (like 'INSERT 1 10002') to the
client end of the connection, and there's no a-priori reason they
couldn't do SELECTS as well...
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2003-05-16 18:30:32 | Re: Heads up: 7.3.3 this Wednesday |
| Previous Message | Sailesh Krishnamurthy | 2003-05-16 18:01:48 | Re: System triggers |