Re: wierd AND condition evaluation for plpgsql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: wierd AND condition evaluation for plpgsql
Date
Msg-id 2787.1022594763@sss.pgh.pa.us
Whole thread Raw
In response to wierd AND condition evaluation for plpgsql  (Louis-David Mitterrand <vindex@apartia.org>)
List pgsql-hackers
Louis-David Mitterrand <vindex@apartia.org> writes:
> I just noticed plpgsql evaluates all AND'ed conditions even if the first
> one fails. Example:

>     elsif TG_OP = ''UPDATE'' and old.type_reponse = ''abandon''

> This will break stuff if the trigger is used on INSERT as
> "old.type_reponse" will be substituted and return an error.

I think you are confusing "evaluation" with "syntax checking".

Try putting the reference to OLD inside a nested IF command.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: strange update problem with 7.2.1
Next
From: Andrew Sullivan
Date:
Subject: Re: Replication status & point-in-time recovery