From: Andrew Dunstan <andrew@dunslane.net>
To: neilc@samurai.com
Cc: alvherre@dcc.uchile.cl
Cc: immaad@gmail.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: Executing Anonymous Blocks
Date: Tue, 29 Mar 2005 05:55:55 -0600 (CST)
Message-ID: <1089.24.211.165.134.1112097355.squirrel@www.dunslane.net> (raw)
In-Reply-To: <42490AF0.6040704@samurai.com>
References: <42490AF0.6040704@samurai.com>
Neil Conway said:
> Alvaro Herrera wrote:
>> On Mon, Mar 28, 2005 at 12:27:18PM +0500, imad wrote:
>>>I want to know is there any way to execute an anonymous PL/pgSQL block
>>>in PostgreSQL.
>>
>> No, there isn't.
>
> It might be possible to implement at least some of this functionality
> entirely in the client. So:
>
> BLOCK;
> /* your pl/pgsql code here */
> END BLOCK;
>
> Could be transformed by the client app to:
>
> CREATE FUNCTION anon_xxx() AS '/* your pl/pgsql code here'
> RETURNS void LANGUAGE 'plpgsql';
> SELECT anon_xxx();
> DROP FUNCTION anon_xxx();
>
> This would be pretty limited -- you couldn't get a return value from
> the anonymous block, for example -- but I can see it being useful in
> some situations.
>
I don't see that performing the same transformation at the SQL level would
be any harder. Then if we ever got SQL host variables we might have a good
way of using them ;-). Of course, another question is whether we should make
plpgsql special, or allow anonymous blocks in any supported language.
cheers
andrew
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: andrew@dunslane.net, neilc@samurai.com, alvherre@dcc.uchile.cl, immaad@gmail.com, pgsql-hackers@postgresql.org
Subject: Re: Executing Anonymous Blocks
In-Reply-To: <1089.24.211.165.134.1112097355.squirrel@www.dunslane.net>
* 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