perlquestion dragonchild (This is more of a general design question vs. a specifically Perl question.) I'm trying to work on decoupling the application I'm working on from its database. The goals here are: <ul> <li>Minimize the impact of schema changes on the business logic as well as the control structure <li>Bring together all SQL so that the business and controller logic aren't dealing with the underlying implementation of how the data is stored. </ul> My problems are thus: <ol> <li>I know that I want to bring all the SQL together, so having every SQL call wrapped in a function is easy enough. <li>But, I know I'll end up with a ton of individual SQL_ functions with very little way to navigate through them. <li>At first glance, every single SQL call will be in some SQL_ wrapper, even if there's a minor change (such as sorting and the like) </ol> Have people worked out some idea of data structures to pass back and forth? I'm not so worried about memory or CPU as I am in cohesion and coupling. ------ We are the carpenters and bricklayers of the Information Age.Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.