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:36:47 |
Message-ID: | CAKFQuwa3462wwBzmEpnAfOgaOynSihufePKqu_bGSWT4saVqLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday, July 27, 2017, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Thursday, July 27, 2017, Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it
> <javascript:_e(%7B%7D,'cvml','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.
>
>
Except you'd have no where to put the "setof" modifier...So, yeah, you
probably aren't going to personal style preference catered to here.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | vinny | 2017-07-28 06:53:51 | Re: Developer GUI tools for PostgreSQL |
Previous Message | David G. Johnston | 2017-07-28 06:29:02 | Re: RETURNS SETOF RECORD with 1 column |