I've used Data::Phrasebook::SQL (or rather, what must have been an older version) with success.

As pointed out, for what you want to do it starts to get really boring maintaining it. After using Phrasebook in my DBI evolution, I switched to ORM. The Perl Object-Oriented Persistence document helped me get started on sorting it all out. Though I think it hasn't been updated in a while, it dosen't mention DBIx::Class or Rose::DB.

If you try the Phrasebook pattern (or something else) and decide it still isn't abstracted enough for you, check out ORM. I suggest starting with Class::DBI and then trying either Rose::DB or DBIx::Class, depending on your requirements.

UPDATE: I guess I should explain what ORM is... simply put, it maps rows in your database to perl objects. And then the idea is when you need to change databases, you just reference a different underlying driver so you don't have to modify your code. It isn't perfect, but the communities behind some of these libraries are pretty large because, well, ORM is "the way".

trwww