Re: [HACKERS] Broken Constraint Checking in Functions

2003-10-23 Thread Curt Sampson
On Fri, 24 Oct 2003, Bruce Momjian wrote: > Does it belong on the SET CONSTRAINT page, the CREATE TABLE page, or the > CREATE FUNCTION page? Hard to say. Possibly all three. I'd defer to your judgement on this. I'd say I have a slight preference for putting it on the SET CONSTRAINT and CREATE FUN

Re: [HACKERS] Broken Constraint Checking in Functions

2003-10-23 Thread Bruce Momjian
Curt Sampson wrote: > On Fri, 24 Oct 2003, Bruce Momjian wrote: > > > I am not sure we should add something to the SET CONSTRAINT page on > > this. Our current behavior is clearly a bug, and for that reason > > belongs more on the TODO list, where it already is: > > Had it been on the SET CONSTR

Re: [HACKERS] Broken Constraint Checking in Functions

2003-10-23 Thread Curt Sampson
On Fri, 24 Oct 2003, Bruce Momjian wrote: > I am not sure we should add something to the SET CONSTRAINT page on > this. Our current behavior is clearly a bug, and for that reason > belongs more on the TODO list, where it already is: Had it been on the SET CONSTRAINT page, it would have saved me

Re: [HACKERS] Broken Constraint Checking in Functions

2003-10-23 Thread Bruce Momjian
I am not sure we should add something to the SET CONSTRAINT page on this. Our current behavior is clearly a bug, and for that reason belongs more on the TODO list, where it already is: * Have AFTER triggers execute after the appropriate SQL statement in a function, not

[HACKERS] Broken Constraint Checking in Functions

2003-10-10 Thread Curt Sampson
So it seems I got bitten today by this to-do list item: Have AFTER triggers execute after the appropriate SQL statement in a function, not at the end of the function Under normal circumstances, delaying this stuff until the end of the function doesn't bother me; in fact I've even used it