On Sun, Jan 1, 2012 at 11:37 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> One thing that I'm concerned about with this is that it treats a plain
> RETURN in a BEFORE trigger as RETURN NULL, whereas arguably it should be
> an error. I haven't found a good way to handle that yet, but I'll keep
I would be very much disinclined to change the behavior of BEFORE
triggers in this way, so I agree we need a way around that.
I'm going to mark this patch Returned with Feedback; I think it's 9.3
material at this point.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2012-03-28 13:57:40|
|Subject: Re: 9.2 commitfest closure (was Command Triggers, v16)|
|Previous:||From: Robert Haas||Date: 2012-03-28 13:51:54|
|Subject: Re: Should I implement DROP INDEX CONCURRENTLY?|