Re: [GENERAL] RETURNS SETOF RECORD with 1 column - Mailing list pgsql-general

From David G. Johnston
Subject Re: [GENERAL] RETURNS SETOF RECORD with 1 column
Date
Msg-id CAKFQuwZJtD4GC+0qmr=Yo8ogV6jAq9yenW5iOKAYTn5zxv4GnQ@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] RETURNS SETOF RECORD with 1 column  (Vincenzo Romano <vincenzo.romano@notorand.it>)
Responses Re: [GENERAL] RETURNS SETOF RECORD with 1 column  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
On Thursday, July 27, 2017, Vincenzo Romano <vincenzo.romano@notorand.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.

pgsql-general by date:

Previous
From: Tim Uckun
Date:
Subject: Re: [GENERAL] Developer GUI tools for PostgreSQL
Next
From: "David G. Johnston"
Date:
Subject: Re: [GENERAL] RETURNS SETOF RECORD with 1 column