| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Pavel Golub <pavel(at)gf(dot)microolap(dot)com> |
| Cc: | Pavel Golub <pavel(at)microolap(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: PQdeleteTuple function in libpq |
| Date: | 2011-06-01 20:48:55 |
| Message-ID: | 4DE6A5B7.2070700@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-01 20:58:36 | Re: [PERFORM] Hash Anti Join performance degradation |
| Previous Message | Tom Lane | 2011-06-01 20:47:36 | Re: [PERFORM] Hash Anti Join performance degradation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Golub | 2011-06-02 08:24:18 | Re: [HACKERS] PQdeleteTuple function in libpq |
| Previous Message | Merlin Moncure | 2011-06-01 16:24:25 | Re: PQdeleteTuple function in libpq |