Skip site navigation (1) Skip section navigation (2)

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

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jim Nasby <jim(at)nasby(dot)net>, "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 19:03:26
Message-ID: 5AEE198A-D446-4ED8-BB67-7A483C89618E@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Oct 30, 2011, at 11:54 AM, Robert Haas 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.

It can also be very useful for generating queries that need to omit rows, such as in PL/pgSQL functions that use EXECUTE, not to mention client code.

Best,

David


In response to

pgsql-hackers by date

Next:From: Darren DuncanDate: 2011-10-30 19:04:30
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Previous:From: Robert HaasDate: 2011-10-30 18:54:35
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group