| From: | David Stanaway <david(at)stanaway(dot)net> |
|---|---|
| To: | Vlad <marchenko(at)gmail(dot)com> |
| Cc: | Brandon Metcalf <bmetcalf(at)nortel(dot)com>, 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 18:44:46 |
| Message-ID: | 1112985886.19084.8.camel@david.dialmex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
On Fri, 2005-04-08 at 14:12 -0400, Vlad wrote:
> we've noticed that too here and quick explanation is - with the new
> "prepare" implementation, the query get prepared on the server side,
> which is good; the problem is that all of the bind values passed to
> the sql server during execute call are in form of ***varchar***, i.e.
> even if a field is of int type in postgresql table, DBD::Pg passes
> your bind value as char - as a result, postgresql doesn't use indexes.
A work around would be in the sql to cast the param to the appropriate
type.
EG: SELECT * FROM Person WHERE personid = %::int
--
David Stanaway <david(at)stanaway(dot)net>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vlad | 2005-04-08 19:07:04 | Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg |
| Previous Message | Vlad | 2005-04-08 18:40:04 | Re: [Dbdpg-general] benchmarking old Pg and DBD::Pg |