Re: psql: add \create_function command
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Steve Chavez <steve@supabase.io>, Andrew Dunstan <andrew@dunslane.net>,
walther@technowledgy.de, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2024-01-29T17:29:12Z
Lists: pgsql-hackers
po 29. 1. 2024 v 18:11 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:
> Steve Chavez <steve@supabase.io> writes:
> > However, :{?variable_name} is already taken by psql to test whether a
> > variable is defined or not. It might be confusing to use the same syntax.
>
> Hmm. Maybe we could go with :{+...} or the like?
>
> > How about using the convention of interpreting an identifier as a file
> path
> > if it has an slash on it?
>
> Sorry, that is just horrid. foo/bar means division, and "foo/bar"
> is simply an identifier per SQL standard, so you can't squeeze that
> in without breaking an ocean of stuff. Plus, there are many use-cases
> where there's no reason to put a slash in a relative filename.
>
sometimes paths starts by $ or .
or maybe :{{ ... }}
>
> regards, tom lane
>
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Combine FSM updates for prune and no-prune cases.
- 5eafacd2797d 17.0 cited