maybe incorrect regexp_replace behavior in v8.3.4 ? - Mailing list pgsql-general

From Gauthier, Dave
Subject maybe incorrect regexp_replace behavior in v8.3.4 ?
Date
Msg-id 0AD01C53605506449BA127FB8B99E5E10F18731A@FMSMSX105.amr.corp.intel.com
Whole thread Raw
Responses Re: maybe incorrect regexp_replace behavior in v8.3.4 ?
Re: maybe incorrect regexp_replace behavior in v8.3.4 ?
List pgsql-general

Hi:

 

bi_hsx_a0_latest=# select regexp_replace('xxx','^xxx$','abc');

regexp_replace

----------------

abc

(1 row)

expected behavior because there's a match

 

 

bi_hsx_a0_latest=# select regexp_replace('xxx','^xxxy$','abc');

regexp_replace

----------------

xxx

(1 row)

expected because there is no match (the 'y' in 'xxxy')

 

 

 

bi_hsx_a0_latest=# select regexp_replace('xxx','^xxxy$',null);

regexp_replace

----------------

 

(1 row)

But why did it return null in this case?  I would think no match would leave it 'xxx'.

 

Thanks in Advance for any help and/or explanation.

 

 

pgsql-general by date:

Previous
From: Vibhor Kumar
Date:
Subject: Re: casting behavior of oids and relation names
Next
From: Richard Huxton
Date:
Subject: Re: maybe incorrect regexp_replace behavior in v8.3.4 ?