| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Eric Ridge <eebbrr(at)gmail(dot)com> |
| 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, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Subject: | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
| Date: | 2011-11-01 22:47:18 |
| Message-ID: | 26758.1320187638@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Eric Ridge <eebbrr(at)gmail(dot)com> writes:
> My original thought, that I probably didn't explain too clearly, was
> to make the "EXCLUDING (...)" bit a modifier to the A_Star node. The
> idea being that you could write "* EXCLUDING (...)" anywhere you can
> currently write "*".
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric B. Ridge | 2011-11-01 23:11:00 | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
| Previous Message | Ross J. Reedstrom | 2011-11-01 22:17:40 | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |