Re: ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Boszormenyi Zoltan" <zb(at)cybertec(dot)at>, "Michael Meskes" <michael(at)fam-meskes(dot)de>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ECPG dynamic cursor fix for UPDATE/DELETE ... WHERE CURRENT OF :curname
Date: 2010-08-04 21:13:21
Message-ID: 4C5991A1020000250003420F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Meskes <michael(at)fam-meskes(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2010-08-04 21:34:54 Re: Develop item from TODO list
Previous Message Nilson 2010-08-04 21:09:13 Using Small Size SSDs to improve performance?