Hi Philip, On Nov 27, 2006, at 11:16 PM, Philip M. Gollucci wrote:
Lev Lvovsky wrote:Hello - this may be a question unrelated to mod_perl so much as it is related to DBI and mysql, but any suggestions would be appreciated greatly!What versions of Apache-DBI, DBI, mysql ?
perl-Apache-DBI-1.01-1 perl-DBI-1.52-1.fc5 perl-DBD-mysql-3.0008_1-1 MySQL 5.022 for all mysql related RPMs
In testing out persistent connections while using transactions, we've noticed that while in a loop which continuously begins and ends a transaction, killing the persistent connection which Apache::DBI is maintaining causes the still-running handler to report things like: error: DBD driver has not implemented the AutoCommit attribute at / usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/DBI.pm line 1668. In dumping the status of the handle after this has been done, the AutoCommit flag is no longer there either.$Apache::DBI::Debug = 2; $dbh->trace('file', 4);
will try this.
In the case that this happens, is there any way other than restarting the apache process to correct this issue (simply setting AutoCommit to 1 doesn't work as it's a tie'd variable).Seems like your Apache::DBI::ping() method is busted which I know was been tweaked -1-2 times recently.1.00_01 05/29/2006 - Fix a () bug in the connect() determining whether we must ping the database. PingTimeOut = 0 now works as documented. Submited by: [Joe Thomas <suppressed>] Contributed by: [Patrick Mulvany <suppressed>] Also, relating to AutoCommit being 'reset' 0.100 08/10/2005 - Move $Idx from a file-scoped variable to a connect() scoped variable, which gets passed to other subroutines as needed. This will ensure that the cleanup/rollback feature will work properly when a script uses more than one database handle to the same database. [Joe Thomas <suppressed>]
sorry, was this a fix, or a changed needed on our end? thank you for your help! -lev
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.