| From: | Marko Kreen <markokr(at)gmail(dot)com> |
|---|---|
| To: | Federico Di Gregorio <fog(at)dndg(dot)it> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: libpq custom row processing |
| Date: | 2012-08-07 10:51:04 |
| Message-ID: | CACMqXCJO=GUD2Gks-9z5=_bGq_q3RQMXikuYP34Rdkfseu0DDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Tue, Feb 14, 2012 at 3:28 PM, Federico Di Gregorio <fog(at)dndg(dot)it> wrote:
> On 14/02/12 13:11, Marko Kreen wrote:
>> There is an item in current commitfest that might be interesting
>> to Psycopg - a way to provide custom callback to result
>> row processing. By default, libpq takes row data from
>> network buffer and puts it into PGresult. This can now
>> be overrided - column data can be converted immediately
>> to final format and even processed in-flight:
The callback API has been rolled back and final 9.2 will have
single-row-mode instead:
http://www.postgresql.org/docs/devel/static/libpq-single-row-mode.html
Callback API was hard to use and did not support iterative
result processing. This API should fix both problems.
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Federico Di Gregorio | 2012-08-07 11:15:11 | Re: libpq custom row processing |
| Previous Message | Richard Harley | 2012-08-03 13:42:04 | Re: Problem with Zope 2.13.15, python 2.6.6 psycopg2-2.4.5, pg 9.0.3 |