title: NHibernate difference between nosetter and field access strategies
body: <p>I originally posted about a problem where NHibernate was issuing an additional query for a collection that was exposed as a ReadOnlyCollection and mapped as "nosetter" or "ReadOnlyPropertyThroughCamelCaseField" in FluentNhibernate.</p>
  
  <p>The property was not being accessed directly in my code but NHibernate thought there was a change. When I changed the access strategy to "field" - or "CamelCaseField" in fluent nhibernate, it fixed the issue.</p>
  
  <p>So my question is, what is the difference between the two access strategies in how NHibernate detects changes to a collection?</p>
  
  <p>Thanks
  Ben</p>