Hello everyone,
In a follow up to my post last week ("mod_perl using different ODBC
driver manager") I have concluded that for some weird reason mod_perl
seems to want to use the unixODBC Driver Manager instead of the iODBC
Driver Manager....is there some environmental variable that can force
mod_perl to use iODBC? My perl scripts have no problem accessing the
connections, just when they are run under mod_perl.
The following script run from the command line produces the correct
output, showing all of the connections available. If I run it under
mod_perl (via Apache::Registry) only the Mysql connections which were
started by Apache::DBI in my startup.pl are shown.
#!/usr/bin/perl
use Apache::DBI; #commented out for command line run
use DBI;
use DBD::ODBC;
use DBD::Proxy;
$|=1;
print "Content-type: text/plain\r\n\r\n";
map {
print "Data sources for $_: " . join("",
DBI->data_sources($_)). ""
}
grep(!/ADO|template/, DBI->available_drivers);
I can't see the other because it's looking in the unixODBC Driver
Manager instead of iODBC.
I've looked high and low and there is simply nothing with mod_perl
connecting to ODBC sources in the archives.
Can anyone please help? I have no where else to go....other than
failure.
Thanks,
Kevin
--
Kevin Old <[EMAIL PROTECTED]>
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html