It would be great to have a broader way to define no tracking contexts or no tracking DbSets so that we can design read-only models or DbSets. Yes we can control that in a repository but controlling it at the context or DbSet level would be simpler for devs to implement read-only data. It could also alleviate the problem of accidentally tracking data because you've set a navigation property. My pref would be to see this for a context. It would let you query but nothing else. Not sure how this will effect relationships via eager, lazy or explicit loading.
Comments: Thanks Julie - I've renamed the bug. At this stage it's not something we're going to tackle in EF6, but we'll definitely consider it for a future release (and of course someone could always contribute it).
Comments: Thanks Julie - I've renamed the bug. At this stage it's not something we're going to tackle in EF6, but we'll definitely consider it for a future release (and of course someone could always contribute it).