NH is too tolerante to incorrect naming when access="field.XXX" is used
Description
Environment
None
Attachments
1
Activity
Show:
Fabio Maulo March 4, 2011 at 2:14 PM
Yes, it is... and a nice one because we have used this kind of things in our tests
Who's Looking?
NH today accepts code below. It would be better if this would throw - it causes problem when configurate NH (or 3rd party tools) other ways than by hbm, using the property name (or memberinfo) of the public interface.
[hbm]
<property name="Name" access="field.camelcase" />
[code]
string name;
public virtual string SomeThingCompletelyDifferent
{
get {return name;}
set {name=value;}
}
Note: This will be a breaking change.