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

From Konstantin Knizhnik
Subject Re: Using scalar function as set-returning: bug or feature?
Date
Msg-id 3d6b0f5c-c157-65b0-f534-225780ace804@postgrespro.ru
Whole thread Raw
In response to Re: Using scalar function as set-returning: bug or feature?  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: Using scalar function as set-returning: bug or feature?
List pgsql-hackers

On 09.02.2018 10:47, Sergei Kornilov wrote:
> Hello
>
>> select into b from my_insert('from func atx');
> You missed select something into b. For example,
> select ret into b from my_insert('from func atx') as ret;
>
> Using scalar function in from is not bug.
> Silent assigning NULL for variables in "into" not matches same in "select"... I think better would be raise warning.
>
> regards, Sergei
Thank you.
Really the problem is caused by empty source list for INTO.
If I rewrite query as

     select my_insert into b from my_insert('from func atx');

then it works as expected.
But I wonder if the original statement should be considered as error or 
at least we should produce warning for such empty projections?


-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company



pgsql-hackers by date:

Previous
From: Garym
Date:
Subject: Is there a cache consistent interface to tables ?
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Parallel bt build crashes when DSM_NONE