Entity Framework 5 First Steps – Mapping

in a previous article , i’ve explained how simple it is to use ef5 to access a database and use database-migrations to create a database suitable to contain your entities (with a simple update-command from the package manager console). when you show this technique to many programmers, the first complaint they have is, “ the structure of the generated tables is not suitable to me .”

figure 1: database generated with previous code example

suppose you want to specify a maximum length for the various columns, specify not-null columns, and you want them to be named with a convention. finally, you don't want to use identity columns, because all the customers you will save in this database come from a legacy cmr application and you want to be able to use the very same id of the crm system.

if you want to customize how the table is generated, but you want to be completely free on how you name entities, properties, or context dbset, you need to specify a custom mapping that does not use standard convention over configuration. first you must create a mapping class for your customer class (you can also do this with attributes) to specify how properties will be mapped on database tables and columns .

public class customermap : entitytypeconfiguration<customer>
{
    public customermap()
    {
        // primary key
        this.haskey(t => t.id);
 
        // properties
        // table & column mappings
        this.totable("customer");
        this.property(t => t.id)
            .hascolumnname("cust_id")
            .hasdatabasegeneratedoption(databasegeneratedoption.none);
        this.property(t => t.name)
            .hascolumnname("cust_name")
            .hasmaxlength(100)
            .isrequired();
        this.property(t => t.address)
            .hascolumnname("cust_address")
            .hasmaxlength(200);
    }
}

you can put this class wherever you want, i usually put it into a subfolder named mappings and i usually call this class with the same name of the entity with the suffix map. now you should only specify in your dbcontext that this mapping is available .

protected override void onmodelcreating(dbmodelbuilder modelbuilder)
{
    modelbuilder.configurations.add(new customermap());
}

by overriding onmodelcreating you can add your custom mapping to the configurations collection , now if you issue another update-database you can verify that the table is now created the way you want.

figure 2: new structure of the table that respect the customermap class

now you can see that the table is called customer, columns are named with your convention and length and not null are created correctly. this is really good because if the dba or some convention impose you some naming rules on database tables and column you are free to use business-friendly names in your entities .