On Sat, July 14, 2007 2:40, Martin J. Evans said: > Alexander Foken wrote: >> Is there a special reason why you do not use DBD::Pg? It should be >> faster because it has less overhead and it supports Unicode better >> than DBD::ODBC, should you need it. DBD::ODBC has seen no update since >> about three years, while the current DBD::Pg is just one year old. >> >> Alexander >> > Just so everyone on the list knows. I did a development release of > DBD::ODBC (1.14_1) a little over a week ago. You can find it on cpan. It > fixes all bugs I know about except one on rt.cpan I have not sufficient > info as yet to look at. If anyone knows of any other issues please > report them on rt.cpan and I will look in to them. Unless I hear from > anyone I'll release 1.14 properly late next week. > > Martin >> On 13.07.2007 00:11, Craig Metzer wrote: >>> I'm having trouble installing DBD::ODBC 1.13 on a system with >>> postgresql. It appears it's because it can't find the sql.h, >>> sqlext.h, etc. headers. I installed the developer and library >>> packages that were supposed to contain these headers. Could someone >>> please tell me what I'm doing wrong or where to find the headers? >>> >>> TIA, >>> Craig >>> Please excuse my ignorance, but is DBD::ODBC still limited to one running query through each Database Handle at a time? That is $sth=$dbh->prepare(...); $sth->execute; $sth1=$dbh->prepare(...); $sth1 will invalidate $sth's result set. Stubbed my toe on this when I was trying to apply DBD::mysql to DBD::ODBC (target MS-SQL server). Of course that was a number of years ago.
Thanks. Bill
