Sherm, Your concerns are understood. Actually, I created the database tempdb sometime earlier (it's inline with a best practice at my company). The user 'tmp' and password 'XXXXXX' are fabrications. The real user and password I used are different; however, the account has `all` permissions to the table.
I'd be glad to re-run the `make test` again. Are there any adverse affects if I do? On 7/16/04 8:12 AM, "Sherm Pendley" wrote: > On Jul 15, 2004, at 9:51 AM, Adam wrote: > >> My test (make test) still failed (only returned a 5.86% pass). > > No guarantees without seeing the test results, of course, but the most > likely cause of the failures - especially given that your own test > script succeeded - was the testdb and testuser options you gave: > > perl Makefile.PL \ > --testdb='tempdb' \ > --cflags='-I/usr/local/mysql/include -O3 -fno-omit-frame-pointer' \ > --libs='-L/usr/local/mysql/lib -lmysqlclient -lz -lm' \ > --testuser='tmp' \ > --testpassword='XXXXXX' \ > --testhost='localhost' > > The options above will create test scripts that try to connect to a > database named 'tempdb', and log in as user 'tmp'. Neither that > database nor that user exists by default, so unless you created that > database and granted the appropriate permissions on it yourself, those > tests would fail. > > You could set this up by logging into mysql and using a few SQL > commands: > > mysql> create database tempdb; > Query OK, 1 row affected (0.04 sec) > > mysql> grant all privileges on tempdb.* to [EMAIL PROTECTED] identified by > 'xxxxxx'; > Query OK, 0 rows affected (0.11 sec) > > mysql> flush privileges; > Query OK, 0 rows affected (0.05 sec) > > mysql> exit > Bye > > A more common option is to use the 'root' user and 'test' database, > which are both created by default when MySQL is installed: > > --testdb='test' \ > --testuser='root' \ > --testpassword='xxxxx' > > sherm-- > Regards, Adam
