title: Is it OK to pass around EF Entities in MVC3 ViewModels and not incur performance issue due to lazy loading?
body: <p>I want to pass around an EF entity in a property of an View Model, but I am worried that it could incur performance issues since some of the column values of the DB records are big. I then realised that unless I access those particular fields then I would not incur that penalty due to lazy loading. Is this correct?</p>
  
  <p>So to elaborate, in the below example the book property may be called ABSTRACT which is a STRING which is VARCHAR(MAX) in the DB. It may also have ID, AUTHOR and TITLE:</p>
  
  <pre><code>   public class vmTest
     {
     public Book MyBook { get; set; }
     }
  </code></pre>
  
  <p>If I only wished to access ID and TITLE then if my theory is correct then the ABSTRACT column will not be loaded into RAM and therefore cause no performance issues.</p>
  
  <p>Many thanks in advance for any help.</p>