Re: maybe incorrect regexp_replace behavior in v8.3.4 ?

On 16/05/12 14:54, Gauthier, Dave wrote:
> 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'.

If a function is defined as "strict" then any null parameters
automatically result in a null result.

And indeed, this:
   SELECT * FROM pg_proc WHERE proname LIKE 'regexp_r%';
shows pro_isstrict is set to true, as it is for most other function.s

--
   Richard Huxton
   Archonet Ltd