.net - ORMs and Constructors -


I am looking at .NET ORM implementations, and I have a bigger burning question - is there any .NET ORM Do not require public properties for every area in implemenations database? When I see an example, a small bell gets out in my head. I believe in strongly encapsulation, and forcing them to open the keys to their objects, they force them to work well with the framework, Is access to all ORMs necessary? If not, then please tell me the examples of those who do not need it!

Supports multiple usage strategies for members of NHibernate class. Public properties is a D-Facto default but you can ask NHibernate to reach areas of your classroom directly.

For example

  & lt; Property name = "CustomerName" access = "Field.camelcase-underscore" />  

will instruct NHibernate to use the field in its class declared in this way:

  protected string _customerName;  

Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -