Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id AB94F9FB675 for ; Thu, 25 Jan 2007 18:13:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 23945-01 for ; Thu, 25 Jan 2007 18:13:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 462279FB674 for ; Thu, 25 Jan 2007 18:13:29 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l0PMDSH29937; Thu, 25 Jan 2007 17:13:28 -0500 (EST) From: Bruce Momjian Message-Id: <200701252213.l0PMDSH29937@momjian.us> Subject: Re: ruby-postgres module needs work, maintainer In-Reply-To: <1169763045.20694.147.camel@dogma.v10.wvs> To: Jeff Davis Date: Thu, 25 Jan 2007 17:13:28 -0500 (EST) CC: "Joshua D. Drake" , pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/40 X-Sequence-Number: 6418 Jeff Davis wrote: > On Thu, 2007-01-25 at 15:18 -0500, Bruce Momjian wrote: > > > ruby-postgres != plruby > > > > Oops, sorry. I got confused. I also have not heard from the > > ruby-postgres guy, but as a community we are less likely to have heard > > from him because interfaces are more independent. > > > > I finally did reach the ruby-postgres guy. He said he would incorporate > my patches. > > I'd like a real release (that becomes a gem), because the current ruby- > postgres release is not sufficient (in a number of ways), and I got at > least one response from someone who literally skipped PostgreSQL support > in their app because of it: > > http://groups.google.com/group/comp.lang.ruby/msg/450c15cb3848129b > > I expect there will be more patches also. Hopefully we can get this up > to speed. > > I've been informed that the Ruby community's gem releases are heavily > dependent on rubyforge. Without involvement of the rubyforge ruby- > postgres project, releases would have to be under a different name > (which would mean changing client code -- not desirable). This is my > understanding, anyway. Good, sounds like things are moving forward. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +