Re: Assert single row returning SQL-standard functions

From: "Joel Jacobson" <joel(at)compiler(dot)org>
To: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assert single row returning SQL-standard functions
Date: 2025-08-29 09:51:12
Message-ID: 6b9be494-1204-4ea4-82d5-dce0ca0ba961@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 29, 2025, at 10:30, Pavel Stehule wrote:
> pá 29. 8. 2025 v 10:16 odesílatel Joel Jacobson <joel(at)compiler(dot)org> napsal:
>> Can we think of some SQL-standard function way to also prevent against 0 rows?
>>
>
> I am afraid there is not nothing. NULL is the correct result in SQL.
> SQL allow to check ROW_COUNT by using GET DIAGNOSTICS commands and
> raising an error when something is unexpected
>
> 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?

Regarding DML functions, could we make the RETURN () trick work somehow?

Here is a failed attempt:

CREATE OR REPLACE FUNCTION test_update(_a int)
RETURNS bool
RETURN (
WITH update_cte AS (
UPDATE footab SET id = _a WHERE footab.id = _a RETURNING footab.id
)
SELECT id FROM update_cte
);

ERROR: WITH clause containing a data-modifying statement must be at the top level
LINE 4: WITH update_cte AS (
^

I'm not sure if this is a standard requirement, or if it's just a PostgreSQL-specific limitation?

/Joel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2025-08-29 09:52:25 Re: Assert single row returning SQL-standard functions
Previous Message Shlok Kyal 2025-08-29 09:46:32 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart