Request a Demo
Home   >   mailing lists

Re: [PATCH] Add error_on_null() to produce an error if the input is null - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PATCH] Add error_on_null() to produce an error if the input is null
Date
Msg-id aPdBYG9I4jLFPriT@paquier.xyz
Whole thread Raw
In response to Re: [PATCH] Add error_on_null() to produce an error if the input is null  (Vik Fearing <vik@postgresfriends.org>)
Responses Re: [PATCH] Add error_on_null() to produce an error if the input is null
List pgsql-hackers
Tree view 
On Sun, Aug 31, 2025 at 04:16:42PM +0200, Vik Fearing wrote:
> Thank you.  Updated.

This one was marked as committer, so I am looking at it.

The original proposal can also be tracked in this message, where you
want to have a trick for SQL bodies to be able to detect if exactly
one row is returned:
https://www.postgresql.org/message-id/de94808d-ed58-4536-9e28-e79b09a534c7@app.fastmail.com

Why not if this simple solution works for you, using error_on_null()
as the function name.  I'll double-check the whole, probably tomorrow.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Next
From: Fujii Masao
Date:
Subject: Re: Invalid primary_slot_name triggers warnings in all processes on reload