Re: Opening a plpgsql cursor parameter by name - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Opening a plpgsql cursor parameter by name
Date
Msg-id 26238.1285170423@sss.pgh.pa.us
Whole thread Raw
In response to Opening a plpgsql cursor parameter by name  (Yeb Havinga <yebhavinga@gmail.com>)
Responses Re: Opening a plpgsql cursor parameter by name  (Yeb Havinga <yebhavinga@gmail.com>)
List pgsql-hackers
Yeb Havinga <yebhavinga@gmail.com> writes:
> We intend to implement $subject, so instead of

> mycursor CURSOR (myparm text) IS SELECT myparm;
> OPEN mycursor('A');

> it would be possible to do

> OPEN mycursor(myparm := 'A');

Is this really worth the trouble?  Is it supported by any other DBMS?
Are cursors used so much, or with so many parameters, that there's a
real benefit to be gained?  (I tend to think that FOR loops are better
than cursors 99% of the time.)

I wouldn't be so obstructionist if this syntax weren't in flux.
But seeing that we have hopes of migrating from := to => before
very long, adding another dependency on that choice where it's
not buying a lot of functionality doesn't seem like a good idea.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: moving development branch activity to new git repo
Next
From: Robert Haas
Date:
Subject: Re: Standby registration