So, has anyone else done an app using a combination of transactional and
non-transactional tables in MySQL? The problem I'm having -- which is
more like an annoyance than a problem -- is that I keep getting this
message in my logs:
DBD::mysql::db rollback failed: Warning: Some non-transactional
Perrin Harkins wrote:
So, the question is, what's an elegant way to eliminate this warning? I
could modify Apache::DBI to do it (although filtering a specific
warning, as opposed to simply turning them all off temporarilly, could
be a pain). I could install a WARN handler. Ick. Any other brigh
On Tue, 2003-11-11 at 13:50, Douglas Hunter wrote:
> I don't know if it qualifies as a bright idea, but could you implement a
> filter class using tie?
Thanks for the suggestion. That's a neat trick, but it feels like
overkill for this purpose. I think I'm going to end up just turning off
warni
On Tue, 2003-11-11 at 14:55, Perrin Harkins wrote:
> I think I'm going to end up just turning off
> warnings for that one line in Apache::DBI.
In case anyone is curious, this doesn't work. What does work is adding
"local $dbh->{'PrintError'} = 0;" right before that line in
Apache::DBI. A better
