Is the latest entity framework finally able to lazy load properties (e.g. byte[] ) without doing that table splitting hack?
5
-
2By "latest", do you mean the latest release, the latest prerelease, or the recently open sourced to-be-EF6 codebase? As far as I know, it doesn't change the answer, but it changes the certainty with which I would say "I don't think so".user743382– user7433822012-08-06 12:05:41 +00:00Commented Aug 6, 2012 at 12:05
-
the latest publically available version :)Elisabeth– Elisabeth2012-08-06 12:30:50 +00:00Commented Aug 6, 2012 at 12:30
-
All of those are publicly available, so that would be the EF6 codebase then. In that case, I don't think so, but I'm not sure enough to answer :)user743382– user7433822012-08-06 12:33:56 +00:00Commented Aug 6, 2012 at 12:33
-
ok then lets wait for someone posting a link here about that feature.Elisabeth– Elisabeth2012-08-06 12:37:38 +00:00Commented Aug 6, 2012 at 12:37
-
One work-around to "the table splitting hack" is to create a view of the table that doesn't have the large field, and then create an EF object that references the view - works quite well. Yes, you have two entities in EF, but the storage is automatically consistent between the two, and it keeps the DB side simple.C.List– C.List2016-02-18 02:09:03 +00:00Commented Feb 18, 2016 at 2:09
Add a comment
|
1 Answer
No it is not able to lazy load columns without table splitting. As you can see the suggestion is even not yet switched to planned or under review state. Table splitting workaround solves this problem.
EF is now open source so you can add that feature yourselves.
1 Comment
Elisabeth
"so you can add that feature yourselves" and get busy till end of this year :P