Re: Exposing keywords to clients
От | Tom Lane |
---|---|
Тема | Re: Exposing keywords to clients |
Дата | |
Msg-id | 9669.1209834761@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Exposing keywords to clients (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: Exposing keywords to clients
|
Список | pgsql-patches |
Peter Eisentraut <peter_e@gmx.net> writes: > Dave Page wrote: >>> Perhaps use a separate string for machine parse (say R, T, C, U), and >>> let the string be translatable. >> >> I considered that, but wasn't sure if folks would like the redundancy. >> It's trivial to do of course - any objections? > Is there anything useful you would do with this information? Or would you > just quote all listed words anyway? I think the practical application would be to avoid quoting unreserved keywords, as pg_dump for instance already does. I doubt anyone would bother distinguishing the different types of partially/wholly reserved words. So maybe a boolean would be sufficient --- but I have nothing against the R/T/C/U suggestion. A more radical alternative is just to omit unreserved words from the view altogether. regards, tom lane
В списке pgsql-patches по дате отправления: