Horton

Re: add function argument names to regex* functions.

Dian Fay <di@nmfay.com>

View thread View on postgr.es
From: "Dian Fay" <di@nmfay.com>
To: "Jim Nasby" <jim.nasby@gmail.com>, "jian he" <jian.universality@gmail.com>, "Peter Eisentraut" <peter@eisentraut.org>
Cc: "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Date: 2024-01-03T23:05:47Z
Lists: pgsql-hackers 
> > Another possibility is `index`, which is relatively short and not a
> > reserved keyword ^1. `position` is not as precise but would avoid the
> > conceptual overloading of ordinary indices.
>
> I'm not a fan of "index" since that leaves the question of
> whether it's 0 or 1 based. "Position" is a bit better, but I think
> Jian's suggestion of "occurance" is best.

We do have precedent for one-based `index` in Postgres: array types are
1-indexed by default! "Occurrence" removes that ambiguity but it's long
and easy to misspell (I looked it up after typing it just now and it
_still_ feels off).

How's "instance"?

Commits

  1. Doc: fix text's description of regexp_replace's arguments.

  2. Add argument names to the regexp_XXX functions.

  3. Add assorted new regexp_xxx SQL functions.