From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL vs SQL/XML Standards |
Date: | 2019-06-01 12:53:35 |
Message-ID: | 5CF2754F.7000702@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/31/19 16:04, Alvaro Herrera wrote:
> https://www.iso.org/standard/41528.html "XQuery Regular Expression
> Support in SQL"
Although I hadn't seen that particular document, I did see those in the
SQL spec and mention them in the wiki page [1].
I should point out that's also a conformance note in the new SQL/JSON
support [2], as the standard specifies XQuery regular expressions for
jsonpath's like_regex predicate, where we're applying POSIX ones
instead.
Doesn't change my thinking much ... I think we should support the
stuff. :) ... using a non-in-house-developed XQuery library to do it,
or better yet, a choice of non-in-house-developed XQuery libraries.
I still think the second idea I suggested on the wiki seems like the
most promising road map [3], though it'll involve a few preparatory
stops along the way.
-Chap
[1]
https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL/XML_Standards#XML_Query_regular_expressions
[2]
https://github.com/obartunov/sqljsondoc/blob/master/README.jsonpath.md#sqljson-conformance
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2019-06-01 14:41:36 | Avoiding possible future conformance headaches in JSON work |
Previous Message | Dmitry Dolgov | 2019-06-01 10:28:28 | Re: Index Skip Scan |