title: DbContext's internal caching (?)
body: <p>I created my own context which inherits from DbContext. Let's assume I have 1 post in my [Posts] table in the database. Consider this scenario:</p>
  
  <ol>
  <li>I ask DbContext for this only post for the <strong>first time</strong>. And DbContext returns it as expected.</li>
  <li>I change one column in [Posts] table <em>manually</em>.</li>
  <li>I refresh my site = I ask DbContext for this post again.</li>
  <li><strong>DbContext returns a post which has old value for this specific column!</strong></li>
  </ol>
  
  <p>I looked into SQL Profiler and the database IS hit every time I refresh my site, so why the returned post has an old value? I guess DbContext is trying to be very clever and has some internal caching mechanism, but it would be nice to inform me that he's so clever...</p>
  
  <p>Can someone explain this to me?</p>