150 Views
Samuel Meacham highlights a crucial performance issue when dealing with many inheritance models in the Entity Framework 4. Microsoft has to this day not dealt with the issue, and in something of a scandal, has deleted the bug report on Connect that Sam filed. Sam offers a good reason to stay clear of the Entity Framework for the time being and perhaps a long time to come too.
2 comments
Noldorin
11/3/2011 11:08:28 PM
This is one thing that really ticks me off about MS. That Microsoft had the nerve to delete a bug report without warning about such an important issue, which has been plaguing database developers / users of EF for years now is horrendous. I really hope they get their act together on this one. For now, I'm quite happy to shun the Entity Framework and go with the much superior NHibernate framework.
Noldorin
11/3/2011 11:08:28 PM
This is one thing that really ticks me off about MS. That Microsoft had the nerve to delete a bug report without warning about such an important issue, which has been plaguing database developers / users of EF for years now is horrendous. I really hope they get their act together on this one. For now, I'm quite happy to shun the Entity Framework and go with the much superior NHibernate framework.