On Mon, September 18, 2006 14:51, Adriaan van Os wrote:
> Still, the issue I raised was about tracing the progress of a SQL command
> in general, not about the
> specific case of using a cursor instead.
True, and dealing with cursors is extra work in libpq.
In the C++ API OTOH there is a class that lets you treat a cursor more or
less as a regular query result. It's set to be replaced with a more
modern version, but it's usable: chunks of result data are fetched on
demand, i.e. as you access them. If you had something like that, all
you'd have to do is issue your query as before, process your data as
before, and update your progress display after every n rows of processing.
You wouldn't really notice any of the complexity underneath.
In response to
pgsql-interfaces by date
|Next:||From: Jan van der Weijde||Date: 2006-09-20 12:38:23|
|Subject: PQsetdbLogin() and PQconnectdb() fail on HPUX11i 64 bits with empty servername|
|Previous:||From: D'Arcy J.M. Cain||Date: 2006-09-18 23:05:06|
|Subject: Re: Python interfaces|