Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
| От | Tom Lane |
|---|---|
| Тема | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
| Дата | |
| Msg-id | 25854.1320002273@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? (Darren Duncan <darren@darrenduncan.net>) |
| Ответы |
Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."? |
| Список | pgsql-hackers |
Darren Duncan <darren@darrenduncan.net> writes:
> The real question to ask ourselves is, if Eric Ridge is willing to do all the
> work to implement this feature, and the code quality is up to the community
> standards and doesn't break anything else, then will the code be accepted?
It's entirely possible that it will get bounced on standards-compliance
grounds. In particular, I don't think it's acceptable to introduce a
new reserved keyword for this --- that would fall under the "fails to
not break anything else" category.
regards, tom lane
В списке pgsql-hackers по дате отправления: