From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Royce Ausburn <royce(dot)ml(at)inomial(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, yebhavinga(at)gmail(dot)com |
Subject: | Re: [REVIEW] Patch for cursor calling with named parameters |
Date: | 2011-10-06 16:23:40 |
Message-ID: | 3583.1317918220@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Royce Ausburn <royce(dot)ml(at)inomial(dot)com> writes:
> Initial Review for patch:
> http://archives.postgresql.org/pgsql-hackers/2011-09/msg00744.php
> The patch adds a means of specifying named cursor parameter arguments in pg/plsql.
> Do we want that?
> I very rarely use pg/plsql, so I won't speak to its utility. However there has been some discussion about the idea:
> http://archives.postgresql.org/pgsql-hackers/2010-09/msg01440.php
I still think what I said in that message, which is that it's premature
to add this syntax to plpgsql cursors when we have thoughts of changing
it. There is not any groundswell of demand from the field for named
parameters to cursors, so I think we can just leave this in abeyance
until the function case has settled.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-10-06 16:32:27 | Re: checkpoints are duplicated even while the system is idle |
Previous Message | David E. Wheeler | 2011-10-06 16:19:23 | Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding. |