From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: proposal - plpgsql - support standard syntax for named arguments for cursors |
Date: | 2025-02-08 21:25:18 |
Message-ID: | 1893388.1739049918@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> so 8. 2. 2025 v 20:25 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
>> Is there any reason to think that that's actually in the standard?
> I think the possibility to use named arguments in OPEN statements is a
> PostgreSQL proprietary feature.
> And usage of cursors in PL/pgSQL is based on PL/SQL (not on SQL/PSM from
> standard), but named
> arguments for cursor is PostgreSQL proprietary feature and the syntax based
> on usage `:=` is our
> proprietary too.
Hmm ... yeah, it's not in SQL/PSM, but looking at PL/SQL:
https://docs.oracle.com/en/database/oracle/oracle-database/19/lnpls/OPEN-statement.html
I see
You can specify actual cursor parameters with either
positional notation or named notation. For information about
these notations, see "Positional, Named, and Mixed Notation
for Actual Parameters".
and that link blesses the use of "name => value" (and not ":=").
So agreed, we should adjust this.
Is there a reason we need a whole new test case instead of
tweaking one of the existing ones?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Prokhorenko | 2025-02-08 21:56:27 | Re: UUID v7 |
Previous Message | Ed Behn | 2025-02-08 20:24:03 | Re: access numeric data in module |