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

From Pavel Stehule
Subject Re: Using scalar function as set-returning: bug or feature?
Date
Msg-id CAFj8pRCY7WXO7BSMCP6+VAjoHaiUkAxHxcjSfjVFybqOZxcFKA@mail.gmail.com
Whole thread Raw
In response to Re: Using scalar function as set-returning: bug or feature?  (Marko Tiikkaja <marko@joh.to>)
Responses Re: Using scalar function as set-returning: bug or feature?
List pgsql-hackers


2018-02-09 12:02 GMT+01:00 Marko Tiikkaja <marko@joh.to>:
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.

This issue can be detected by plpgsql_check and commitfest pipe is patch that raise warning or error in this case.

Regards

Pavel
 


.m

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: CALL stmt, ERROR: unrecognized node type: 113 bug
Next
From: Ildar Musin
Date:
Subject: Re: Proposal: partition pruning by secondary attributes