Jeff Davis wrote:
> On Thu, 2008-09-18 at 15:04 -0400, Tom Lane wrote:
> > This does seem like a bit of a gotcha for someone who writes RETURN NEW
> > instead of RETURN OLD or vice versa, but I'm not sure how much we can do
> > about that. Lots of people like to write triggers that fire on multipl
On Thu, 2008-09-18 at 15:04 -0400, Tom Lane wrote:
> This does seem like a bit of a gotcha for someone who writes RETURN NEW
> instead of RETURN OLD or vice versa, but I'm not sure how much we can do
> about that. Lots of people like to write triggers that fire on multiple
> event types, so we cou
"Michael Nolan" <[EMAIL PROTECTED]> writes:
> Recently I discovered a coding error of mine in a trigger that is called
> only for deletes.
> I was returning NEW instead of OLD.
> Since NEW is undefined when deleting a row, it was failing and the row
> wasn't being deleted.
> However, it was failing
On Thu, 2008-09-18 at 14:21 -0400, Michael Nolan wrote:
> Recently I discovered a coding error of mine in a trigger that is
> called only for deletes.
>
> I was returning NEW instead of OLD.
>
> Since NEW is undefined when deleting a row, it was failing and the row
> wasn't being deleted.
In P
