ORMs and Constructors
Posted
by Harper Shelby
on Stack Overflow
See other posts from Stack Overflow
or by Harper Shelby
Published on 2009-05-05T20:54:42Z
Indexed on
2010/03/12
19:17 UTC
Read the original article
Hit count: 265
I'm looking over .NET ORM implementations, and I have a major burning question - are there any .NET ORM implemenations that don't require public properties for every field in the database? When I see examples like this, a little bell goes off in my head. I firmly believe in encapsulation, and being forced to open the kimono of my objects just to make them work nicely with persistence frameworks gives me the heebie-jeebies. Is this sort of accessibility required in all ORMs out there? If not, please point me to examples of those that don't need it!
© Stack Overflow or respective owner