in reply to
Re: Help prevent a ModPerl application from replacement by Java
in thread Help prevent a ModPerl application from replacement by Java
The profiler data (posted with the original question) states this. But I'll have a hard and dull drawback on not using it: my column names and table names are not intuitive nor easy to guess. This would be a pain to write SQL to them. But it seems better than dropping Perl in favor of Java.
My hope is not need to do this. Maybe someone have a good suggestion that allows my Perl to fly...