Voytek,
You are strongly urged to read the README file that comes with the Mysql
module.
In my previous email I mentioned the possibility of backwards incompatibility
problems. Voila ... the README states the following:
COMPATIBILITY ALERT
The statement attribute *TYPE* has changed its meaning, as of
Msql-Mysql-modules 1.19_19. Formerly it used to be the an array of
native engine's column types, but it is now an array of portable SQL
column types. The old attribute is still available as *mysql_type*
or *msql_type*, respectively.
and there is more about the "moving target" that is this DBD module.
Anywho, on to your questions ...
Voytek wrote:
I've tried updating DBD::mysql
it attempt to log on to the mysql server, but fails, as it needs the password
- how can I pass valid password to the 'Making, testing and installing
DBD::mysql ..' routine ?
-----
Failed 16/18 test scripts, 11.11% okay. 725/732 subtests failed, 0.96% okay.
make: *** [test_dynamic] Error 2
/usr/bin/make test -- NOT OK
Running make install
make test had returned bad status, won't install without force
-----
The README file in the tests directory talks about setting the username
and password for testing, if you do not like the defaults:
- set the dsn, user name and password for test purposes in
"mydriver.dbtest", if the defaults aren't good for you. The
default is
$::test_dsn = $ENV{'DBI_DSN'} || "DBI::$::driver:test";
$::test_user = $ENV{'DBI_USER'} || "";
$::test_password = $ENV{'DBI_PASS'} || "";
Thus, you should be able to set the username and password in the shell
before running make test:
export DBI_USER=whatever
export DBI_PASS=some_password
or, should I do a forced install ?
Many do chose this option :(
cheers
rickw
--
_________________________________
Rick Welykochy || Praxis Services
People who enjoy eating sausage and obey the law should not watch either being
made.
-- Otto von Bismarck
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
