Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation
Date
Msg-id 201005311412.o4VECtI11351@momjian.us
Whole thread Raw
In response to Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List pgsql-bugs
Daniele Varrazzo wrote:
> On Sun, May 30, 2010 at 4:45 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> > On Sat, May 29, 2010 at 5:00 PM, Bruce Momjian <bruce@momjian.us> wrote:
> >> I have updated the patch, attached, to clarify that this returns text
> >> arrays, and that you can force it to always return one row using
> >> COALESCE() and a '|' pattern (the later suggested by Daniele Varrazzo).
> >
> > I don't find this part to be something we should include in the
> > documentation. ?If we want to include a workaround, how about defining
> > a non-SRF that just calls the SRF and returns the first row?
>
> I think a documentation correction could be backported without problem
> to all the currently maintained version of PostgreSQL (which would be
> of good google value, as very often google searches lands you to
> previous releases doc pages), whereas a easier to use function would
> be a new feature and as such could only be introduced in 9.0 or even
> 9.1.

While you might have had this problem, it is not a common problem so not
something we are about to take tons of time addressing.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #5416: int4inc() is wrong