NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
Purdy (2383)
Purdy
jasonNO@SPAMpurdy.info
http://purdy.info/
AOL IM: EmeraldWarp (Add Buddy, Send Message)
Yahoo! ID: jpurdy2 (Add User, Send Message)
Bleh - not feeling creative right now. You can check me out on PerlMonks [perlmonks.org].
jasonNO@SPAMpurdy.info
http://purdy.info/
AOL IM: EmeraldWarp (Add Buddy, Send Message)
Yahoo! ID: jpurdy2 (Add User, Send Message)
Bleh - not feeling creative right now. You can check me out on PerlMonks [perlmonks.org].
Friday November 02, 2001
10:51 AM
Found out what was going on w/ MySQL!
For some reason, MySQL ignores your port specification unless you specify a hostname. It assumes without a hostname that you're wanting to connect to the localhost AND through the UNIX socket instead of TCP/IP. I'm no networking genius, so I don't know if that summed it up right, but to fix it, I just had to put in the DSN:
DBI:mysql:database=$db;hostname=www.myhost.com;port=3309
Then I had to grant privs to the username connecting from the host and voila! I had a script if placed on one place in the server connected to a development db server and if it were somewhere else, connected to the production db server.
happy happy joy joy!
As always, thanks go out to the fine chaps @ PerlMonks!
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Found out what was going on w/ MySQL! 0 Comments More | Login | Reply /