Received: from smtp.cistron-office.nl (10fwd.cistron-office.nl [195.64.65.197]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f27Jqrx92182 for ; Wed, 7 Mar 2001 14:52:53 -0500 (EST) (envelope-from jtv@cistron-office.nl) Received: from slipstream.cistron-office.nl ([195.64.65.252]) by smtp.cistron-office.nl with smtp (Exim 3.22 #1 (Debian)) id 14ajzL-0007s2-00 for ; Wed, 07 Mar 2001 20:52:47 +0100 Received: by slipstream.cistron-office.nl (sSMTP sendmail emulation); Wed, 7 Mar 2001 20:52:47 +0100 From: "J. T. Vermeulen" Date: Wed, 7 Mar 2001 20:52:47 +0100 To: pgsql-interfaces@postgresql.org Subject: libpq++ Message-ID: <20010307205247.E3900@cistron.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.3.15i X-Disclaimer: Include standard disclaimer here. X-Archive-Number: 200103/67 X-Sequence-Number: 1228 Is anyone maintaining libpq++? My patches are beginning to seriously overlap each other, making it hard to submit them individually. If there's nobody out there, I'd be willing to maintain this code and make more extensive changes. In particular, I would like to: - introduce exceptions instead of manual checking, as suggested in TODO; - update the manual; - review all the little consts, bools, explicits and such; - replace PgTransaction by a more fine-grained and exception-safe mechanism outside the PgDatabase hierarchy; - provide STL-conformant interfaces for iterating over result sets; - allow fields to be accessed in a type-safe manner; - ensure clean compilation under g++ 3.0; - bring functionality up-to-date with libpq if, as & where needed Would that be OK? Jeroen