There is Class::DBI::Oracle which could be used also, in place of Class::DBI (it subclasses Class::DBI).

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.