Re: quotes in SET grammar - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: quotes in SET grammar
Date
Msg-id 3C7BBB7A.5C5276D0@fourpalms.org
Whole thread Raw
In response to quotes in SET grammar  (Thomas Lockhart <thomas@fourpalms.org>)
Responses Re: quotes in SET grammar  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: quotes in SET grammar  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: quotes in SET grammar  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: quotes in SET grammar  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
...
> I think it would be best to disallow the double-quoted form...
> However, I'm not sure *how* to disallow it without also disallowing
> unquoted words (since ultimately the productions reduce to ColId,
> and the lexer output doesn't distinguish quoted and unquoted
> identifiers).

Well, that would be how to distinguish them; we could define a new
token, say "QIDENT" to refer to quoted identifiers and leave "IDENT" for
the unquoted ones. Then a little work in gram.y should be enough to
finish the job.

The use of IDENT in gram.y is isolated to just a few places so
introducing QIDENT would be almost trivial afaict.
                    - Thomas


pgsql-hackers by date:

Previous
From: Oliver Elphick
Date:
Subject: COPY incorrectly uses null instead of an empty string in last field
Next
From: Tom Lane
Date:
Subject: Re: quotes in SET grammar