Re: Using scalar function as set-returning: bug or feature? - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: Using scalar function as set-returning: bug or feature?
Date
Msg-id CAL9smLDjJ1D2eB2iJj_WXrL4KXR=KohS+3ZtMuQ76E2fB2b7MA@mail.gmail.com
Whole thread Raw
In response to Re: Using scalar function as set-returning: bug or feature?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Using scalar function as set-returning: bug or feature?  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Fri, Feb 9, 2018 at 9:58 AM, Konstantin Knizhnik <k.knizhnik@postgrespro.ru> wrote:
Attached please find patch reporting error in case of empty attribute list for SELECT INTO

This is quite short-sighted.  The better way to do this is to complain if the number of expressions is different from the number of target variables (and the target variable is not a record-ish type).  There's been at least two patches for this earlier (one my me, and one by, I think Pavel Stehule).  I urge you to dig around in the archives to avoid wasting your time.


.m

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: non-bulk inserts and tuple routing
Next
From: Pavel Stehule
Date:
Subject: Re: CALL stmt, ERROR: unrecognized node type: 113 bug