Horton

Re: [PATCH] Add error_on_null() to produce an error if the input is null

Vik Fearing <vik@postgresfriends.org>

View thread
From: Vik Fearing <vik@postgresfriends.org>
To: Joel Jacobson <joel@compiler.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-08-30T12:52:20Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Bump catalog version for new function error_on_null()

  2. Add error_on_null(), checking if the input is the null value

On 30/08/2025 13:49, Joel Jacobson wrote:
> Dear fellow hackers,
>
> This polymorphic function produces an error if the input value is null,
> otherwise it returns the input value unchanged.


This only checks for the null value.  I don't think we need to change 
the function's name, but we do need to be more precise in the 
documentation that it checks for the null value and not values that are 
null.


Perhaps replacing "Produces an error if the input is null, and returns 
the input otherwise." with "Produces an error if the input is the null 
value, and returns the input otherwise."


Then also add ROW(NULL, NULL)) to the regressions tests showing that we 
are aware that that is the behavior for things that are null but are not 
the null value.

-- 

Vik Fearing