| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Susanne Holzgraefe <miracee(at)web(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: replace() using NULL |
| Date: | 2022-04-13 11:34:29 |
| Message-ID: | Yla1RQYrF9Qn3GR3@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On Wed, Apr 13, 2022 at 10:38:28AM +0200, Susanne Holzgraefe wrote:
>
> tested by using postgresql 13.5:
>
> SELECT REPLACE('xyz‘, ’y’, ’a’); => xaz => expected
> SELECT REPLACE('xyz', 'a‘, 'b‘); => xyz => expected
>
> SELECT REPLACE('xyz‘, 'a‘, NULL); => NULL
>
> Also tested by using MariaDB. Same behavior like in PG.
> Tested with Oracle, result is ‚xyz‘.
>
> That is what I would expect because xyz includes no a.
>
> I neither can find any documentation about this nor a bug report.
The function is declared as STRICT, which means that it won't be called at all
and just returns NULL if any of its parameters is NULL.
Maybe oracle supports such calls as it supports NULL bytes in strings (I
think), but postgres doesn't.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-04-13 13:43:04 | Re: replace() using NULL |
| Previous Message | Susanne Holzgraefe | 2022-04-13 08:38:28 | replace() using NULL |