Message-ID: <49D65F0A.70107@borstad.com>
Date: Fri, 03 Apr 2009 12:10:02 -0700
From: Peter Willis <peterw@borstad.com>
Reply-To: peterw@borstad.com
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Adrian Klaver <aklaver@comcast.net>
CC: pgsql-sql@postgresql.org
Subject: Re: FUNCTION problem
References: 
 <1381545833.2939121238777956737.JavaMail.root@sz0030a.emeryville.ca.mail.comcast.net>
In-Reply-To: 
 <1381545833.2939121238777956737.JavaMail.root@sz0030a.emeryville.ca.mail.comcast.net>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 7bit

Adrian Klaver wrote:
>
> 
> If you are using Postgres 8.1+ then it becomes even easier because you can use OUT parameters in the function argument list to eliminate the "as test(c1 int,c2 int)" clause. At this point it becomes a A-->B-->C problem i.e determine what your inputs are, how you want to process them and how you want to return the output.
> 

'8.1+'?? Hmmm, I'm using 8.3. I could use that.

I got the more complex version of the query to work
by backing away from 'plpgsql' as the language and using
'sql' instead.

I then nested (terribly ugly) my select statements to
generate a single SQL query from all. This allows
me to change the output of the query without needing
to define a new set of output 'OUT' parameters each time
I change things.

I have use of the 'OUT' parameters with another set
of functions though. Thanks for that.

Peter