FYI, I think I remember accidentally having some tracing in when fixing a memory over-run issue, but: it could also be your ODBC driver tracing calls (I doubt it, but I'm trying to be complete). If upgrading doesn't resolve, then please check if you have DBI's tracing on (but you'd get a lot more information) and/or your driver's tracing. If none of those resolve the issue, post your exact configuration, including your platform (linux, unix, nt, etc) ODBC driver Manager & Version and your ODBC driver & version information.
Regards, Jeff > -----Original Message----- > From: Jeff Urlwin [mailto:jurlwin@;bellatlantic.net] > Sent: Monday, October 28, 2002 12:55 PM > To: Chris Wesley; [EMAIL PROTECTED] > Subject: RE: :ODBC & output from ->execute() > > > It's probably some debug code I left in by accident. Please try 0.45_18. > > Regards, > > Jeff > > > > > > > DBD::ODBC (v0.43) and Perl (v5.6.1) > > > > Whenever I execute() an SQL statement using DBD::ODBC, I get on > STDERR the > > SQL statement being executed. This is odd to me since I don't get this > > output when using other DBI drivers (like DBD::Sybase and DBD::mysql). > > (For instance: > > my $dbh = DBI->connect(dbi:ODBC:myDSN); > > my $sth = $dbh->prepare( "SELECT * FROM FOO" ); > > $sth->execute(); // output on STDERR, I get "SELECT * FROM FOO" > > $sth->finish(); > > ) > > > > Can anyone help explain why this is happening, and how to disable it > > (other than by redirecting STDERR to /dev/null)? > > > > THX, > > ~Chris > > > > > > >
