Mappings can be built in several different ways:

• Mappings can be created by using auto mapping
• Mappings can be created by putting attributes on classes that you build.
• Mappings can be created by getting the schema from the database.
• Mappings can be created by loading XML Mapping Files
• Mappings can be created by creating a mapping entirely in code

 

Each one of the mappings above can be overridden at run time in code.  The is particularly useful if in your application you need to change your database at run time to point to a different schema, for example pointing to a QA schema versus a UAT schema.  See the Schema property on the table object.  Changing table names is useful when needing to point to staging tables or archive tables for use in ETL scenarios. 

 

Example

 

IDataHelper db = DataHelper.SessionFactory();

Table table = _db.Mapper.GetObjectMap(typeof(Customer));

table.TableName = "Customer_Staging";

table.Schema = "TestEnvironment4.";