To: Paul Lambert <paul.lambert@reynolds.com.au>
cc: pgsql-sql <pgsql-sql@postgresql.org>
Subject: Re: Function result using execute 
In-reply-to: <475F6E69.3060207@reynolds.com.au> 
References: <475F6E69.3060207@reynolds.com.au>
Comments: In-reply-to Paul Lambert <paul.lambert@reynolds.com.au>
	message dated "Wed, 12 Dec 2007 14:15:21 +0900"
Date: Wed, 12 Dec 2007 01:01:51 -0500
Message-ID: <12742.1197439311@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Paul Lambert <paul.lambert@reynolds.com.au> writes:
> The relevant part of the code looks like thus:
>     EXECUTE curr_query INTO curr_amount;
>     RAISE NOTICE '%',curr_amount;
>     IF NOT FOUND THEN
>        curr_amount=0;
>     END IF;

> ... which suggests to me that although the 
> execute has populated the curr_amount field with something, the IF NOT 
> FOUND is always firing.

IIRC, the EXECUTE command does not change FOUND --- leastwise it's not
listed as one of the plpgsql commands that do set FOUND.

Do you really need an EXECUTE?  If so, maybe you could restructure this
using a FOR ... IN EXECUTE, or some such thing.

> therefore I just be using a test of IF curr_amount IS NOT NULL?

Well, that might work.  Have you thought through the corner case
where the query does find a row but the field's value is null?

			regards, tom lane