Re: proposal - plpgsql - support standard syntax for named arguments for cursors

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gilles Darold <gilles(at)darold(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: proposal - plpgsql - support standard syntax for named arguments for cursors
Date: 2025-03-04 05:34:14
Message-ID: CAFj8pRAM5_81efK=P5T0_rpS8Xa0D4u=0-=xF3vFV4yXKBYTkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

út 4. 3. 2025 v 0:04 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:

> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> >> po 24. 2. 2025 v 21:05 odesílatel Gilles Darold <gilles(at)darold(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-03-04 06:01:56 Re: [PATCH] Add regression tests of ecpg command notice (error / warning)
Previous Message John Naylor 2025-03-04 05:13:17 Re: Improve CRC32C performance on SSE4.2