Re: SQL/JSON functions vs. ECPG vs. STRING as a reserved word
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Cc: Michael Meskes <meskes@postgresql.org>
Date: 2022-05-31T15:09:23Z
Lists: pgsql-hackers
On 2022-05-29 Su 16:19, Tom Lane wrote: > More generally, I feel like we have a process problem: there needs to > be a higher bar to adding new fully- or even partially-reserved words. > I might've missed it, but I don't recall that there was any discussion > of the compatibility implications of this change. > Thanks for fixing this while I was away. I did in fact raise the issue on 1 Feb, see <https://postgr.es/m/f174a289-3274-569d-875c-2e810101df22@dunslane.net>, but nobody responded that I recall. I guess I should have pushed the discussion further cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Fix ECPG's handling of type names that match SQL keywords.
- 83f1c7b742e8 16.0 landed
-
Make STRING an unreserved_keyword.
- 5f0adec2537d 15.0 landed
-
SQL/JSON query functions
- 1a36bc9dba8e 15.0 cited