I hate it when I type "it's" instead of "its". On Wed, Feb 18, 2009 at 8:51 PM, Brian Kotek <[email protected]> wrote:
> Ideally the database structure should have no bearing on the object model. > In many cases the two may be similar, but there are plenty of situations > where they aren't. My advice would be not to couple them unless you have a > good reason. Transfer creates objects that are fairly tied to the database > schema, so for many the tradeoff of having Transfer do a lot of work for you > is worth the coupling. Though you can get around some of that by using it's > Decorators. > > One of the nice things about Hibernate is that it allows a lot of > flexibility in designing the object model because in most cases it can just > generate whatever database schema is needed to support the model. > Essentially, you just say "persist this" and you don't care how Hibernate > does it. > > If you're looking to get something done quickly and want to use Transfer or > one of the other CF ORMs, then fine, but at the least I would say create > your model first, and then figure out what you need in terms of a schema to > allow that to work in Transfer or in your own DAOs and factories. But if > your goal is to learn more about OO design, I would stop thinking about the > database right now. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
