Linked by Eugenia Loli-Queru on Sat 10th Dec 2005 19:25 UTC
An unwritten consensus in the IT industry is that data shared between object-oriented software and relational databases is best exchanged with object/relational (O/R) mapping frameworks where the entity relationship (ER) model follows the object-oriented model. This article proposes a reversed, lightweight approach supported by a small framework called Amber.
Thread beginning with comment 70922
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:I would think twice before using it. I've read the article and the code he's written is very slow, because it uses n+1 query to load an object and its dependent childs (the jedi and the fighters).
Hibernate on the contrary would issue a single query with an outer join and return the object properly formatted (one parent, many childs). This plus the ability to cache prepared statements should provide quite a performance boost compared to the silly example provided in the article.
Maybe Amber has a way to deal with the n+1 problem, I don't know, since there is no web site with public documentation, but claiming high performance and then falling in the most common performance trap in O/R mapping is rather dumb...
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
Gotcha. I understand where your are coming from. My experience is with companies that commit to one DB Vendor to maintain all their data internally. To me, at least currently, this would be a great solution, but I can see how it might not be as easily accepted for multi-DB use.