Add the mapping strategy to support the table name and column name

In the real scenario, we should create the datatable with the different name conventions. For example: tbl_customer (table name), id(column name), first_name(column name). But the domain object should follow the C# name convention, for example

public class Customer
{
        public int Id { get; set; }
        public string FirstName { get; set; }
}

We can define a interface IMappingStrategy then implement different strategies:

We can define the global strategy or set the strategy for the speicifed domain object event the property. We will generate the SQL with the defined strategies. That will be wonderful feature.

Thanks.

No files, tests, or entry points are named in the issue. Start by locating the current table and column name generation, then review how global, object-level, and property-level mapping could fit the requested IMappingStrategy. Done means the generated SQL honors the selected naming strategy for examples such as Customer, Id, and FirstName.