From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: update substring pattern matching syntax |
Date: | 2020-06-27 09:07:34 |
Message-ID: | 0f9efbd7-d697-eba5-e48e-9f0d455e9793@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-06-20 09:08, Fabien COELHO wrote:
> I cannot say I'm a fan of this kind of keywords added for some arguments.
> I guess that it allows distinguishing between variants. I do not have the
> standard at hand: I wanted to check whether these keywords could be
> reordered, i.e. whether SUBSTRING(text ESCAPE ec SIMILAR part) was legal.
> I guess not.
It is not.
> Maybe the doc could advertise more systematically whether a features
> conforms fully or partially to some SQL standards, or is pg specific.
I think that would be useful, but it's probably a broader topic than
just for this specific function.
> The
> added documentation refers both to SQL:1999 and SQL99. I'd suggest to
> chose one, possibly the former, and use it everywhere consistently.
fixed
> It seems that two instances where not updated to the new syntax, see in
> ./src/backend/catalog/information_schema.sql and
> ./contrib/citext/sql/citext.sql.
done
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Clean-up-grammar-a-bit.patch | text/plain | 4.7 KB |
v2-0002-Add-current-substring-regular-expression-syntax.patch | text/plain | 13.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-06-27 09:36:10 | Re: pgsql: Enable Unix-domain sockets support on Windows |
Previous Message | Amit Kapila | 2020-06-27 05:22:49 | Re: Remove a redundant condition check |