You will probably notice in your error logs, some database handle destroyed messages, or active statements destroyed. Although these errors do not cause any problems in the program ( I know at times it seems like they do), they are still annoying because they fill up the error log. The errors come from 'use strict' which I have to use if I want the program to run under mod_perl,
and not finishing up all the statements before disconnecting or running another query.
I was hoping to have all of these cleaned up before I made the next release public, but they are still hanging around. Running under mod_perl, fixes these little errors, but I realize that everyone cannot run under mod_perl. So eventually, when things settle down I will work on getting all of these cleaned up and release the cleaned version before I start making any new additions.
---
'If it's worth doing, It's worth doing loudly'
Scream
http://www.screamingweb.com
