Subject: Re: DBD::Pg 1.20 uncompatible with Postgres 7.3?
From: Jeff Boes <jboes@nexcerpt.com>
To: David Wheeler <david@wheeler.net>
Cc: dbi-users@perl.org, pgsql-interfaces@postgresql.org
In-Reply-To: <808BAE24-0878-11D7-A241-0003931A964A@wheeler.net>
References: <808BAE24-0878-11D7-A241-0003931A964A@wheeler.net>
Content-Type: text/plain
Organization: Nexcerpt, Inc.
Message-Id: <1039110295.26687.106.camel@takin.private.nexcerpt.com>
Mime-Version: 1.0
Date: 05 Dec 2002 12:44:55 -0500
Content-Transfer-Encoding: 7bit

On Thu, 2002-12-05 at 12:39, David Wheeler wrote:
> I chatted with Bruce Momjian about this a bit, too. My idea: PostgreSQL 
> should provide functions that do this sort of thing, so that psql, 
> DBD::Pg, org.postgresql.jdbc, and PostgreSQL ODBC can just use the 
> functions without worrying about the version numbers.
> 
> But then, somebody's gotta write the functions, contributed them to the 
> project, get them committed, and then wait for 7.4 to take advantage of 
> them. Still, it could eventually make such driver metadata requirements 
> much more portable across later PostgreSQL versions.
> 

So what's the answer?  At present, we cannot upgrade to PostgreSQL 7.3
because the DBD code will quit working.  I could produce a patch that
solves our problem, but I have no facilities or expertise to verify that
it will work for everyone.

-- 
Jeff Boes                                      vox 616.226.9550 ext 24
Database Engineer                                     fax 616.349.9076
Nexcerpt, Inc.                                 http://www.nexcerpt.com
           ...Nexcerpt... Extend your Expertise