| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Standard REGEX functions |
| Date: | 2022-12-18 13:59:56 |
| Message-ID: | 8d7dd34e-d5a8-89e8-360d-5a3945c9f081@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The standard uses XQuery regular expressions, which I believe are subtly
different from ours. Because of that, I had been hesitant to add some
standard functions to our library such as <regex occurrences function>.
While looking at commit 6424337073589476303b10f6d7cc74f501b8d9d7 from
last year (which will come up soon from somebody else for a different
reason), I noticed that we added those functions for Oracle
compatibility even though the regexp language was not the same.
Are there any objections to me writing a patch to add SQL Standard
regular expression functions even though they call for XQuery and we
would use our own language?
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-12-18 14:24:57 | Re: Standard REGEX functions |
| Previous Message | Ted Yu | 2022-12-18 05:12:00 | Re: Rework of collation code, extensibility |