Skip site navigation (1) Skip section navigation (2)

Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation
Date: 2010-05-31 14:11:44
Message-ID: 201005311411.o4VEBiQ11120@momjian.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Robert Haas wrote:
> On Sat, May 29, 2010 at 5:00 PM, Bruce Momjian <bruce(at)momjian(dot)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?

Remember this has to return one row for no matches, so a simple SRF will
not work.  I also have not seen enough demand for another function.  A
single doc mention seemed the appropriate level of detail for this.

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2010-05-31 14:12:55
Subject: Re: BUG #5469: regexp_matches() has poor behaviour and more poor documentation
Previous:From: Sachin SrivastavaDate: 2010-05-31 13:17:22
Subject: Re: BUG #5485: Microsoft VC++ exception during postgres instalation

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group