[ http://issues.apache.org/jira/browse/IBATISNET-101?page=comments#action_12330358 ]
Hugo Hallman commented on IBATISNET-101: ---------------------------------------- It's impossible to have properties and fields with the same name. Speaking of the subject, I think it would be very usefull if the framework could detect if it's a property or field automatically. Because then the code could be changed with not su much hazzle. I know I've made the mistake hundreds of times, changing something from a field to a property forgetting the details of some not compiler checked dependencies. In cases where you don't have unit tests for it, it's also easy to forget completely! > Support for public fields > ------------------------- > > Key: IBATISNET-101 > URL: http://issues.apache.org/jira/browse/IBATISNET-101 > Project: iBatis for .NET > Type: New Feature > Components: DataMapper > Environment: .Net > Reporter: Ling Wang > > Currently, IBatis.Net support only private fields and public properties. For > example: > private string _FirstName; > public string FirstName > { > get { return _FirstName; } > set { _FirstName = value; } > } > IBatis for .Net should also support > public string FirstName; > The way of doing it is to add an field attribute starting from: > <result property="FirstName" column="PER_FIRST_NAME" > /> > add support for: > <result field="FirstName" column="PER_FIRST_NAME" /> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
