I am curious (coming from a MS SQL Server background, I just started
playing with PostgreSQL recently).
What type of situation would warrant a statement-level trigger that
can't access the old and new values? Without that access, isn't the
only information you get is the fact that an operation occurred on the
table? Or am I missing something?
-- Stephen
Pavel Stehule wrote:
> Hello
>
> You cannot to access to values in statement trigger. Postgres doesn't
> support it.
>
> Regards
> Pavel Stehule
>
> On 29/11/2007, Christian Kindler <christian.kindler@gmx.net> wrote:
>> Hi
>>
>> Can anyone provide me a simple example of a statement-level trigger? Problem is I do not know how to access the
old.*,new.* values.
>>
>> Thanks
>> Chris
>> --
>> GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
>> Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 1: if posting/reading through Usenet, please send an appropriate
>> subscribe-nomail command to majordomo@postgresql.org so that your
>> message can get through to the mailing list cleanly
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>