Comments on: perl-DBD-MySQL errors

By: admin

admin — Thu, 07 May 2009 19:30:42 +0000

While this isn’t considered a “permanent fix” it is the best method to get something working as fast as possible to prevent a process from failing. Not to mention that the differences between so.14 and so.15 are so minor and do not in any way prevent the processes from not working or working incorrectly lead me to believe that you’re just another one of those tight ass admins that don’t have to work on thousands of servers and only have to play around on the accounting office’s closet rack of three old white-box servers. There are many ways to accomplish solutions – while this is not perfect, it works. I’d rather have it be the proper version but considering the limitations of the up2date system and the version of mysql running on that server, it’s the best solution. So, until you know all of the facts behind a situation I recommend you keep your opinions to your own blog.

By: Michael Fleming: This should be obvious, but..

Michael Fleming: This should be obvious, but.. — Thu, 07 May 2009 18:43:50 +0000

[...] I also the only person who sees “advice” like this “fix” for a library error and let out a Charlie Brown-esque “AUGH!” (Two good ways to fix this, microbrew to the commenter [...]

By: admin

admin — Thu, 07 May 2009 15:01:26 +0000

This came about when using MySQL-server-percona-5.0.68 on a RHEL4 server. The package manager wanted to install mysql-server-4.1.22 to solve the dependency error. So in this case, there’s absolutely no way I’m installing mysql-server-4.1.22 just because of a small mismatch in the libmysqlclient version. Otherwise I’d agree with you.

By: Mark R

Mark R — Thu, 07 May 2009 08:34:54 +0000

Or you could just build your DBD module against the installed version of libmysqlclient.

If you’re using a sane package manager, it should manage dependencies of this sort for you.