Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/henkmollema/Dapper-FluentMap
Provides a simple API to fluently map POCO properties to database columns when using Dapper.
https://github.com/henkmollema/Dapper-FluentMap
c-sharp dapper poco-properties
Last synced: about 2 months ago
JSON representation
Provides a simple API to fluently map POCO properties to database columns when using Dapper.
- Host: GitHub
- URL: https://github.com/henkmollema/Dapper-FluentMap
- Owner: henkmollema
- License: mit
- Archived: true
- Created: 2014-04-24T10:33:12.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2023-04-19T13:48:03.000Z (over 1 year ago)
- Last Synced: 2024-07-28T02:01:17.705Z (about 2 months ago)
- Topics: c-sharp, dapper, poco-properties
- Language: C#
- Homepage:
- Size: 2.57 MB
- Stars: 428
- Watchers: 32
- Forks: 85
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-dotnet-core - Dapper-FluentMap - Provides a simple API to fluently map POCO properties to database columns when using Dapper. (Frameworks, Libraries and Tools / ORM)
- awesome-dotnet-core - Dapper-FluentMap - Dapper的扩展。 (框架, 库和工具 / 对象关系映射ORM)
- Awesome-Nuget-Packages - **Dapper.FluentMap**
- fucking-awesome-dotnet-core - Dapper-FluentMap - Provides a simple API to fluently map POCO properties to database columns when using Dapper. (Frameworks, Libraries and Tools / ORM)
- awesome-dotnet-core - Dapper-FluentMap - Provides a simple API to fluently map POCO properties to database columns when using Dapper. (Frameworks, Libraries and Tools / ORM)
README
## 📦 Archived
This repository is archived as I'm not using this library myself anymore and have no time maintaining it. Thanks for using it.
# Dapper.FluentMap
Provides a simple API to fluently map POCO properties to database columns when using Dapper.
| Windows | Linux/OSX | NuGet |
| --- | --- | --- |
| [](https://ci.appveyor.com/project/henkmollema/dapper-fluentmap) | [](https://travis-ci.org/henkmollema/Dapper-FluentMap) | [](https://www.nuget.org/packages/Dapper.FluentMap/ "NuGet version") |
### Introduction
This [Dapper](https://github.com/StackExchange/dapper-dot-net) extension allows you to fluently configure the mapping between POCO properties and database columns. This keeps your POCO's clean of mapping attributes. The functionality is similar to [Entity Framework Fluent API](http://msdn.microsoft.com/nl-nl/data/jj591617.aspx). If you have any questions, suggestions or bugs, please don't hesitate to [contact me](mailto:[email protected]) or create an issue.
### Download
[](https://www.nuget.org/packages/Dapper.FluentMap)
### Usage
#### Manual mapping
You can map property names manually using the [`EntityMap`](https://github.com/henkmollema/Dapper-FluentMap/blob/master/src/Dapper.FluentMap/Mapping/EntityMap.cs) class. When creating a derived class, the constructor gives you access to the `Map` method, allowing you to specify to which database column name a certain property of `TEntity` should map to.
```csharp
public class ProductMap : EntityMap
{
public ProductMap()
{
// Map property 'Name' to column 'strName'.
Map(p => p.Name)
.ToColumn("strName");
// Ignore the 'LastModified' property when mapping.
Map(p => p.LastModified)
.Ignore();
}
}
```
Column names are mapped case sensitive by default. You can change this by specifying the `caseSensitive` parameter in the `ToColumn()` method: `Map(p => p.Name).ToColumn("strName", caseSensitive: false)`.
**Initialization:**
```csharp
FluentMapper.Initialize(config =>
{
config.AddMap(new ProductMap());
});
```
#### Convention based mapping
When you have a lot of entity types, creating manual mapping classes can become plumbing. If your column names adhere to some kind of naming convention, you might be better off by configuring a mapping convention.
You can create a convention by creating a class which derives from the [`Convention`](https://github.com/henkmollema/Dapper-FluentMap/blob/master/src/Dapper.FluentMap/Conventions/Convention.cs) class. In the contructor you can configure the property conventions:
```csharp
public class TypePrefixConvention : Convention
{
public TypePrefixConvention()
{
// Map all properties of type int and with the name 'id' to column 'autID'.
Properties()
.Where(c => c.Name.ToLower() == "id")
.Configure(c => c.HasColumnName("autID"));
// Prefix all properties of type string with 'str' when mapping to column names.
Properties()
.Configure(c => c.HasPrefix("str"));
// Prefix all properties of type int with 'int' when mapping to column names.
Properties()
.Configure(c => c.HasPrefix("int"));
}
}
```
When initializing Dapper.FluentMap with conventions, the entities on which a convention applies must be configured. You can choose to either configure the entities explicitly or use assembly scanning.
```csharp
FluentMapper.Initialize(config =>
{
// Configure entities explicitly.
config.AddConvention()
.ForEntity()
.ForEntity;
// Configure all entities in a certain assembly with an optional namespaces filter.
config.AddConvention()
.ForEntitiesInAssembly(typeof(Product).Assembly, "App.Domain.Model");
// Configure all entities in the current assembly with an optional namespaces filter.
config.AddConvention()
.ForEntitiesInCurrentAssembly("App.Domain.Model.Catalog", "App.Domain.Model.Order");
});
```
##### Transformations
The convention API allows you to configure transformation of property names to database column names. An implementation would look like this:
```csharp
public class PropertyTransformConvention : Convention
{
public PropertyTransformConvention()
{
Properties()
.Configure(c => c.Transform(s => Regex.Replace(input: s, pattern: "([A-Z])([A-Z][a-z])|([a-z0-9])([A-Z])", replacement: "$1$3_$2$4")));
}
}
```
This configuration will map camel case property names to underscore seperated database column names (`UrlOptimizedName` -> `Url_Optimized_Name`).
### [Dommel](https://github.com/henkmollema/Dommel)
Dommel contains a set of extensions methods providing easy CRUD operations using Dapper. One of the goals was to provide extension points for resolving table and column names. [Dapper.FluentMap.Dommel](https://github.com/henkmollema/Dapper-FluentMap/tree/master/src/Dapper.FluentMap.Dommel) implements certain interfaces of Dommel and uses the configured mapping. It also provides more mapping functionality.
#### [`PM> Install-Package Dapper.FluentMap.Dommel`](https://www.nuget.org/packages/Dapper.FluentMap.Dommel)
#### Usage
##### `DommelEntityMap`
This class derives from `EntityMap` and allows you to map an entity to a database table using the `ToTable()` method:
```csharp
public class ProductMap : DommelEntityMap
{
public ProductMap()
{
ToTable("tblProduct");
// ...
}
}
```
##### `DommelPropertyMap`
This class derives `PropertyMap` and allows you to specify the key property of an entity using the `IsKey` method:
```csharp
public class ProductMap : DommelEntityMap
{
public ProductMap()
{
Map(p => p.Id).IsKey();
}
}
```
You can configure Dapper.FluentMap.Dommel in the `FluentMapper.Initialize()` method:
```csharp
FluentMapper.Initialize(config =>
{
config.AddMap(new ProductMap());
config.ForDommel();
});
```