Dear, A friend recommended me this white paper:
http://www.ambysoft.com/persistenceLayer.html The Author suggests to implement what he called "Robust Persistence Layer" between "Business Classes" and "Storage mecanism" (ex Relational Database"). Here an extrait from the white paper: "This approach to persistence effectively allows your database administrators (DBAs) to do what they do best, administer databases, without forcing them to worry about what their changes will do to existing applications. As long as they keep the data dictionary up-to-date they can make whatever changes they need to make to the persistence mechanism schema. Similarly, application programmers can refactor their objects without having to worry about updating the persistence mechanism schema because they can map the new versions of their classes to the existing schema. Naturally when new classes or attributes are added or removed to/from an application there will be a need for similar changes within the persistence mechanism schema." Is there in Perl's world a way to avoid hard coding SQL in DBI. I would like to have your opinion about this white paper. Feedback appreciated ... Jos�. **** DISCLAIMER **** "This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by other persons than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer". Thank you for your cooperation. For further information about Proximus mobile phone services please see our website at http://www.proximus.be or refer to any Proximus agent.
