Re: ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname
Date
Msg-id 4C5991A1020000250003420F@gw.wicourts.gov
Whole thread Raw
In response to ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname  (Boszormenyi Zoltan <zb@cybertec.at>)
Responses Re: [HACKERS] ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname  (Michael Meskes <michael@fam-meskes.de>)
List pgsql-hackers
Michael Meskes <michael@fam-meskes.de> wrote:
> I'd consider this a bug.
Could you explain why?  The assertions that people consider it a bug
without explanation of *why* is confusing for me.
It sounds more like a feature of the ECPG interface that people
would really like, and which has been technically possible since
PostgreSQL 8.3, but for which nobody submitted a patch until this
week.  There was some hint that a 9.0 ECPG patch added new features
which might make people expect this feature to have also been added.
If this patch isn't necessarily correct, and would be dangerous to
apply at this point, should the other patch be reverted as something
which shouldn't go out without this feature?
-Kevin


pgsql-hackers by date:

Previous
From: Nilson
Date:
Subject: Using Small Size SSDs to improve performance?
Next
From: Tom Lane
Date:
Subject: Re: Drop one-argument string_agg? (was Re: [BUGS] string_agg delimiter having no effect with order by)