Re: proposal - plpgsql - support standard syntax for named arguments for cursors
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gilles Darold <gilles@darold.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-03-04T05:34:14Z
Lists: pgsql-hackers
út 4. 3. 2025 v 0:04 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal: > Pavel Stehule <pavel.stehule@gmail.com> writes: > >> po 24. 2. 2025 v 21:05 odesílatel Gilles Darold <gilles@darold.net> > >> napsal: > >>> I think it could be ready to be committed. > > Pushed with a docs/test correction: this also affects the syntax > of FOR-over-cursor. > > >>> Note for the committer: does it make sense to mention in the > >>> documentation that this standard SQL/PSM syntax is preferred than the > PG > >>> syntax? > > > I modified doc in same manner like function's named arguments are > described > Thank you very much Regards Pavel > > I didn't especially care for this change and didn't include it. We've > had the := syntax for decades and aren't likely to ever remove it, > so why start acting like it's deprecated? > > regards, tom lane >
Commits
-
Allow => syntax for named cursor arguments in plpgsql.
- 246dedc5d028 18.0 landed
-
Allow named parameters to be specified using => in addition to :=
- 865f14a2d31a 9.5.0 cited
-
Add support for passing cursor parameters in named notation in PL/pgSQL.
- 4adead1d2242 9.2.0 cited