Mapping CLR Types Properties and Associations - Overview

When you use default mapping, the FluentMetadataSource takes care of the property to column mapping. When you use explicit mapping you are explicitly specifying the property to column mapping. The explicit mapping configuration gives you more control over the column naming, and it also allows you to create partially mapped models.

This section contains the following topics that discuss how to perform explicit mapping:

• Mapping CLR Types
• Defining Identity
  • Single Field Identity
  • Internal Identity
  • Composite Field Identity
  • Identity Per Configuration Level
• Property Configuration
  • Primitive Property Configuration
  • String Property Configuration
  • DateTime Property Configuration
  • Setting DataAccessKind
• Mapping Associations
  • One-to-Many Associations
  • One-to-One Associations
  • Many-to-Many Associations
  • One Sided Associations
  • Creating ForeignKey Constraints
  • Additional Associations Configuration
• Advanced Mapping
  • Array Property Mapping
  • String Array Property Mapping
  • Using String Based API
  • Mapping Private Fields
  • Defining Indexes
  • Defining Explicit Indexes in Join Table
  • Polymorphic References
  • IList<ValueT> Property Mapping
  • Backend Independent Mapping
    • How to: Change the Backend
    • String Properties
    • Char Properties
    • Decimal Properties
    • Byte Array Properties
  • Dictionary Property Mapping
    • Primitive Key-Value Types
    • Primitive Key and Reference Type Value
    • Reference Type Key and Primitive Value
    • Reference Key-Value Types
  • Multi-Table Entities
    • Multi-Table Entities
    • How to: Set Up Cascade Delete With Multi-Table Entities
• Field Name Rules
• Enum Support
• Struct Support
• Mixing Default and Explicit Mapping
• Using Per-Class Configuration
• Handling Database Columns with Default Value