I also choose Class::DBI.

I work for a Java shop, where c# is getting its way into this small peaceful world. It seems to me very normal to go Class:DBI. In my shop (or in the Java world), when we access database through Java, all data are wrapped in DCO (Data Container Object, and obviously they have bunch of getters and setters, for you to retrieve each column), and all access methods (select/update...) are wrapped in DAO (Data Access Object) object. Class::DBI has a very close idea behind, and makes great sense to me.