From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jim Nasby <jim(at)nasby(dot)net> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Eric Ridge <eebbrr(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
Date: | 2011-10-30 18:54:35 |
Message-ID: | CA+TgmoYJnqOY6BD5g8iHe03UMONQwFjN5_cw+=KEcFVMygFS9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Oct 30, 2011 at 2:15 PM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> If you know that you want all fields except X, Y and Z, why should you be forced to manually cut and paste all the other fields into the view definition? That's wasted time and effort that could better be spent elsewhere.
I agree. This isn't something I would recommend that people do in the
queries they embed in their application, but for ad-hoc queries it
comes up all the time.
OTOH, I'm slightly afraid of how much work it would take to implement
this properly.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2011-10-30 19:03:26 | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
Previous Message | Robert Haas | 2011-10-30 18:49:40 | Re: [v9.2] make_greater_string() does not return a string in some cases |