Re: Variadic polymorpic functions

From: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Variadic polymorpic functions
Date: 2010-01-27 16:07:27
Message-ID: 3eff28921001270807p7e46adbaqbeacb339ecd4a20b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2010/1/27 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> writes:
>> But why still on  separate schema?
>> I'd rather put them all in the public one, so you don't need the "pst." anymore.
>> Just like (most of) all other contrib modules ...
>
> If this were to get committed, it would definitely get made to look just
> like all the other contrib modules; so forget the separate schema.
>
> But what I'm wondering is whether it should be contrib or in core.
> Is there some potential reason why someone might not want it installed?

I'm currently using it to solve a number of problems with dynamic SQL code
in PL/PgSQL functions.

I'm using "EXECUTE psd.format(...)" in order to overcome a number of
"limitations" with the
EXECUTE ... USING form I was not able to solve otherwise.

Something known in the past as "wishful thinking"! :-)

--
Vincenzo Romano
NotOrAnd Information Technologies
NON QVIETIS MARIBVS NAVTA PERITVS

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Aycock, Jeff R. 2010-01-27 16:10:05 Re: syntax error during function call
Previous Message Pavel Stehule 2010-01-27 16:05:42 Re: Variadic polymorpic functions