| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Chris BSomething <xpusostomos(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18715: replace() function silently fails if 3rd argument is null |
| Date: | 2024-11-19 22:40:48 |
| Message-ID: | 3966228.1732056048@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Erik Wienhold <ewie(at)ewie(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-11-19 22:50:36 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
| Previous Message | Erik Wienhold | 2024-11-19 22:34:23 | Re: BUG #18715: replace() function silently fails if 3rd argument is null |