On Wed, Apr 27, 2005 at 10:38:48AM -0600, [EMAIL PROTECTED] wrote:
>
> What about performance, if its a matter of choice between after or before
> insert, what perform better?
According to the "Triggers" chapter in the documentation, "If you have
no specific reason to make a trigger before or afte
>PostgreSQL 8.0 introduced PL/pgSQL exception handlers.
>http://www.postgresql.org/docs/8.0/interactive/plpgsql-control-structures.h
tml#PLPGSQL-ERROR-TRAPPING
>Regardless of whether the trigger is BEFORE or AFTER, an untrapped
>error will abort the insert.
>CREATE FUNCTION trigfunc() RETURNS tr
On Wed, Apr 27, 2005 at 05:24:16PM +0200, Stephane Bortzmeyer wrote:
> On Wed, Apr 27, 2005 at 08:45:44AM -0600,
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote
> >
> > I am concerned about how reliable is an before insert trigger, i
> > made some computation in my trigger and i want that no matte
On Wed, Apr 27, 2005 at 08:45:44AM -0600,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote
a message of 21 lines which said:
> I am concerned about how reliable is an before insert trigger, i
> made some computation in my trigger and i want that no matter what
> happens inside the trigger (exception
Hi ppl,
i have a specific question about insert triggers, in the docs i found that
you can change the value of an inserted column using the following syntax:
NEW.column_name := value
and then if you return NEW the new value is stored instead of the original.
this is true if it is a before insert
