Horton

Re: SQL/JSON functions vs. ECPG vs. STRING as a reserved word

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Michael Meskes <meskes@postgresql.org>, pgsql-hackers@lists.postgresql.org
Date: 2022-07-03T17:08:36Z
Lists: pgsql-hackers

Attachments

Noah Misch <noah@leadboat.com> writes:
> On Mon, May 30, 2022 at 05:20:15PM -0400, Tom Lane wrote:
>> [allow EXEC SQL TYPE unreserved_keyword IS ...]

> I didn't locate any problems beyond the test and doc gaps that you mentioned,
> so I've marked this Ready for Committer.

Thanks!  Here's a fleshed-out version with doc changes, plus adjustment
of preproc/type.pgc so that it exposes the existing problem.  (No code
changes from v1.)  I'll push this in a few days if there are not
objections.

			regards, tom lane

Commits

  1. Fix ECPG's handling of type names that match SQL keywords.

  2. Make STRING an unreserved_keyword.

  3. SQL/JSON query functions