Connecting to "test" mysql

am 06.03.2004 18:03:23 von beau

Hello -

On one Linux machine, I recently installed a 'test'
mysql server (5.0 - bit keeper). I have a 'production'
mysql server (4.0.18) on that machine also.

On production: bins in /usr/bin/mysql, libs in /usr/lib,
unix socket in /tmp/mysql.sock, tcp port 3306.

On test: bins in /home/test/usr/bin,
libs in /home/test/usr/lib (LD_LIBRARY_PATH setup),
unix socket in /home/test/var/lib/mysql/test-mysql.sock,
tcp port 3308.

Logged in as user 'test' (with the test environment in place)
the 'mysql' utility works properly; the test database
is used. However DBD-mysql (from my perl scripts) accesses
the production server; but the test suite (make test) correctly
accesses the test server.

In my perl scripts, I use the 'standary' connect string, i.e:

connect( 'dbi:mysql:some_database', etc... );

The connect connects to the production server; If I take the
production server down (and leave the test server up), I get
an error message:

unable to connect ... no socket in ('/tmp/mysql.sock') ...

I guess I don't understand how DBD-mysql 'finds' a server to
use. I thought I had it setup so he would find the test
server.

Can someone please explain?

Aloha = > Beau;

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org

Re: Connecting to "test" mysql

am 06.03.2004 22:24:42 von Rudy Lippan

On Sat, 6 Mar 2004, Beau E. Cox wrote:

> On one Linux machine, I recently installed a 'test'
> mysql server (5.0 - bit keeper). I have a 'production'
> mysql server (4.0.18) on that machine also.
>
> On production: bins in /usr/bin/mysql, libs in /usr/lib,
> unix socket in /tmp/mysql.sock, tcp port 3306.
>
> On test: bins in /home/test/usr/bin,
> libs in /home/test/usr/lib (LD_LIBRARY_PATH setup),
> unix socket in /home/test/var/lib/mysql/test-mysql.sock,
> tcp port 3308.
>
> Logged in as user 'test' (with the test environment in place)
> the 'mysql' utility works properly; the test database
> is used. However DBD-mysql (from my perl scripts) accesses
> the production server; but the test suite (make test) correctly
> accesses the test server.
>
> In my perl scripts, I use the 'standary' connect string, i.e:
>
> connect( 'dbi:mysql:some_database', etc... );
>
> The connect connects to the production server; If I take the
> production server down (and leave the test server up), I get
> an error message:
>
> unable to connect ... no socket in ('/tmp/mysql.sock') ...
>
> I guess I don't understand how DBD-mysql 'finds' a server to
> use. I thought I had it setup so he would find the test
> server.
>

You can get DBD::mysql to read your my.cnf by adding a default_group
connect string. Or you can specify the socket (udp || inet) in the connect
string

Rudy

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org

Re: Connecting to "test" mysql

am 06.03.2004 22:24:42 von Rudy Lippan