This question is locked. New answers and comments are not allowed.
OpenAccess seems to use the private field names from the objects instead of the public property names. This does not make sense to me first because private scope information should not be exposed outside of the class, and second, the prefix we use for private field name in the objects make their way to the database. For example, one convention in C# is to use the underscore character as the prefix for private field names; OpenAccess creates database column names that include the prefix. Another worse example: if you declare your properties like this:
public string Name { get; set; }
the database column name ends up being the private field name generated internally by the compiler. Ugly!
How can OPenAccess be configured to avoid this situation and use the name of public properties to generate the database schema? I know that I can use forward mapping and modify the information, but when you deal with hundreds of persistent objects and thousands of persistent properties, this is not a practical solution.
public string Name { get; set; }
the database column name ends up being the private field name generated internally by the compiler. Ugly!
How can OPenAccess be configured to avoid this situation and use the name of public properties to generate the database schema? I know that I can use forward mapping and modify the information, but when you deal with hundreds of persistent objects and thousands of persistent properties, this is not a practical solution.