Simple CRUD operations for Dapper.
$ dotnet add package DommelCRUD operations with Dapper made simple.
| Windows | Linux | NuGet | MyGet | Test Coverage |
|---|---|---|---|---|
 |  |  |  |  |
Dommel provides a convenient API for CRUD operations using extension methods on the IDbConnection interface. The SQL queries are generated based on your POCO entities. Dommel also supports LINQ expressions which are being translated to SQL expressions. is used for query execution and object mapping.
There are several extensibility points available to change the behavior of resolving table names, column names, the key property and POCO properties. See Extensibility for more details.
Dommel is available on NuGet.
dotnet add package Dommel
Install-Package Dommel
var product = await connection.GetAsync<Product>(1);var products = await connection.GetAllAsync<Product>();Dommel allows you to specify a predicate which is being translated into a SQL expression. The arguments in the lambda expression are added as parameters to the command.
var products = await connection.SelectAsync<Product>(p => p.Name == "Awesome bike" && p.Created < new DateTime(2014, 12, 31) && p.InStock > 5);Which would translate in the following SQL:
select * from Products where Name = @p1 and Created < @p2 and InStock > @p3You can add parentheses to combine and & or queries:
var products = await connection.SelectAsync<Product>(p => p.Name == "Awesome bike" && (p.Created < new DateTime(2014, 12, 31) || p.InStock > 5));Which would translate in the following SQL:
select * from Products where Name = @p1 and (Created < @p2 or InStock > @p3)There is also a FirstOrDefaultAsync<T>(...) method available to select the first entity matching the predicate.
It is possible to generate LIKE-queries using Contains(), StartsWith() or EndsWith() on string properties:
var products = await connection.SelectAsync<Product>(p => p.Name.Contains("bike"));
var products = await connection.SelectAsync<Product>(p => p.Name.StartsWith("bike"));
var products = await connection.SelectAsync<Product>(p => p.Name.EndsWith("bike"));var product = new Product { Name = "Awesome bike", InStock = 4 };
var id = await connection.InsertAsync(product);var product = await connection.GetAsync<Product>(1);
product.Name = "New name";
await connection.UpdateAsync(product);var product = await connection.GetAsync<Product>(1);
await connection.DeleteAsync(product);Dommel is able to generate join-queries based on the specified multi mapping function. Consider the following POCO's:
public class Product
{
public int Id { get; set; }
public string Name { get; set; }
// Maps to the foreign key column
public int CategoryId { get; set; }
// The navigation property
public Category Category { get; set; }
}
public class Category
{
public int Id { get; set; }
public string Name { get; set; }
}The Product with its associated Category can be queried toegether using the Get<T1, T2, ..., TResult>() method:
var product = await product.GetAsync<Product, Category, Product>(1, (product, category) =>
{
product.Category = category;
return product;
});CategoryId is automatically used as foreign key between Product and Category. This follows a simple convention: joining table name + Id (Category + Id). You can override this behavior by using the [ForeignKey("ForeignKeyColumnName")] attribute or by implementing your own IForeignKeyPropertyResolver.
One-to-many relationships work in a similar way, expect that the foreign key is defined on the joined type rather than the source type. For example:
public class Order
{
public int Id { get; set; }
// The navigation property
public ICollection<OrderLine> OrderLines { get; set; } = new List<OrderLine>();
}
public class OrderLine
{
public int Id { get; set; }
// The foreign key column to the Order table
public int OrderId { get; set; }
public string Description { get; set; }
}The Order with its child OrderLine's can be queried toegether using the Get<T1, T2, ..., TResult>() method:
var product = await product.GetAsync<Order, OrderLine, Order>(1, (order, line) =>
{
// Naive mapping example, in reality it requires more gymnastics
order.OrderLines.Add(line);
return order;
});Note: this is an experimental feature.
Dommel is able to create simple join-expressions for retrieving parent-child entities. One-to-one and one-to-many relations are supported. It works the samy way as regular mapping, except there is no need to specify a function which performs the mapping of the objects. Using the same POCO's as the previous examples:
Retrieving a Product and its associated Category:
var product = product.Get<Product, Category, Product>(1);Retrieving one Order and with its child OrderLine's:
var product = product.Get<Order, OrderLine, Order>(1);When joining with two or more tables with a one-to-many relationship, you are required to override Equals(object obj) method or implement the IEquatable<T> interface on your POCO's so Dommel can determine whether an entity is already added to the collection. For example:
public class OrderLine : IEquatable<OrderLine>
{
public int Id { get; set; }
public int OrderId { get; set; }
public string Description { get; set; }
public bool Equals(OrderLine other) => Id == other.Id;
}Select and multi-mappingIt's possible to combine Select queries and multi-mapping. For example:
var products = await connection.SelectAsync<Product, Category, Product>(x => x.Name.StartsWith("bike"));This is applicable for Select, SelectAsync, FirstOrDefault and FirstOrDefaultAsync. Both with manual and automatic multi-mapping.
With From-queries you can create more complex queries on a certain table by providing access to the SqlExpression<T>. For example:
var products = await connection.FromAsync<Product>(sql => sql
.Where(x => x.Name.StartsWith("bike") && x.DeletedOn == null)
.OrWhere(x => x.InStock > 5)
.OrderBy(x => x.DateCreated)
.Page(1, 25)
.Select()));All Dommel methods have async and non-async variants, such as as Get & GetAsync, GetAll & GetAllAsync, Select & SelectAsync, Insert & InsertAsync, Update & UpdateAsync, Delete & DeleteAsync, etc.
Dommel supports building specialized queries for a certain RDBMS. By default, query builders for the following RDMBS are included: SQL Server, SQL Server CE, SQLite, MySQL and Postgres. The query builder to be used is determined by the connection type. To add or overwrite an existing query builder, use the AddSqlBuilder() method:
DommelMapper.AddSqlBuilder(typeof(SqlConnection), new CustomSqlBuilder());ITableNameResolverImplement this interface if you want to customize the resolving of table names when building SQL queries.
public class CustomTableNameResolver : ITableNameResolver
{
public string ResolveTableName(Type type)
{
// Every table has prefix 'tbl'.
return $"tbl{type.Name}";
}
}Use the SetTableNameResolver() method to register the custom implementation:
SetTableNameResolver(new CustomTableNameResolver());IKeyPropertyResolverImplement this interface if you want to customize the resolving of the key property of an entity. By default, Dommel will search for a property with the [Key] attribute, or a column with the name 'Id'.
If you, for example, have the naming convention of {TypeName}Id for key properties, you would implement the IKeyPropertyResolver like this:
public class CustomKeyPropertyResolver : IKeyPropertyResolver
{
public ColumnPropertyInfo[] ResolveKeyProperties(Type type)
{
return new [] { new ColumnPropertyInfo(type.GetProperties().Single(p => p.Name == $"{type.Name}Id"), isKey: true) };
}
}Use the SetKeyPropertyResolver() method to register the custom implementation:
DommelMapper.SetKeyPropertyResolver(new CustomKeyPropertyResolver());IForeignKeyPropertyResolverImplement this interface if you want to customize the resolving of the foreign key property from one entity to another. By default Dommel will search for a property of {TypeName}Id or the column name specified using the [ForeignKey] attribute.
This is a rather advanced interface. Providing your own implementation requires quite some knowledge of the way Dommel handles foreign key relationships. Consider subclassing
DefaultForeignKeyPropertyResolverand overrideResolveForeignKeyProperty().
Use the SetForeignKeyPropertyResolver() method to register the custom implementation:
DommelMapper.SetForeignKeyPropertyResolver(new CustomForeignKeyPropertyResolver());IColumnNameResolverImplement this interface if you want to customize the resolving of column names for when building SQL queries. This is useful when your naming conventions for database columns are different than your POCO properties.
public class CustomColumnNameResolver : IColumnNameResolver
{
public string ResolveColumnName(PropertyInfo propertyInfo)
{
// Every column has prefix 'fld' and is uppercase.
return $"fld{propertyInfo.Name.ToUpper()}";
}
}Use the SetColumnNameResolver() method to register the custom implementation:
DommelMapper.SetColumnNameResolver(new CustomColumnNameResolver());