Re: Expanding regexp_matches flags - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Expanding regexp_matches flags
Date
Msg-id 4083172.1628782315@sss.pgh.pa.us
Whole thread Raw
In response to Expanding regexp_matches flags  (Jordan Gigov <coladict@gmail.com>)
List pgsql-hackers
Jordan Gigov <coladict@gmail.com> writes:
> A recent thread gave me the idea that it would be convenient to have
> another flag for `regexp_matches` to make it return a singular
> two-dimensional array of matches when performing a global match.

> Why? Well, basically you avoid having to aggregate the rows afterwards
> using by wrapping it in a subquery.

> Is there some interest in this?

I'm not really convinced that has any value.  The first question you
ought to be answering is whether the recently-pushed regexp function
additions don't already serve whatever use-case you had in mind.

If we do do it, I think it ought to be a different function.  "flag"
values that utterly change the meaning of the output sound like a
pretty bad idea.  Also, "returns setof text[]" is very different from
"returns text[]".  The primary reason we invented regexp_match() a few
years ago was to get away from the ugliness involved in trying to
pretend the former is the latter.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jordan Gigov
Date:
Subject: Expanding regexp_matches flags
Next
From: Greg Sabino Mullane
Date:
Subject: Re: make MaxBackends available in _PG_init