If/where you find sub-optimal SQL in Class::DBI, simply replace it inside Class::DBI::Oracle. When you've made some nice improvements, send in a patch so the rest of us can benefit.
Look at Class::DBI as a starting point rather than an ending point.
In reply to Re^4: Class::DBI not intuitive
by drago99
in thread Class::DBI not intuitive
by Jaap
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |