Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b) - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)
Date
Msg-id CA+HiwqEgsaArsh6R40e+-pwS==276MbFSiRYZMEEgpv+24QL+Q@mail.gmail.com
Whole thread Raw
In response to Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)
Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)
List pgsql-hackers
On Fri, May 2, 2014 at 12:57 PM, Amit Langote <amitlangote09@gmail.com> wrote:
> I
> s the following behavior perceived fix-worthy?
>
>
> -- note the
> '
> 1's
>  in the output
> s
>
> po
> stgres=# CREATE TABLE test AS SELECT;
> SELECT 1
>
> postgres=# insert into test select;
> INSERT 0 1
>

Or maybe, it just means 1 'null' row/record and not no row at all?

--
Amit



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)
Next
From: Rajmohan C
Date:
Subject: is there a hook by which we can modify input query before postgresql builds raw parse tree