Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f27M2Rx53733 for ; Wed, 7 Mar 2001 17:02:28 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id RAA02078; Wed, 7 Mar 2001 17:02:19 -0500 (EST) From: Bruce Momjian Message-Id: <200103072202.RAA02078@candle.pha.pa.us> Subject: Re: libpq++ In-Reply-To: <20010307205247.E3900@cistron.nl> "from J. T. Vermeulen at Mar 7, 2001 08:52:47 pm" To: "J. T. Vermeulen" Date: Wed, 7 Mar 2001 17:02:19 -0500 (EST) CC: pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200103/70 X-Sequence-Number: 1231 > 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? Also, would you review this? ftp://candle.pha.pa.us/pub/postgresql/libpq++.mbox and merge any valuable changes into your copy of the code. Much of it is already in there. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026