Re: add function argument names to regex* functions.
От
Tom Lane
Тема
Re: add function argument names to regex* functions.
Дата
Msg-id
1258361.1721847108@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
add function argument names to regex* functions. jian he <jian.universality@gmail.com>
Re: add function argument names to regex* functions. Peter Eisentraut <peter@eisentraut.org>
Re: add function argument names to regex* functions. jian he <jian.universality@gmail.com>
Re: add function argument names to regex* functions. Peter Eisentraut <peter@eisentraut.org>
Re: add function argument names to regex* functions. "Dian Fay" <di@nmfay.com>
jian he writes: > On Fri, Jul 19, 2024 at 5:48 AM Tom Lane wrote: >> The larger issue is that contrib/citext offers versions of some of >> these functions that are meant to be drop-in replacements using >> citext input. Hence, we need to add the same parameter names to >> those functions, or they'll fail to replace some calls. > citext module, these functions: > regexp_match() > regexp_matches() > regexp_replace() > regexp_split_to_array() > regexp_split_to_table() > were created in contrib/citext/citext--1.4.sql, we can add the CREATE > OR REPLACE FUNCTION to 1.4.sql. > but to avoid unintended consequences I just add these to the newly > created file citext--1.6--1.7.sql, > to make a version bump. Yes. You *have to* do it like that, the shortcut is not an option, because without an extension update script there is no way to upgrade an existing installation to the new definition. Basically, once we ship a given release of an extension, that script is frozen in amber. I haven't heard any further bikeshedding on the argument names, so I'll move forward with committing this soon. regards, tom lane
В списке pgsql-hackers по дате отправления
От: Robert Haas
Дата: