I often add methods to my Class::DBI code that perform some operation on multiple tables without the caller specifically needing to know that. There's no reason you have to expose the full underlying table structure just to use Class::DBI. Some would say Tangram does a better job of hiding this stuff though.