Re: [HACKERS] PQdeleteTuple function in libpq

From: Pavel Golub <pavel(at)microolap(dot)com>
To: Andrew Chernow <ac(at)esilo(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: [HACKERS] PQdeleteTuple function in libpq
Date: 2011-06-02 08:28:26
Message-ID: 707574086.20110602112826@gf.microolap.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Hello, Andrew.

You wrote:

AC> On 6/1/2011 11:43 AM, Pavel Golub wrote:
>> Hello.
>>
>> I'm some kind of PQdeleteTuple function will be very usefull in libpq.
>> Because right now after deleting some record I need refetch result
>> set, or mark tuple as deleted and this is headache for me.
>>

AC> IMHO, this should be handled by the application. You could track tuples
AC> removed in an int[] or copy the result set into an application defined
AC> array of C structures. I've always been under the impression that
AC> PGresult objects are immutable once delivered to the application.

Andrew, why we have PQmakeEmptyPGresult, PQcopyResult,
PQsetResultAttrs, PQsetvalue and PQresultAlloc in this case? Of course
there's no big deal with their absence but let's be consistent.

--
With best wishes,
Pavel mailto:pavel(at)gf(dot)microolap(dot)com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2011-06-02 08:39:05 patch: enhanced get diagnostics statement 2
Previous Message Pavel Golub 2011-06-02 08:24:18 Re: [HACKERS] PQdeleteTuple function in libpq

Browse pgsql-interfaces by date

  From Date Subject
Next Message Pavel Golub 2011-06-02 08:44:51 Re: PQdeleteTuple function in libpq
Previous Message Pavel Golub 2011-06-02 08:24:18 Re: [HACKERS] PQdeleteTuple function in libpq