From: | "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inline PL/pgSQL |
Date: | 2005-05-09 23:28:42 |
Message-ID: | 427FF22A.4000900@tvi.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David,
I agree with your idea. That seems like it would be somewhat easy to
implement and would do exactly what I would need. Anyone else have
ideas or thoughts along this line?
David Fetter wrote:
>On Mon, May 09, 2005 at 11:44:23AM -0600, Jonah H. Harris wrote:
>
>
>>Hey everyone,
>>
>>In addition to package support in plpgsql, it would be really handy
>>to have inline plpgsql. Likewise, I think there are others who feel
>>this way as-well.
>>
>>
>
>Why yes, there are. :)
>
>
>
>>Years ago, Oracle merged PL/SQL with their normal SQL parser which
>>allowed for inline PL/SQL. They did this because it was difficult
>>to maintain two separate parsers. While this worked great for
>>Oracle, it probably wouldn't really work as well for PostgreSQL
>>because pgsql supports multiple procedural languages.
>>
>>
>
>I proposed a syntax for this awhile back. I haven't found it in the
>archives, but it goes like this:
>
>EXECUTE IMMEDIATE $$
> function body here
>$$
>LANGUAGE plfoo;
>
>Similarly, a CREATE TEMPORARY FUNCTION could be quite handy.
>
>Cheers,
>D
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2005-05-10 00:26:35 | Re: Inline PL/pgSQL |
Previous Message | Simon Riggs | 2005-05-09 23:16:17 | Re: Table Partitioning, Part 1 |