I looked at the documentation before I ever posted anything. I didn't know how
EXECUTE works and I actually thought the UPDATE statement itself would set
the variable.
Thanks for the reply.
On Friday 02 September 2005 10:47 am, Tom Lane saith:
> Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> >
Terry Lee Tucker <[EMAIL PROTECTED]> writes:
> Will the FOUND variable be set, when using EXECUTE, as it would be with a
> normal UPDATE statement?
The documentation is pretty specific about which plpgsql statements set
FOUND, and I don't see EXECUTE in that list ...
http://developer.postgresql.o
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
d
I haven't tried it. It's a complicated trigger function with updates to other
tables that are NOT dynamic in nature. If the EXECUTE statement doesn't set
the FOUND variable, then I will be reading the result from a previous
operation. I thought maybe somebody would know this already.
On Friday
On Fri, Sep 02, 2005 at 08:51:41AM -0400, Terry Lee Tucker wrote:
>
> Will the FOUND variable be set, when using EXECUTE, as it would be with a
> normal UPDATE statement?
What happened when you tried it?
--
Michael Fuhr
---(end of broadcast)---
T
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
