Lazy loading of non-navigation properties
At time we may require to lazy load at column level. For e.g. if we have a LOB column which could be huge, we may not want to load that upfront when the table is lazy loaded. Agreed that we can workaroudn this problem, but a straight forward way would be good to have
Support for lazy properties (not associations). For example, loading a NVARCHAR(max) only when the property is accessed.
Tommy Long commented
I'm so bored of ending up back on this website...
Somebody once told me EF4 was alike L2S's bigger brother. For my lunch break today I intend to buy a large fish, find that idiots, and slap them across the face with it.
This is yet another hurdle when attempting to migrate from L2S to EF4. Both teams work for the same company, right? All these lovely features supposedly made available by EF4 and I fear I'll never get to use them because the cost of migration for existing projects in terms of time, GREATLY exceeds the cost of purchasing a third party ORM.
Please, EF4 team, one hand giveth, the other taketh away... *stop disappointing*.
Oh, how much time we spent to solve this! Table separating, designing, coding... For some systems (f.e. Document Flow, CMS...) it is a very reqiured feature.
ryan lin commented
This is a must.