> Bad generic advice. You should use persistent connections when it
> makes sense to use them.
>
> BLH> Whether or not you use mod_perl is irrelevant.
>
> It is relevent if you want to use Apache::DBI.
Ouch!
I was a bit more specific in my follow-up email which I sent direct since I didn't
think it was necessary to post it to the list, but I may have been mistaken. It's
difficult to provide detailed advice when you don't have all the information, so I did
my best.
Subject: Re: DBI
Date: Fri, 05 Jan 2001 17:56:53 -0500
From: Buddy Lee Haystack <[EMAIL PROTECTED]>
Organization: www.RentZone.org
To: Joe Grastara <[EMAIL PROTECTED]>
References: 1
When I first "migrated" from a Windows environment, I was absolutely amazed at how the
Unix people cobbled together independent pieces of software to solve systems
integration
issues that plagued me in corporate americana.
A couple of issues.
When you use the Apache DBI module to maintain persistent connections to your database,
each Apache child process inherits one of the database handles, and caches the
connection. This means that your database will have to be able to have one database
connection open for each Apache child process running. If you have Apache configured to
spawn 20 child processes, the database your connecting to will have to be able to
handle
at least the number of connections opened by just the single webserver.
I use PostgreSQL, which is compiled to handle just over 30 open connections. My website
uses 20 of those connections, which allows just over 10 other people to open up
connections to the database.
There is some undocumented command in DBI that will allow you to open a connection with
the Apache DBI module installed, but not cache the connection. I used this to connect
to
an HR database that was rarely ever accessed.
ENJOY!!!
--
www.RentZone.org
