From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | chris(at)bitmead(dot)com |
Cc: | Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] libpq |
Date: | 2000-02-11 15:10:13 |
Message-ID: | 19512.950281813@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> writes:
> If you think applications may like to keep buffered 100k of data, isn't
> that an argument for the PGobject interface instead of the PGresult
> interface?
How so? I haven't actually figured out what you think PGobject will do
differently from PGresult. Given the considerations I mentioned before,
I think PGobject *is* a PGresult; it has to have all the same
functionality, including carrying a tuple descriptor and a query
status (+ error message if needed).
> This seems too much responsibility to press onto libpq, but if the user
> has control over destruction of PQobjects they can buffer what they
> want, how they want, when they want.
The app has always had control over when to destroy PGresults, too.
I still don't see the difference...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-02-11 15:13:32 | Re: [HACKERS] how to make libpq on winnt using the 'win32.mak's |
Previous Message | Tom Lane | 2000-02-11 15:07:04 | Re: [HACKERS] Solution for LIMIT cost estimation |