On Tue, Jun 24, 2008 at 3:32 PM, Mark Mandel <[EMAIL PROTECTED]> wrote: > I don't know if I entirely agree with this, in that if you start modelling > first, and then build a DB that will support that model, and ORM / code > generator will give you the OO model you want.
Agreed. I'm in an environment where I can still design and build a decent OO model but have a seasoned DBA construct the schema and then I can map between the two - the whole point of ORM really. > That being said, if you have > a legacy DB, or you start developing DB first, then, yup, you will have to > jump through some hoops to get to where you want to go OO wise - or you may > not get there at all. And what a lot of people seem to forget (or not want to deal with) is that you can always write adapter objects to enable your nice, clean, well-designed business object model to map onto a (completely different) nice, clean, well-designed relational data model. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
