You are currently browsing the category archive for the ‘OR/M’ category.
I’m reviewing my presentation about Entity Framework V1.0: in particular I’m concentrating on introduction, positioning correctly the problem that is:
Why use Entity Framework when NHibernate is here from long time and it’s a better and mature product?
Well, I have not completed yet, but I have found a post about Frans Bouma writing about Entity Framework. The sentence that made me happy was this:
Object-Relational Mapping, or O/R mapping or ‘ORM’ …and it is always used to solve a mismatch between two projections of an abstract entity model: the projection onto a relational schema and the projection onto an object oriented language
There is also an older post quite interesting…
It’s interesting for me about my thinking about the need (not – just for me!) of POCO support in Entity Framework V4.
As always, everyone has an opinion, some likes and dislikes.
Davy Brion is writing about Build Your Own Data Access Layer Series, not using NHibernate (of which he is one of the committers) or Entity Framework. Very interesting, also when Stephen Walther in his book speaks about Repository Pattern in Model chapter.
It is also interesting that always incredibly prolific Ayende is writing “shadow posts”:
I am going to shadow his posts in the series, talking about the implications of the choices made and the differences between Davy’s approach and NHibernate. I think it would be a good approach to show the challenges inherit in building an OR/M.
