Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Date
Msg-id CA+TgmoYJnqOY6BD5g8iHe03UMONQwFjN5_cw+=KEcFVMygFS9A@mail.gmail.com
Whole thread Raw
In response to Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?  (Jim Nasby <jim@nasby.net>)
Responses Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?  ("David E. Wheeler" <david@kineticode.com>)
Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?  (Eric Ridge <eebbrr@gmail.com>)
List pgsql-hackers
On Sun, Oct 30, 2011 at 2:15 PM, Jim Nasby <jim@nasby.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
otherfields 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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [v9.2] make_greater_string() does not return a string in some cases
Next
From: "David E. Wheeler"
Date:
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?