From: Pavel Stehule <pavel.stehule@gmail.com>
To: Stephen Cook <sclists@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: statement-level trigger sample out there?
Date: Thu, 29 Nov 2007 15:26:54 +0100
Message-ID: <162867790711290626m105ac02fgd1a6dcab673a24d4@mail.gmail.com> (raw)
In-Reply-To: <474EC9CE.9090609@gmail.com>
References: <20071129130159.110470@gmx.net>
<162867790711290548t2a050d59ta77595c2b05d59ce@mail.gmail.com>
<474EC9CE.9090609@gmail.com>
On 29/11/2007, Stephen Cook <sclists@gmail.com> wrote:
> I am curious (coming from a MS SQL Server background, I just started
> playing with PostgreSQL recently).
yes, I belive. I was too. There are total different style of triggeres
in Postgres. But If I can say, programming in Postgres is much more
confortable. But It is different. You have to use ROW triggers.
>
> 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
>
Statement triggers can be used in some kind of auditing. Maybe. I
didn't use it. And I use Postgres five years.
Pavel
>
>
> 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
> >
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pavel.stehule@gmail.com, sclists@gmail.com
Subject: Re: statement-level trigger sample out there?
In-Reply-To: <162867790711290626m105ac02fgd1a6dcab673a24d4@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox