Re: Define jsonpath functions as stable
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: pgsql-hackers@lists.postgresql.org
Date: 2019-07-29T14:53:36Z
Lists: pgsql-hackers
Hi, On 7/29/19 10:25 AM, Alexander Korotkov wrote: > * like_regex predicate uses our regular expression engine, which > deviates from standard. I still favor adding some element to the syntax (like a 'posix' or 'pg' keyword in the grammar for like_regex) that identifies it as using a different regexp flavor, so the way forward to a possible compliant version later is not needlessly blocked (or consigned to a standard_conforming_strings-like experience). That would also resolve much of the case against calling that predicate immutable. It looks as if, in my first implementation of XQuery regexps, there will have to be a "not-quite-standard" flag for those too, because it turns out the SQL committee made some tweaks to XQuery regexps[1], whereas any XQuery library one relies on is going to provide untweaked XQuery regexps out of the box. (The differences only affect ^ $ . \s \S) Regards, -Chap [1] https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL/XML_Standards#XML_Query_regular_expressions
Commits
-
Fix some minor spec-compliance issues in jsonpath lexer.
- e56cad84d542 13.0 landed
- 5f3bec0769c1 12.0 landed
-
Doc: improve documentation around jsonpath regular expressions.
- b9cf94c8c249 12.0 landed
- 0a97edb12ec4 13.0 landed
-
Fix bogus handling of XQuery regex option flags.
- d5b90cd64855 13.0 landed
- 148881454208 12.0 landed