Re: upgrading DBD::Pg without client libs

I am surprised DBD::Pg even works if the client libs aren't present. Perhaps it was linked statically. Or maybe you mean that the libraries and headers for development weren't installed but the shared libraries were. Why can't you install the client development libraries?

Another option is to build DBD::Pg on another machine with the devel libraries and copy it over. The hard part is finding all the files and installing them in the right place. It is important that you get the same version of the libraries on the build machine as the database server.

Upgrading DBD::Pg won't fix the problem. It was a change in version 7.3 to not allow empty strings for integer columns. The solution is to not pass empty strings for integer columns.

Comment on Re: upgrading DBD::Pg without client libs

Replies are listed 'Best First'.
Re: Re: upgrading DBD::Pg without client libs by jfroebe (Parson) on Apr 08, 2004 at 01:35 UTC
That's what I get for about 1 minute of research ;-) No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1	[reply]
Re: Re: upgrading DBD::Pg without client libs by geektron (Curate) on Apr 08, 2004 at 04:47 UTC
Upgrading DBD::Pg won't fix the problem. It was a change in version 7.3 to not allow empty strings for integer columns. The solution is to not pass empty strings for integer columns. well, eventually i should upgrade DBD::Pg, but i combed through the code today and found where the empty strings are passed and fixed them. i was hoping that DBD::Pg would have possibly addressed the issue as well ... oh well.	[reply]