RE: DBD::mysql...solved

------_=_NextPart_001_01C3667B.7DC52AF0
Content-Type: text/plain;
charset="iso-8859-1"

>If this is the case, there is a patch available, see the last weeks of the
>mailing list archive. In either case, you can safely go on and do a
>"make install".
ah ha. I was thinking it might be ok to install.


>And, please, be so kind to post what you did to get things working.

Sure....


I installed mysql 4.0.14 with rpms (actualy upgraded from .12 to be prescise
I heard there was issues with sorting with .12). At the time I didn't think
I needed the
MySQL-devel-4.0.14-0.i386.rpm
MySQL-shared-4.0.14-0.i386.rpm
RPM's, since I assumed from the name that it had to do with devloping mysql.
I thought it had to do with UDF's or accesing c interpreters for mysql; or
the like. Naming convention not very intuitive....

At any rate, while installing the DBD::mysql I was getting many errors. The
first was that it couldn't find mysql_config. Not knowing that it came from
the 2 rpms listed above, I downloaded/untared the source and found the
script in the bin directory. Simply copying the config script helped, but
other scripts were still missing. So I added the path of the source to my
env and re-made the makefile. This allowed allowed it to create the make
file.

I had trouble with connecting to the database with the default settings.
Then I remembered that I removed the default settings from mysql for
security reasons. So I re-made the makefile with a valid user and a valid
password. This got me to the point where it would connect, but many tests
would fail.

With the scripts not properly installed I had the
> cflags (Users choice) = -I
> libs (Users choice) = /usr/lib/

not set correctly. At this point I found that the other rpm's (see above)
held the scripts that could be installed properly, so I installed them via
the rpm.

At this point I re-made the makefile (with user/pw set)
perl Makefile.PL -testpassword='password' -testuser='user'
This brought me to the point where all but three tests passed.
-6/21 New testab not in DSN list
-10/21DSN testab not in DSN list
-14/21DSN testac not in DSN list
which are explained as:

>These are most probably bugs in the test suite, triggered by the need to
use a password. (

....which is exactly what I did.

So basicly...all of the rpms need to be installed and you need to change the
user/pw when running the makefile.



....hope this info helps.


Cheers,

-jh

------_=_NextPart_001_01C3667B.7DC52AF0--