Tom Lane wrote:
Why not?
The real answer is "it's historical and I didn't see any need to
change it". But one could argue that a function returning NULL
doesn't know it's supposed to be a trigger.
The reason I ask is that this behavior just bit me in PL/Java. Triggers
returning null didn't wor
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> Perhaps you should either change this behavior or make a note it in
> "Writing Trigger Functions in C"?
Okay, I've changed the text thusly:
diff -r1.35 trigger.sgml
434,435c434,437
< A trigger function must return either NULL or a
< HeapTuple
Thomas Hallgren <[EMAIL PROTECTED]> writes:
> In backend/commands/trigger.c the following can be found:
> /*
> * Trigger protocol allows function to return a null pointer,
> * but NOT to set the isnull result flag.
> */
> if (fcinfo.isnull)
> ereport(ERROR,
> W
In backend/commands/trigger.c the following can be found:
/*
* Trigger protocol allows function to return a null pointer,
* but NOT to set the isnull result flag.
*/
if (fcinfo.isnull)
ereport(ERROR,
Why?
Regards,
Thomas Hallgren
---(end of bro
