From: Michael Fuhr <mike@fuhr.org>
To: Yves Vindevogel <yves.vindevogel@implements.be>
Cc: pgsql-performance@postgresql.org
Subject: Re: Stored Procedure
Date: Tue, 22 Nov 2005 22:13:14 -0700
Message-ID: <20051123051314.GB49008@winnie.fuhr.org> (raw)
In-Reply-To: <06612338d301f531643d479a819e4632@implements.be>
References: <e28aace15975ef9972fdd65ceb6e0ce8@implements.be>
<20051122185941.GA18102@winnie.fuhr.org>
<06612338d301f531643d479a819e4632@implements.be>
On Tue, Nov 22, 2005 at 11:20:09PM +0100, Yves Vindevogel wrote:
> 8.1, hmm, that's brand new.
Yes, but give it a try, at least in a test environment. The more
people use it, the more we'll find out if it has any problems.
> But, still, it's quite some coding for a complete recordset, not ?
How so? The examples I posted are almost identical to how you'd
return a composite type created with CREATE TYPE or SETOF that type,
except that you declare the return columns as INOUT or OUT parameters
and you no longer have to create a separate type. If you're referring
to how I wrote two sets of assignments and RETURN NEXT statements,
you don't have to do it that way: you can use a loop, just as you
would with any other set-returning function.
--
Michael Fuhr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: mike@fuhr.org, yves.vindevogel@implements.be
Subject: Re: Stored Procedure
In-Reply-To: <20051123051314.GB49008@winnie.fuhr.org>
References: <e28aace15975ef9972fdd65ceb6e0ce8@implements.be> <20051122185941.GA18102@winnie.fuhr.org> <06612338d301f531643d479a819e4632@implements.be> <20051123051314.GB49008@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox