|The stupid question is the question not asked|
DBI with 2nd mysql server, nonstandard portby Kozz (Friar)
|on Feb 26, 2005 at 21:58 UTC||Need Help??|
Kozz has asked for the
wisdom of the Perl Monks concerning the following question:
Most wise monks:
I've got a bit of a dilemma on a server which I do not administer, and the actual administrator is very hesitant to upgrade perl and DBI to accomodate my needs. Here's the issue...
I requested an upgrade of MySQL, which he did: MySQL 4.1.9. However, he left the remaining MySQL server installed and running, for safety purposes while considering moving the entire server from the old to the new. He configured the new compile such that the binary is named "mysql4" instead of "mysql", it runs on port 3310 (instead of 3306), and socket file is /var/mysql4.1.9/mysql.sock.
Here's more version information:
I'm trying to get a perl script using DBI to connect to this OTHER server on port 3310 (not the mysql 3.x on 3306). Simply specifying "port=3310" in the $dsn doesn't seem to do anything -- it connects to the "old" mysql server. Only when specifying
Is there any way to get this script with these versions of DBI, DBD::mysql to play nice with this new version of MySQL? My guess is that DBD::mysql is some sort of direct interface with the "mysql" binary, but I need it to use the binary named "mysql4". Can I hack things so it works properly?
All monks input is welcome and appreciated!