With many OO wrappers you lose the ability to readily take the generated SQL and test it outside of Perl. It also becomes hard to take the SQL to a DBA when trying to figure out performance issues. Or the other way around when the DBA says, "These are our most expensive running SQL statements..." - does no good when you can't find the query.
Yes indeed.
My current job is trying to help a company that uses Apples Web Objects to create java apps. The SQL generated by WO5 is OK in most cases, but sometimes you need to tweak it to get decent behavior, and trying to figure out which part of the OO framework generates which queries, and then figuring out how to fix them is ugly and difficult.
Using an OO framework is great for the programer, and can lead to faster development times. But when it comes to getting good performance from the database itself in a non-trivial app they cause a lot of problems and headaches for the DBA (which is the role I play these days...)
Michael