Re: Using scalar function as set-returning: bug or feature?

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Using scalar function as set-returning: bug or feature?
Date: 2018-02-09 11:02:45
Message-ID: CAL9smLDjJ1D2eB2iJj_WXrL4KXR=KohS+3ZtMuQ76E2fB2b7MA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Feb 9, 2018 at 9:58 AM, Konstantin Knizhnik <
k(dot)knizhnik(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2018-02-09 11:02:57 Re: CALL stmt, ERROR: unrecognized node type: 113 bug
Previous Message Etsuro Fujita 2018-02-09 10:26:01 Re: non-bulk inserts and tuple routing