Darren,
Thanks for the suggestion. I tried that today and noticed the same behavior.
This is not surprising as both are using DBI internally to get the connection.
All httpd processes point to the same DBH after connection. Should they or
should each process have a unique address returned by
Instead of using Apache::DBI directly, I recommend using the CPAN module
http://search.cpan.org/dist/DBIx-Connector/ instead, which is focused on
handling your use case effectively. -- Darren Duncan
Schultz, Len wrote:
I've run into an issue when stress testing mod_perl that the database
conne
I've run into an issue when stress testing mod_perl that the database
connections are going away. I suspect that processes are sharing
database connections, causing the issue.
But I've followed all instructions for Apache::DBI, and can't figure
this out.
I'm making the connections in the child pr
On 19/05/2012 13:33, pe...@vanroose.be wrote:
DBD::ODBC is returning strings for integers. This results in incorrect values
for bit wise operators. (for ex:- $e='16'; $f = '32' print $e& $f returns
12 instead of zero ). Is there a setting that can help us return integers as
'integers'.
It's
> DBD::ODBC is returning strings for integers. This results in incorrect values
> for bit wise operators. (for ex:- $e='16'; $f = '32' print $e & $f returns
> 12 instead of zero ). Is there a setting that can help us return integers as
> 'integers'.
It's safer (and easier) to make your perl co
