Hi,
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.
Shouldn't plpgsql shortcut AND conditions when a previous one fails, as
perl does?
--
OENONE: Quoi ?
PHEDRE: Je te l'ai pr�dit, mais tu n'as pas voulu.
(Ph�dre, J-B Racine, acte 3, sc�ne 3)
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
