Java world has this <A HREF="/javaworld/jw-01-2000/jw-01-step.html">Map Java objects to database records </A> A two-part series on object database implementation. A nice article. He does a better job of using interfaces, than is in the current OPL code. On some things he doesn't do as well. He doesn't use map to load and unload his internal representation of fields (aka, attributes). So, he gets and puts all fields, not just db fields. He uses members instead of methods for get and set. Scott Ambler suggests using methods, and I agree that this is a better approach. Internally, the class might do some additional work (Scott call them business rules) in the set method. -- george __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
