tag:blogger.com,1999:blog-6927558.post6202333166785431460..comments2023-08-29T10:30:31.267+01:00Comments on Biofractal: An Irrational Love of the Relationalbiofractalhttp://www.blogger.com/profile/11229842750489025189noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6927558.post-50600894021726418022010-09-08T00:10:02.781+01:002010-09-08T00:10:02.781+01:00There are many tools available that make translati...There are many tools available that make translation between OO and RDBMS easy (hibernate for example). The power of RDBMS is being hughly underestimated here and it's maturity+stability totally forgotten about. SQL's simplicity is also never mentioned.<br /><br />You never mention how you query an Object Database?<br />Also, what if you need to add a new field to an object. You may have millions of objects that need modified, how does this happen?<br /><br />Part of the success of SQL and RDBMS is that it allows you to manipulate data in ways you didn't think of when you designed the db schema.<br /><br />Your comment that you know your report designs up front seems somewhat naive and totally none agile. There's a very good chance the report design will change whilst your coding your object model (probably several times), also over the course of an application lifetime, business is in constant flux, and therefore the chances are your reports will be too. Agile is about be able to quickly adapt. Taking your YAGNI approach will mean a rewrite at possible the same cost and time as the original. <br /><br />For me, I'm not convinced, but I'll watch this approach mature before commiting.Anonymousnoreply@blogger.com