Re: Exposing keywords to clients - Mailing list pgsql-patches

From Tom Lane
Subject Re: Exposing keywords to clients
Date
Msg-id 9669.1209834761@sss.pgh.pa.us
Whole thread Raw
In response to Re: Exposing keywords to clients  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Exposing keywords to clients
List 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 by date:

Previous
From: Andreas 'ads' Scherbaum
Date:
Subject: Re: create or replace language
Next
From: Tom Lane
Date:
Subject: Re: configure option for XLOG_BLCKSZ