Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?

From: "Eric B(dot) Ridge" <eebbrr(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Marti Raudsepp <marti(at)juffo(dot)org>, Marcin Mańk <marcin(dot)mank(at)gmail(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, Darren Duncan <darren(at)darrenduncan(dot)net>, David Wilson <david(dot)t(dot)wilson(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Date: 2011-11-01 23:11:00
Message-ID: CC7DDE3E-7643-4818-B8AA-8662714E199E@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Nov 1, 2011, at 6:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I can think of a number of places where you can write "*" where I'm
> pretty sure we *don't* want this. It should be restricted to top-level
> entries in SELECT targetlists, IMO.

Yes. That is the exact conclusion I've come to.

However, why is

select table.* foo from table

allowed? What does that even mean?

eric

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2011-11-02 00:58:48 Is there a good reason we don't have INTERVAL 'infinity'?
Previous Message Tom Lane 2011-11-01 22:47:18 Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?