X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 0F1A7DB2DC for ; Thu, 10 Nov 2005 05:54:35 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 43379-02 for ; Thu, 10 Nov 2005 09:54:30 +0000 (GMT) X-Greylist: delayed 00:42:36.144867 by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id 091A5DB26F for ; Thu, 10 Nov 2005 05:54:27 -0400 (AST) Received: from gatefox.foxi.nl (foxi.xs4all.nl [194.109.246.192]) by svr2.postgresql.org (Postfix) with ESMTP id AC60EF0B4C for ; Thu, 10 Nov 2005 09:11:50 +0000 (GMT) Received: from techfox.foxi (techfox.foxi [192.168.0.79]) by gatefox.foxi.nl (8.13.3/8.13.3) with ESMTP id jAA9BkK1011195 for ; Thu, 10 Nov 2005 10:11:46 +0100 From: Frank van Vugt Organization: Foxi Consultants in Technology BV To: pgsql-interfaces@postgresql.org Subject: Re: Incremental results from libpq Date: Thu, 10 Nov 2005 10:11:45 +0100 User-Agent: KMail/1.8 References: <4D426B54-E08F-4DE9-9776-D46610CA4968@slamb.org> <19391.1131571328@sss.pgh.pa.us> <84C7635D-EAF2-40CF-A71C-976077D5465A@slamb.org> In-Reply-To: <84C7635D-EAF2-40CF-A71C-976077D5465A@slamb.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511101011.45702.ftm.van.vugt@foxi.nl> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.042 required=5 tests=[AWL=0.042] X-Spam-Score: 0.042 X-Spam-Level: X-Archive-Number: 200511/14 X-Sequence-Number: 5810 > >> Is there a better way? > > > > Not at the moment. It's been requested before though, so if you > > want to develop a patch for libpq, have at it. > Cool. I think I'll get my own interface hashed out in my kludgey way, > then look at the broader need if it's a success. Just FYI, I'm interested in this extension as well. At the moment, the PostgreSQL driver in TrollTech's Qt will fetch the complete result of any select-query as opposed to for example the Oracle driver which will fetch just the rows that are desired. This results in the fact that for example database-enabled tables in the UI won't do the initial paint as 'snappy' as they could since although they will show only part of the result-set, the underlying driver is still picking up the complete set or records from the backend. -- Best, Frank.