8
May
CUD stored procedures “improvements” in Entity Framework 4
The EDM designer in Entity Framework 4 has a “nice” new feature. You, know in EFv1 you was forced to map all three CUD procedures or nothing. If you didn’t do that, the validation feature told you. If you do the same in EFv4 the validation succeeds. Great, you may think. Finally I can use just procedures I really want (if you whatsoever want to use SPs and tight the logic into database when using ORM) to use and the rest will be generated for me. But nope. In fact the error will be thrown in runtime(!!!).
It’s described in documentation. But I couldn’t help but wonder, who did this decision??? I hate every error in runtime, I like my static compile time checking. It’s much safer, in my opinion.
There's 5 Comments So Far
May 8th, 2010 at 20:58
Sounds like a bug, to me. Did you file a connect report? I’d vote for it.
May 9th, 2010 at 12:36
Hard to say whether it’s a big or not – it’s noted in documentation. :\
May 10th, 2010 at 14:57
I mean the designer “feature” mismatch with the proc limitation, not the proc limitation itself — though I, too, would love to see *that* fixed.
May 10th, 2010 at 22:54
The problem is, it’s not the designer. The whole mapping validation has been changed – it’s relaxed, until needed.
Who Linked To This Post?
Share your thoughts, leave a comment!