Re: "Dynamic" database handles?

[prev] [thread] [next] [Date index for 2005/01/24]

Quoting William McKee <william@xxxxxxx.xxx>:

> On Sat, Jan 22, 2005 at 06:47:18PM -0600, Jason Gessner wrote:
>> The problem with C::DBI is that your connection is a module variable
>> and is never reinitialized (unless you force it to be).  What this
>> means is that Virtual host A will start accessing Virtual host B's
>> database if that particular apache child has already been used against
>> virtual host A.  Sucks.
>
> But doesn't this assume that you are using the same module to access
> different databases? If you use a different namespace for each database
> table you are accessing, I would think you'd be spared these headaches.
> I know this is not always feasible, esp. for the type of application
> that the OP was describing.


Yes it does assume that.  However, i most commonly use a config
module/file/directive to configure that stuff if I am reusing modules, so this
bites me if i am not careful.

-jason gessner
     jason@xxxxxxxx.xxx