Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <0F6E79F9-9402-4428-8F1E-2A64D4D2D9CD@sonous.com>
References: <0F6E79F9-9402-4428-8F1E-2A64D4D2D9CD@sonous.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B002F2B7-D657-48D2-A82C-4B05D756BBBE@sonous.com>
Content-Transfer-Encoding: 7bit
From: Lev Lvovsky <lev@sonous.com>
Subject: Re: DBI AutoCommit goes away when db connection is killed
Date: Mon, 27 Nov 2006 23:23:35 -0800
To: modperl@perl.apache.org

I forgot to mention also that we're not using a startup.pl file, but  
instead connecting to the DB several times using several different  
accounts as a specific virtual host requires.  At the risk of  
pointing out the answer for myself, does this adversely affect anything?

thanks,
-lev

On Nov 27, 2006, at 10:45 PM, 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!
>
> 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.
>
> 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).
>
> thank you for any help you might shine on this!
> -lev