From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Kalyanov Dmitry <kalyanov(dot)dmitry(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Anonymous code block with parameters |
Date: | 2014-09-16 07:57:49 |
Message-ID: | 5417ED7D.4070509@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 09/16/2014 03:15 PM, Pavel Stehule wrote:
> Why we don't introduce a temporary functions instead?
I think that'd be a lot cleaner and simpler. It's something I've
frequently wanted, and as Hekki points out it's already possible by
creating the function in pg_temp, there just isn't the syntax sugar for
"CREATE TEMPORARY FUNCTION".
So why not just add "CREATE TEMPORARY FUNCTION"?
It means two steps:
CREATE TEMPORARY FUNCTION ... $$ $$;
SELECT my_temp_function(blah);
but I'm not personally convinced that a parameterised DO block is much
easier, and the idea just rings wrong to me.
I agree with Pavel that the natural way to parameterise DO blocks, down
the track, will be to allow them to get (and set?) SQL-typed session
variables. Of course, we'd need to support them first ;-)
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-09-16 07:58:18 | Re: Anonymous code block with parameters |
Previous Message | Pavel Stehule | 2014-09-16 07:44:17 | Re: Anonymous code block with parameters |