Обсуждение: Re: DBD::Pg 1.20 uncompatible with Postgres 7.3?
On Wednesday, December 4, 2002, at 11:40 AM, Jeff Boes wrote: > I received the following communication from Tom Lane, who is active in > PostgreSQL development: > >> ... without so much as a "ta-ta" in the release notes. Hmph. Well, >> is >> there any hope that a search-and-replace will convert old source code >> to >> using the new table? > > It shouldn't be a difficult change. Be aware that pg_constraint has > more stuff in it than pg_relcheck did, so you'll want to add "WHERE > contype = 'c'" to be sure you only see the rows corresponding to the > old pg_relcheck table. 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. Best, David -- David Wheeler AIM: dwTheory david@wheeler.net ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: Theory@jabber.org
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
On Thursday, December 5, 2002, at 09:44 AM, Jeff Boes wrote: > 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. Yeah, but it would be a start. Patches warmly welcomed. Regards, David -- David Wheeler AIM: dwTheory david@wheeler.net ICQ: 15726394 http://david.wheeler.net/ Yahoo!: dew7e Jabber: Theory@jabber.org