From: Karsten H. <Kar...@gm...> - 2006-05-24 10:51:33
|
On Wed, May 24, 2006 at 02:21:16PM +1000, Andrew McNamara wrote: > Should pyPgSQL attempt to mitigate this, or just count on Postgresql to > "fix" it?: AFAICT they fixed it already but the fix involves client code having to be modified, so, yes, pyPgSQL needs to be released compiled against an updated libpq to take advantage of that fix. Which may still leave some "application" code having to be fixed, too. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 |