Re: RETURNS SETOF RECORD with 1 column

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: RETURNS SETOF RECORD with 1 column
Date: 2017-07-28 06:29:02
Message-ID: CAKFQuwZJtD4GC+0qmr=Yo8ogV6jAq9yenW5iOKAYTn5zxv4GnQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday, July 27, 2017, Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
wrote:
>
> The main difference is that with RETURNS SETOF RECORD I still get the
> "usual"(tm) function argument list in the usual place: between two
> parentheses.
> It's a matter of style. And a consistent one.
> But I still don't get the point for not having it for a single column.
>
>
Docs say: " When there are OUT or INOUT parameters, the RETURNS clause can
be omitted. ". Sounds like you should you do just that.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2017-07-28 06:36:47 Re: RETURNS SETOF RECORD with 1 column
Previous Message Tim Uckun 2017-07-28 04:31:06 Re: Developer GUI tools for PostgreSQL