Re: Table as argument in postgres function

út 21. 5. 2019 v 9:04 odesílatel Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
napsal:

>
>>> Is there anything preventing us from having the planner resolve object
>>> names from strings?
>>>
>>
>> The basic problem is fact so when you use PREPARE, EXECUTE protocol, you
>> has not parameters in planning time.
>>
>
> I agree that it defeats PREPARE as it is currently implemented with
> PQprepare(), and it would never be meaningful to have a query plan that
> hasn't finalized which objects are involved.
>
> But could it be made to work with PQexecParams(), where the parameter
> values are already provided?
>
> Could we make a version of PQprepare() that takes an extra array of
> paramValues for object names that must be supplied at prepare-time?
>

I think so it is possible, but there is a question how much this design
uglify source code. Passing query parameters is maybe too complex already.

Second question. I am not sure if described feature is some different. ANSI
SQL 2016 knows Polymorphic table functions - looks like that. For me, I
would to see implementation of PTF instead increasing complexity of work
with parameters.

https://www.doag.org/formes/pubfiles/11270472/2019-SQL-Andrej_Pashchenko-Polymorphic_Table_Functions_in_18c_Einfuehrung_und_Beispiele-Praesentation.pdf

>
>
>
>