You want an interface to the database. How much of the complexity of the database do you want your interface to give you access to? Do you want to be able to manipulate data in the database, or just display some of it? Do you wish to integrate this tool with the schema of the database? Do you wish to integrate constraints in some efficient way? And how should it scale? To updating 10's of millions of rows of data at once? To hundreds of simultaneous users? (That tends to conflict with manipulating lots of data at once.)

Until you nail down some of these significant details, it is hard for me to understand what you want to do. What you are describing could mean anything from Microsoft Access down to a module for displaying query result sets. I don't think that any one solution can effectively address all of the possible desires (certainly if I could dream of that solution, then I'd expect it to exist already).

Perhaps a better place to start is to think through some "use cases". Imagine that you had your module. How do you envision using it and what would the result be? Envision the usage in enough detail and you have a pretty good idea what the API should be. Envision what the result is in enough detail and how to start writing it will start falling into place. (Or, more likely, you will be able to recognize what you are looking for as being something that is already on CPAN.)