X-Original-To: pgsql-interfaces@postgresql.org Received: from mxzilla3.xs4all.nl (mxzilla3.xs4all.nl [194.109.6.49]) by postgresql.org (Postfix) with ESMTP id 627B6476141 for ; Mon, 10 Mar 2003 11:16:30 -0500 (EST) Received: from xs1.xs4all.nl (xs1.xs4all.nl [194.109.3.11]) by mxzilla3.xs4all.nl (8.12.3/8.12.3) with ESMTP id h2AGGO2w014226 for ; Mon, 10 Mar 2003 17:16:29 +0100 (CET) Received: (from jtv@localhost) by xs1.xs4all.nl (8.11.6/8.11.6) id h2AGGOp18944 for pgsql-interfaces@postgresql.org; Mon, 10 Mar 2003 17:16:24 +0100 (CET) (envelope-from jtv) Date: Mon, 10 Mar 2003 17:16:24 +0100 From: "Jeroen T. Vermeulen" To: pgsql-interfaces@postgresql.org Subject: libpqxx and large objects Message-ID: <20030310161623.GD98248@xs4all.nl> Mail-Followup-To: pgsql-interfaces@postgresql.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Archive-Number: 200303/17 X-Sequence-Number: 3766 The latest versions of libpqxx offer a preliminary Large Objects interface that lets you slot a large object into a standard C++ istream, iostream or ostream with all the features that entails. If anyone is interested in advanced large objects usage, please take a look and tell me: - If it works, and what you do with it. I'd like to hear about it either way. - What test cases I could add to my regression test. One thing I haven't tested yet is mixed read/write access. - What I could change in the interface. I know I still need to build my own stream classes around the streambuf class, so that part of the interface is going to get a lot cleaner. Please, if you have some time, download the 1.6.1 source tree from the Developer branch on http://pqxx.tk/ and let me know! TIA, Jeroen