The problem I'm trying to solve is this:
I have an Oracle DB. The schema is... complex. More complex than it needs to be. When we can get funding, one of our "todos" is to refactor the schema and make it something easier to access and maintain. In the meantime, there's a new project coming down the pipe that wants me to create an interface between a third-party application and that Oracle DB. Obviously, if we refactor the DB, I don't want to rewrite all of that integration code. Also, I'm pushing to do a full rewrite of the application that sits in-front of this DB anyway (it's in classic ASP). If I get the go-ahead to start that project, I'd like to be able to reuse the code from this integration project.
I want to take the "meet-in-the-middle" approach. I'd like to build the object model for the app-side without thinking about the database. I'd like a lightweight mapper to link that abstract model back to the more concrete database. The big hurdle is the fact that, when the DB schema changes, it will probably be nigh unrecognizable. Keeping the object model and the DB in sync through mapping may be too ambitious.