in reply to Re: DBD Drivers query
in thread DBD Drivers query

Sutch, this works exactly the same for me.

Once I removed that line I get 

Driver: ExampleP

Driver: Multiplex

Driver: Proxy

Driver: mysql

[download]

Does this glitch have any affect on any of the drivers (in particular mysql). Are these driver working functionaly, as normal, in other words will i have any problems using these drivers later on?

Replies are listed 'Best First'.
Re: Re: Re: DBD Drivers query
by sutch (Curate) on Apr 06, 2001 at 17:38 UTC
    Without reading up too much about why DBD::Proxy may be choking on the data_sources call, I did find that DBD::Proxy should not have any effect on Mysql. From the DBD::Proxy documentation:

    DBD::Proxy is a Perl module for connecting to a database via a remote DBI driver.

    This is of course not needed for DBI drivers which already support connecting to a remote database, but there are engines which don't offer network connectivity.

    I would suggest limiting your data_sources method calls to only driver(s) that your are going to use. For example, use a conditional such as if ($driver eq 'mysql') so that only the mysql driver is queried for data_sources.

[reply]
[d/l]
      That is what i have done.

      Also note that DBD::Multiplex also has a problem with datasources!!
[reply]

In Section Seekers of Perl Wisdom