From: Michael GUIARD <michael@nestor-tech.com>
To: pgsql-hackers-win32@postgresql.org
Subject: libpq request results
Date: Tue, 26 Jul 2005 10:46:36 +0200
Message-ID: <008801c591be$893a24b0$027ba8c0@NSTMike> (raw)
Hi !
I hope I choose the correct mailing list and I hope my question has not been already asked.
Correct me if I wrong.
I do not understand something : what is the difference between this mailing list and the newsgroup : news.postrgesql.org ?
My question concerning postgre sql libpq :
I'd like to use database support in my application. My application are
written in C++ and oftenly I do not use complex database.
So I want to use libpq library to manage db from my applications.
When I make a request like SELECT ... the result is downloaded completely
through network. The problem is that I have to wait the end of the download
before viewing some results (for many result rows and with a poor network
connection I have to wait a lot). I tried to use anychronous methos but the
problem is the same : my application is not locked during result retreiving
(good) but I can't present any results until the download is finished.
Is it possible to ask Postgre engine for a request, then wait for the end of
the request : postgre gives me the total result rows and then ask for
downloading the rows separately ?
thanks
Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-hackers-win32@postgresql.org
Cc: michael@nestor-tech.com
Subject: Re: libpq request results
In-Reply-To: <008801c591be$893a24b0$027ba8c0@NSTMike>
References: <008801c591be$893a24b0$027ba8c0@NSTMike>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox