Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg - Mailing list pgsql-interfaces

From Brandon Metcalf
Subject Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg
Date
Msg-id Pine.LNX.4.58L.0504081408060.18466@cash.rhiamet.com
Whole thread Raw
In response to Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg  (Vlad <marchenko@gmail.com>)
List pgsql-interfaces
m == marchenko@gmail.com writes:
m> it's acceptible (actually better in form of passing columns type viam> bind_values) as a quick workaround for a
smallscripts only. Actuallym> as a quick workarround it's easier to downgrade DBD::Pg.
 
m> Think of numerouse DB-OO Mappers and Object Persistance tools... itm> won't be easy to fix all of them. As of right
nowa lot of times youm> get screwed if you upgrade DBD::Pg to 1.40-1.41.
 

When you say downgrade DBD::Pg, is there a version that doesn't have
this problem?  That is, the problem of everything being treated as
SQL_VARCHAR?


-- 
Brandon


pgsql-interfaces by date:

Previous
From: "Brandon Metcalf"
Date:
Subject: Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg
Next
From: Tom Lane
Date:
Subject: Re: pg.py under Mac OS X