Re: plpgsql lacks generic identifier for record in triggers... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plpgsql lacks generic identifier for record in triggers...
Date
Msg-id 24065.1101353066@sss.pgh.pa.us
Whole thread Raw
In response to plpgsql lacks generic identifier for record in triggers...  (Sean Chittenden <sean@chittenden.org>)
List pgsql-hackers
Sean Chittenden <sean@chittenden.org> writes:
> ... Better yet, could TRIGGER functions be allowed to 
> return nothing (ala VOID)?
> Which would tell the backend to assume that the row wasn't changed and 
> proceed with its handling.  This is the preferred approach, IMHO... but 
> I think is the hardest to achieve (I haven't looked to see what'd be 
> involved yet).

plperl is doing it that way, so I don't see why plpgsql couldn't allow
it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Postresql 8.0 Beta 3 - SELECT ... FOR UPDATE
Next
From: Rod Taylor
Date:
Subject: Re: Postresql 8.0 Beta 3 - SELECT ... FOR UPDATE