DomainKey-Signature: a=rsa-sha1; s=main; d=esilo.com; c=simple; q=dns;
	b=zEEZymumPFng0pnYpDbw/2drgUsETmx36HZfJr6z6Cb1tGTNP8RbeDJiKrOtBI9U2
	EWtw42wFhQXA+9zGkLJYg==
Message-ID: <4DE6A5B7.2070700@esilo.com>
Date: Wed, 01 Jun 2011 16:48:55 -0400
From: Andrew Chernow <ac@esilo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
	rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Pavel Golub <pavel@gf.microolap.com>
CC: Pavel Golub <pavel@microolap.com>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	pgsql-interfaces@postgresql.org
Subject: Re: PQdeleteTuple function in libpq
References: <147534417.20110601184310@gf.microolap.com>
In-Reply-To: <147534417.20110601184310@gf.microolap.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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.
>

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

-- 
Andrew Chernow
eSilo, LLC
global backup
http://www.esilo.com/