Apparently, the FOUND variable is set to false regardless of the outcome of
the dynamic update statement. I placed a call to GET DIAGNOSTICS var =
ROW_COUNT. It returned 1. Question is, was that the result of a direct
update previously coded in the same trigger, or is that the result of the
dynamic update statement performed with EXECUTE?
On Friday 02 September 2005 08:51 am, Terry Lee Tucker saith:
> Greetings,
>
> I have a question regarding the use of the FOUND variable within a plpgsql
> function. I have a trigger fuction which executes a dynamic update on a
> different table with the EXECUTE statement. Here's the question:
>
> Will the FOUND variable be set, when using EXECUTE, as it would be with a
> normal UPDATE statement?
>
> Thanks for the input...
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: 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
--
Quote: 87
"To those who cite the First Amendment as reason for excluding God
from more and more of our institutions every day, I say: The First
Amendment of the Constitution was not written to protect the people of
this country from religious values; it was written to protect
religious values from government tyranny."
--Ronald Reagan
Work: 1-336-372-6812
Cell: 1-336-363-4719
email: [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
