| From: | "Brandon Metcalf" <bmetcalf(at)nortel(dot)com> |
|---|---|
| To: | Vlad <marchenko(at)gmail(dot)com> |
| Cc: | David Stanaway <david(at)stanaway(dot)net>, dbdpg-general(at)gborg(dot)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg |
| Date: | 2005-04-08 19:10:33 |
| Message-ID: | Pine.LNX.4.58L.0504081408060.18466@cash.rhiamet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
m == marchenko(at)gmail(dot)com writes:
m> it's acceptible (actually better in form of passing columns type via
m> bind_values) as a quick workaround for a small scripts only. Actually
m> as a quick workarround it's easier to downgrade DBD::Pg.
m> Think of numerouse DB-OO Mappers and Object Persistance tools... it
m> won't be easy to fix all of them. As of right now a lot of times you
m> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-08 19:11:49 | Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg |
| Previous Message | Vlad | 2005-04-08 19:07:04 | Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg |