> On 24 Jan 2020, at 08:27, Peter Eisentraut
> wrote:
>
> I definitely want to make it work in a way that does not require writing C
> code. My idea was to create a new type, perhaps called "descriptor", that
> represents essentially a tuple descriptor. (It could be exactly a TupleDesc,
> a
On 2019-12-20 01:30, Vik Fearing wrote:
On 16/12/2019 22:13, Tom Lane wrote:
That being the case, I'm not in favor of using up SQL syntax space for it
if we don't have to.
Do I understand correctly that you are advocating *against* using
standard SQL syntax for a feature that is defined by the
On 2019-12-16 22:13, Tom Lane wrote:
Hm. Given that this involves a function-taking-and-returning-internal,
I think it's fairly silly to claim that it is implementing a SQL-standard
feature, or even a subset or related feature. Nor do I see a pathway
whereby this might end in a feature you coul
On 2019-12-16 19:53, Peter Eisentraut wrote:
SQL:2016 has a feature called polymorphic table functions (PTF) that
addresses this. The full PTF feature is much larger, so I just carved
out this particular piece of functionality. Here is a link to some
related information:
https://modern-sql.com/
Vik Fearing writes:
> On 16/12/2019 22:13, Tom Lane wrote:
>> That being the case, I'm not in favor of using up SQL syntax space for it
>> if we don't have to.
> Do I understand correctly that you are advocating *against* using
> standard SQL syntax for a feature that is defined by the SQL Standa
On 16/12/2019 22:13, Tom Lane wrote:
> That being the case, I'm not in favor of using up SQL syntax space for it
> if we don't have to.
Do I understand correctly that you are advocating *against* using
standard SQL syntax for a feature that is defined by the SQL Standard
and that we have no simil
Peter Eisentraut writes:
> I want to address the issue that calling a record-returning function
> always requires specifying a result column list, even though there are
> cases where the function could be self-aware enough to know the result
> column list of a particular call. For example, mo
Hi
po 16. 12. 2019 v 19:53 odesÃlatel Peter Eisentraut <
peter.eisentr...@2ndquadrant.com> napsal:
> I want to address the issue that calling a record-returning function
> always requires specifying a result column list, even though there are
> cases where the function could be self-aware enough
