Re: [Dbdpg-general] bug in DBD::Pg
From: Greg Sabino Mullane (greg_at_turnstep.com)
Date: 03/24/05
- Next message: Richard Rice: "Entering a TimeStamp value into DB2"
- Previous message: Brandon Metcalf: "Re: prepare() bug?"
- Next in thread: David Wheeler: "Re: [Dbdpg-general] bug in DBD::Pg"
- Reply: David Wheeler: "Re: [Dbdpg-general] bug in DBD::Pg"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: dbdpg-general@gborg.postgresql.org Date: Thu, 24 Mar 2005 00:57:05 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> The following reproduces what I believe is a know bug in DBD::Pg 1.40. Is
> there a new version due out anytime soon?
This has been fixed in CVS, and will be in 1.41. We hope to release it in
the next few weeks. Until then, you can specifically bind the parameter
types with bind_param, or you can upgrade your PostgreSQL server (this
bug only affects older versions).
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200503231955
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFCQhBbvJuQZxSWSsgRAgLhAJ4rensdh0afg8ZoH09U60WYBqFgPACeIc8s
VkPPUEwq2C94/HQK+yPI1oI=
=vcCK
-----END PGP SIGNATURE-----
- Next message: Richard Rice: "Entering a TimeStamp value into DB2"
- Previous message: Brandon Metcalf: "Re: prepare() bug?"
- Next in thread: David Wheeler: "Re: [Dbdpg-general] bug in DBD::Pg"
- Reply: David Wheeler: "Re: [Dbdpg-general] bug in DBD::Pg"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
