Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)
Date: 2014-05-02 04:30:25
Message-ID: CA+HiwqEgsaArsh6R40e+-pwS==276MbFSiRYZMEEgpv+24QL+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 2, 2014 at 12:57 PM, Amit Langote <amitlangote09(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rajmohan C 2014-05-02 04:37:30 is there a hook by which we can modify input query before postgresql builds raw parse tree
Previous Message Amit Langote 2014-05-02 03:57:04 Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)