Hi all, I have been recently working through updating an old application and making it better behaved in terms of object orientation. The application has a variety of REALSQLDatabase tables that I need to read in and display, and as I have been updating I have been creating a set of classes that effectively model the data. The further I have gone the more I think that actually I should be abstracting the whole process of what is effectively ORM - I have a whole range of (probably highly redundant) methods now for (for example) reading the columns from a row of table tA and and instantiating object oA. I can do (well I have been doing) this myself, and could probably sort out an abstract process for doing it more tidily, but I wanted to know whether there are some exemplars of good practice in taking a data model and generating the appropriate classes (with properties, accessor methods and so on), handling the inserts, updates, deletes and so on.
Any pointers would be very welcome. Regards, Ian. -- Ian Piper [EMAIL PROTECTED] skype: ianmpiper -- If I'd asked people what they wanted, they would have said faster horses (Henry Ford) _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
