Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <4384CDE1.4050202@serverspy.net>
Date: Wed, 23 Nov 2005 13:15:29 -0700
From: Pierre Smolarek <pierre@serverspy.net>
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: "Philippe M. Chiasson" <gozer@ectoplasm.org>
CC: Perrin Harkins <perrin@elem.com>,  modperl@perl.apache.org,
 pgollucci@p6m7g8.com
Subject: Re: Apache::DBI + DBD::Multiplex
References: <43835219.1070807@serverspy.net> <4383D9D5.2000501@p6m7g8.com>
 <4383EC57.9080709@serverspy.net> <4383ECD1.3000301@elem.com>
 <4384A7BE.1020805@serverspy.net> <4384CA3A.4040204@ectoplasm.org>
In-Reply-To: <4384CA3A.4040204@ectoplasm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Philippe M. Chiasson wrote:
> 2 possible avenues to investigate:
>  - Change your code to not use an array-ref as mx_dsns argument but some string (comma delimited, etc)
>  - Look at changing Apache::DBI to not use the ref as part of the dsn cache key, but use the contents of the array
>    something along the lines of :
>     $Key = Dumper(\@_);
>   

The arrayref is a requirment of multiplex. I'll do some hacking in both 
modules and see what works. I'm not certain if the first possible change 
would work as suggested as Apache::DBI would end up caching possibly 
just one, if any of the multiple potential DB connections. The target 
will be to cache a persistant connection for all DB servers that 
multiplex is setup to query against.

I'm not completly up to scratch when or how Apache::DBI does its magic, 
either within the connect call of my DBI handle or within Multiplex's 
(as multiplex does a similar thing to Apache::DBI in redirecting the 
connect request).

I'll report back any findings.

Many thanks,

Pierre