--- "Ramon Leon" <[EMAIL PROTECTED]> wrote: > [...] In the java community, I'm pretty sure most people > just use existing open source object mapping layers, in > the .NET world, most are still hacking up their own > private implementation because there isn't any really > outstanding open source implementations yet.
In other words, put all persistence code in /one/ place -- not one per business class. Most per-class logic will be data driven, and hence generic. > --- From: Stede Troisi [mailto:[EMAIL PROTECTED] >> I was thinking about YAGNI yesterday. [...] >> [...] if I want to persist to something different (like >> a flat file) I can create a new class to handle it while >> leaving the domain class intact. *This* is the right point to say "You Aren't Going to Need It" -- *don't* complicate your design now with the justification that, "Some day we might want to persist to XML instead of the database." >> Is this how most people solve the problem or is there >> a better solution? Sure there's a better solution: Object Prevalence. Don't persist your objects to a relational database. You don't need it. ;-> http://www.prevayler.org/wiki.jsp?topic=PrevalenceSkepticalFAQ To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/extremeprogramming/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
