From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Marc Millas <marc(dot)millas(at)mokadb(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: syntax question |
Date: | 2021-06-03 19:21:15 |
Message-ID: | 49061.1622748075@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 6/3/21 12:01 PM, Bruce Momjian wrote:
>> On Thu, Jun 3, 2021 at 08:58:03PM +0200, Marc Millas wrote:
>>> within a function, I want to create another function.
>> You can't create functions inside of functions; same for procedures.
> Sure you can:
Yeah. The actual problem here is that Marc is expecting variable
substitution to occur within a utility (DDL) statement, which it
doesn't. The workaround is to build the command as a string and
use EXECUTE, as Adrian illustrated:
> EXECUTE 'create function ' || bidule || '() RETURNS void language
> plpgsql AS $fnc$ BEGIN END; $fnc$ ';
This is not terribly well explained in the existing docs. I tried
to improve the explanation awhile ago in HEAD:
https://www.postgresql.org/docs/devel/plpgsql-statements.html#PLPGSQL-STATEMENTS-GENERAL-SQL
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vijaykumar Jain | 2021-06-03 19:21:40 | Re: max_connections |
Previous Message | Adrian Klaver | 2021-06-03 19:11:00 | Re: syntax question |