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

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

From: "Eric B(dot) Ridge" <eebbrr(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Darren Duncan <darren(at)darrenduncan(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot)Drake" <jd(at)commandprompt(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Date: 2011-10-31 01:09:07
Message-ID: CB184B3D-C791-4261-B14E-072AC446660B@gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> The exact choice of keyword matters
> a lot less than whether this can be done with out shift/reduce or
> reduce/reduce conflicts.

Which is the problem right now.  See my other email.  

I'll post a diff tomorrow. Maybe if enough folks think is a feature worth having we can find a solution.  My gram.y-fu is at its limits right now. 

eric

In response to

pgsql-hackers by date

Next:From: Christopher BrowneDate: 2011-10-31 02:00:23
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Previous:From: Robert HaasDate: 2011-10-31 00:56:53
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?

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