| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: update substring pattern matching syntax |
| Date: | 2020-06-19 10:25:50 |
| Message-ID: | CAFj8pRCNt2iO8OyVQF6EzLh-RZ7TE4FOrCjLhMNk9JetPqqrow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pá 19. 6. 2020 v 11:42 odesílatel Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> napsal:
> At
> <
> https://wiki.postgresql.org/wiki/PostgreSQL_vs_SQL_Standard#Obsolete_syntax_for_substring.28.29>
>
> it is described that the substring pattern matching syntax in PostgreSQL
> does not conform to the current standard. PostgreSQL implements
>
> SUBSTRING(text FROM pattern FOR escapechar)
>
> whereas the current standard says
>
> SUBSTRING(text SIMILAR pattern ESCAPE escapechar)
>
> The former was in SQL99, but the latter has been there since SQL:2003.
>
> It's pretty easy to implement the second form also, so here is a patch
> that does that.
>
+1
Pavel
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2020-06-19 11:38:24 | Re: doing something about the broken dynloader.h symlink |
| Previous Message | matsumura.ryo@fujitsu.com | 2020-06-19 10:18:34 | RE: archive status ".ready" files may be created too early |