Re: Fix parsing of identifiers in jsonpath

2019-10-02 Thread Nikita Glukhov
Nikita Glukhov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company >From fac98cad7a8dcb1354dd305c55372699d34659fe Mon Sep 17 00:00:00 2001 From: Nikita Glukhov Date: Fri, 22 Mar 2019 15:15:38 +0300 Subject: [PATCH] Fix parsing of identifiers in jsonpath --- src/backe

Re: Fix parsing of identifiers in jsonpath

2019-09-18 Thread Tom Lane
Nikita Glukhov writes: > I don't know if it is possible to check Unicode properties "ID_Start" and > "ID_Continue" in Postgres, and what ZWNJ/ZWJ is. Now, identifier's starting > character set is simply determined by the exclusion of all recognized special > characters. TBH, I think you should s

Re: Fix parsing of identifiers in jsonpath

2019-09-18 Thread Chapman Flack
On 9/18/19 11:10 AM, Nikita Glukhov wrote: > 4. Even if the Unicode escape sequence '\u' is used, it cannot produce >    special symbols or whitespace, because the identifiers are displayed > ... > I don't know if it is possible to check Unicode properties "ID_Start" and > "ID_Continue" in Pos

Fix parsing of identifiers in jsonpath

2019-09-18 Thread Nikita Glukhov
ma-262/10.0/index.html#sec-ecmascript-language-lexical-grammar [2] https://www.ecma-international.org/ecma-262/10.0/index.html#sec-names-and-keywords [3] https://unicode.org/reports/tr31/ -- Nikita Glukhov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company >From 238