Re: regexp_replace( , , , NULL ) returns null? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: regexp_replace( , , , NULL ) returns null?
Date
Msg-id 1440.1399082230@sss.pgh.pa.us
Whole thread Raw
In response to regexp_replace( , , , NULL ) returns null?  (Jim Nasby <jnasby@enova.com>)
Responses Re: regexp_replace( , , , NULL ) returns null?
List pgsql-hackers
Jim Nasby <jnasby@enova.com> writes:
> Is there any particular reason for this:
> decibel@decina.local=# SELECT regexp_replace( 'a', 'a', 'b', null ) IS NULL;
>  ?column? 
> ----------
>  t
> (1 row)

Yeah: regexp_replace is strict.

> ISTM it�d be a lot better if it treated NULL flags the same as ��...

In Oracle's universe that probably makes sense, but to me it's not
sensible.  Why should "unknown" flags produce a non-unknown result?

I find it hard to envision many use-cases where you wouldn't actually
have the flags as a constant, anyway; they're too fundamental to the
behavior of the function.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: New and interesting replication issues with 9.2.8 sync rep
Next
From: Tom Lane
Date:
Subject: Re: Faster array_length()