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

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)
Date: 2014-05-02 07:30:54
Message-ID: CA+HiwqFUmF0jBarfPidNgogg=NgoZvc+SwAQwypmvMXzLCtJgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 2, 2014 at 4:14 PM, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
>
> Why should the above results be any different than if I created the nocols
> table with a column then dropped it?
> Certainly removing all of the records on the drop of the last column would
> be wrong.
>

I see, dropping the only column in a table does exhibit a similar behavior.

--
Amit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip kumar 2014-05-02 09:28:33 Re: Proposal for Merge Join for Non '=' Operators
Previous Message Albe Laurenz 2014-05-02 07:16:07 Re: Allowing empty target list in SELECT (1b4f7f93b4693858cb983af3cd557f6097dab67b)