Re: DBD::mysql odd behavior

On Tue, 5 Aug 2003, Jochen Wiedmann wrote:

> Whether to like environment variables or not, is a matter of taste. My
> personal feeling is that it doesn't matter how the configuration occurs,
> but I strongly encourage that all configuration is left in one place,
> which is Makefile.PL, as it is now.
>

Well it might be nice to be able to override the Makefile options at test
time, but I don't see much need for that, but on the other hand DBD::Pg
uses the DBI_DSN et al. at test time to set up the test env.

I am thinking the best route would be to add test* options to Pg and make
the DBI_ env vars work in mysql. That way I don't have to remember as much
when bouncing between drivers :)

Thoughts?

> What you probably aren't aware is that there already is a possibility
> for automated installs, which is the mysql_config script. The main
> idea is to have a custom mysql_config script which is internally using
> the MySQL script with the same name to reply to --libs or --cflags,
> but also listens to --test-user and the like. See "perldoc DBD::mysql::Install"
> for details.
>

The usage message gives better info about mysql_config --testuser then the
INSTALL.pod which I guess needs updating so that it enumerates all of the
flags which it might call mysql_info with -- Added to the TODO.


Rudy


--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org