Re: Assert single row returning SQL-standard functions

Merlin Moncure <mmoncure@gmail.com>

From: Merlin Moncure <mmoncure@gmail.com>

To: Joel Jacobson <joel@compiler.org>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-08-29T17:34:27Z

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

On Fri, Aug 29, 2025 at 1:03 AM Joel Jacobson <joel@compiler.org> wrote:

> *) Renaming of database objects seamless, thanks to function body being
> parsed at function definition time and stored as expression nodes.

How does that work in practice?  for current SQL (not pl/pgsql) functions,
this will fail:

create function f() returns int as $$ create temp table i(i int); select *
from i; $$ language sql;
ERROR:  relation "i" does not exist

Also, how do search_path interactions work in your understanding?

merlin