Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace
От | Gilles Darold |
---|---|
Тема | Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace |
Дата | |
Msg-id | 170bf229-0d4a-eaa1-4fb0-802442964474@darold.net обсуждение исходный текст |
Ответ на | Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace
|
Список | pgsql-hackers |
Le 15/12/2021 à 13:41, Peter Eisentraut a écrit : > On 03.08.21 19:10, Tom Lane wrote: >> Gilles Darold <gilles@darold.net> writes: >>> Sorry I have missed that, but I'm fine with this implemenation so let's >>> keep the v6 version of the patch and drop this one. >> >> Pushed, then. There's still lots of time to tweak the behavior of >> course. > > I have a documentation follow-up to this. It seems that these new > functions are almost a de facto standard, whereas the SQL-standard > functions are not implemented anywhere. I propose the attached patch > to update the subsection in the pattern-matching section to give more > detail on this and suggest equivalent functions among these newly > added ones. What do you think? I'm in favor to apply your changes to documentation. It is a good thing to precise the relation between this implementation of the regex_* functions and the SQL stardard. -- Gilles Darold
В списке pgsql-hackers по дате отправления: