On Friday, February 21, 2003 at 2:36:49 PM, Thomas wrote: >> Whoever wrote this article: Do you have contact to the authors of DBI >> and DBD::ODBC to fix the problems in future?
> I wrote Jeff Urlwin a mail and he intended to have a look at this. > Furthermore he was interested in the errors reported by Jeroen, who > probably wrote http://sapdb.2scale.net/moin.cgi/PerlDbiDbdOdbc, or? Yeah, I wrote that. We just tried the 1.04 version of DBD-ODBC (with DBI 1.25), but at make test we get: t/02simple..........dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 11, 13, 19 Failed 3/19 tests, 84.21% okay Now I was used to test 13 failing because we don't use a driver manager, but this is 3 subtests failing. Errors I get: "my" variable $dbh2 masks earlier declaration in same scope at t/02simple.t line 183. DBD::ODBC::st fetchrow failed: [SAP AG][LIBSQLOD SO]Data truncated. (SQL-01004)(DBD: st_fetch/SQLFetch (long truncated DBI attribute LongTruncOk not set and/or LongReadLen too small) err=-1) at t/02simple.t line 202. DBI->connect(DSN=sapdb) failed: [SAP AG][LIBSQLOD SO]Data source name not found and no default driver specified. DBI->(SQL-IM002)(DBD: db_login/SQLConnect err=-1) at t/02simple.t line 183 Can't call method "disconnect" on an undefined value at t/02simple.t line 185. The problem with DBI > 1.25 seems to be more subtle as it is very hard to reproduce but it is serious and clearly visible on our production systems. I am not sure if it is SAP DB specific, but I suspect it was introduced with the C-implementations that were introduced after 1.25, but that's just a guess... > The ping method was changed due to problems with Openlink. The old method > (still in the module, oldping) sends a simple select to the db and > evaluates the intended error message. The new ping calls SQLTables, which > results in a quite expensive SQL statement disturbing caches etc. It would be very nice if DBD-ODBC would use the old method if SAP DB was detected, as this has a negative effect on performance with cached connections. >> As DBD::ODBC is mentioned as your current official Perl connector it >> should really be fixed. > When I have time I will try the current versions of DBI and DBD::ODBC. Please do, maybe it's possible to include them in some way in your QA with new releases? Regards, Jeroen Boomgaardt _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
