MYSQL DBI

muizelaar has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: MYSQL DBI by moritz (Cardinal) on Sep 10, 2008 at 15:59 UTC
The usual approach is to use DBI with the DBD::mysql backend. The testing reports for DBD::mysql don't look very bright, but then again it's only one failure for Solaris. Older versions have some success reports for Solaris. Does the client script also run on Solaris, or only the server? If the client runs on a more common platform (such as linux) it might be easier to get the modules installed.	[reply]
Re^2: MYSQL DBI by Illuminatus (Curate) on Sep 10, 2008 at 18:19 UTC
I have used DBD::mysql on Solaris 10 fairly extensively with no problems. Have you already tried this module? Was there some specific problem you experienced?	[reply]
Re^3: MYSQL DBI by moritz (Cardinal) on Sep 10, 2008 at 19:08 UTC
No problem, I just wanted to make sure that I didn't recommend something that doesn't run at all on Solaris, so I mused a bit over the cpan tester reports.	[reply]
Re^2: MYSQL DBI by muizelaar (Sexton) on Sep 11, 2008 at 10:44 UTC
Hi Moritz Both the MYSQL DB and the client scripts are on Solaris. Ill give your suggested modulus a ago. Fingers crossed :) Thanks for your help	[reply]
Re: MYSQL DBI by leocharre (Priest) on Sep 11, 2008 at 14:14 UTC
A sidenote... I've had troubles in the past running DBD::mysql , one platform would work, one would not. I was under the impression, that it was a DBI or DBD::mysql problem- so I checked versions against each other on those systems and against cpan. What was freaking going on.. is that my mysqld / mysql-devel versions were varied. I would get DBI errors for sql queries on one machine and not another. I wasn't realizing that I was really getting errors from two different mysqld database servers.	[reply]