Re: Assert single row returning SQL-standard functions
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Vik Fearing <vik@postgresfriends.org>
Cc: Joel Jacobson <joel@compiler.org>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-08-29T14:08:00Z
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 →
-
Add error_on_null(), checking if the input is the null value
- 2b75c38b707a 19 (unreleased) landed
-
SQL-standard function body
- e717a9a18b2e 14.0 cited
pá 29. 8. 2025 v 15:47 odesílatel Vik Fearing <vik@postgresfriends.org> napsal: > > On 29/08/2025 12:06, Pavel Stehule wrote: > > > I can imagine allowing the NOT NULL flag for functions, and then the >> > result can be checked on NOT NULL value. >> >> I like the idea of a NOT NULL flag for functions. >> What syntax could we image for that? >> > > CREATE OR REPLACE FUNCTION foo() RETURNS int NOT NULL AS $$ SELECT 10 $$ > LANGUAGE ... > > > What if the function is supposed to return NULL sometimes? The point here > is not the value but the row count. > yes, it doesn't 100% cover Joel's proposal. It can work for naturally NOT NULL domains only. > -- > > Vik Fearing >