Re: BUG #18715: replace() function silently fails if 3rd argument is null - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18715: replace() function silently fails if 3rd argument is null
Date
Msg-id 3966228.1732056048@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18715: replace() function silently fails if 3rd argument is null  (Erik Wienhold <ewie@ewie.name>)
Responses Re: BUG #18715: replace() function silently fails if 3rd argument is null
List pgsql-bugs
Erik Wienhold <ewie@ewie.name> writes:
> On 2024-11-19 17:47 +0100, Tom Lane wrote:
>> I thought we documented somewhere that built-in functions are strict
>> unless explicitly stated otherwise ... but I sure can't find that
>> statement right now.

> Perhaps this one?:
>> (Most internal functions expect to be declared “strict”.)
>> https://www.postgresql.org/docs/current/xfunc-internal.html

I did see that one, but it's not exactly in an obvious-to-novices
place.

David was working on a new docs section that would talk more about
SQL NULLs in general.  Maybe that would be a reasonable place?
An alternative could be somewhere early in func.sgml, but that chapter
doesn't really have anything I would call an overview section.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: BUG #18715: replace() function silently fails if 3rd argument is null
Next
From: Nathan Bossart
Date:
Subject: Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails