From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Seeking Clarification on Function Definitions in PostgreSQL Extensions |
Date: | 2024-06-19 16:50:44 |
Message-ID: | CAKFQuwYUBCqsCS85yvHGkvWBtfxUWFJiTQ9MppUNa5RVitD7ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday, June 19, 2024, Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com> wrote:
> Hi David,
> Thanks for clarification
> > I prefer TABLE. Using setof is more useful when the returned type is
> predefined
> But in the table also isn't the returned type predefined? Example:
> CREATE FUNCTION fun1(integer)
> RETURNS TABLE(
> col1 integer,
> col2 text
> )
> AS 'MODULE_PATHNAME', 'fun1'
> LANGUAGE C;
> We know the returned type will have two columns with type - integer and
> text. Am I correct?
>
Sorry, predefined independently of the function. Using create type then
referring to that type by name in the create function.
>
> > Or a true record where the caller has to specify the shape.
> Sorry but didn't get this shape part?
>
… from rec_func as (col1 isn’t, col2 text) …
The shape is two columns, type int and text respectively.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-06-19 17:07:56 | Re: Manual Failover |
Previous Message | Ayush Vatsa | 2024-06-19 16:46:44 | Re: Seeking Clarification on Function Definitions in PostgreSQL Extensions |