Introduction

Dapper, Dapper Extensions and Linq. Dapper.Extensions.Linq builds on this providing advanced DB access through Linq queries. The fluid configuration makes setup simplistic and quick.

Release Notes

1.1.17

Reduced the target framework to .NET 4.5 (previously 4.6)
IEnumerable insert
Schema attribute for AutoMapper
Added LogManager

1.1.16

Added timeout to Query, QueryScalar, QueryDynamic

1.1.15

QueryDynamic added for executing inline queries

1.1.14

Nolock unit tests and fix

1.1.13

Handling NullReferenceException when comparing against MemberExpression on the left side (alexzubiaga)
Timeouts can be specified for EntityBuilder
Nolock can be specified for EntityBuilder

1.1.12

Improve QueryBuilder.cs handling of boolean (alexzubiaga)

1.1.11

Expressions can use variables and constants

1.1.10

Linq contains can be used to mimic a like
Bug fixes

1.1.9

PredicateBuilder fix

1.1.8

Added PredicateBuilder to allow ExpressionBuilding for Query

1.1.7

Querying with extrernal lists can now use nullable types

1.1.6

Added the ability to query with external lists

1.1.5

Added Top to Query.
Added OrderBy to Query.
Added OrderByDescending to Query.

1.1.4

Added new AutoClassMapper attributes TableName and PrefixForColumns.
Isolated AutoMap to AutoClassMapper for clarity.
Removed an unused reference to EntityFramework on Dapper.Linq.Extensions.SQLite

Features

Simplistic fluid configuration
Automatic mapping of Entities
Sql generation with Linq
Customisable entity mapping with ClassMapper.
Entites can be manipulated with attributes
Custom IoC containers
Multiple connection providers
Support for Sql Server, Postgre Sql, MySql, SqlCe and SQLite

Attributes

DataContext - Which connection provider to use, defaults to __Default, you can additionally override this with fluid configuration.

Property Attributes

Ignore - This property will not be mapped
MapTo - Assign a property to a different database column

Naming Conventions

Entity names should match the table name in the database. Pluralized table names are supported through the PlurizedAutoClassMapper.
Entity properties should match the column name in the table.
By convention, the primary key should be named Id. Using another name is supported through custom mappings.

Installation

http://nuget.org/List/Packages/Dapper.Extensions.Linq

PM> Install-Package Dapper.Extensions.Linq

Configuration

Note that dapper configuration requires a container in order to build. You can use the nuget package Dapper.Extensions.Linq.CastleWindsor or implement your own. The caslte provides you with dependency injection for the repositories.

Basic configuration and setup:

DapperConfiguration
    .Use()
    .UseClassMapper(typeof(AutoClassMapper<>))
    .UseContainer<Dapper.Extensions.Linq.CastleWindsor.ContainerForWindsor>(c => c.UseExisting(_container))
	.UseSqlDialect(new SqlServerDialect())
    .FromAssembly("Dapper.Entities")
    .Build();

#Configure internal component logging

The DefaultFactory logging class makes use of Trace.

LogManager
    .Use<DefaultFactory>()
    .Enable();

Application config:

  <configSections>
    <section name="Logging" type="Dapper.Extensions.Linq.Core.Config.Logging, Dapper.Extensions.Linq.Core" />
  </configSections>
  <Logging Threshold="DEBUG" />

Examples

The following examples will use a Person Entity

public class Person : IEntity
{
    public int Id { get; set; }
    public string FirstName { get; set; }
    public string LastName { get; set; }
    public bool Active { get; set; }
    public DateTime DateCreated { get; set; }
}

Get

_dapperRepository.Get(Id) //Using a get
_dapperRepository.Query(e => e.Id == Id) //Using linq by id
_dapperRepository.Query(e => e.FirstName == "Gary").SingleOrDefault() //Using linq by first name

Insert

var person = new Person { FirstName = "Foo", LastName = "Bar", DateCreated = DateTime.Now };
_dapperRepository.Insert(person);

Update

Person person = _dapperRepository.Get(PersonId);
person.LastName = "Rwar";
_dapperRepository.Update(person);

Delete

Person person = _dapperRepository.Get(PersonId);
_dapperRepository.Delete(person);

Count

int numberOfPeople = _dapperRepository.Count();

or

int numberOfPeople = _dapperRepository.Count(e => e.FirstName == "Foo");

Lists with Linq

Using Query you additionally have access to other methods like Top, OrderBy, OrderByDescending and others.

List<Person> people = _dapperRepository
                       .Query(e => e.Active && e.DateCreated > DateTime.AddDays(-5))
                       .OrderBy(e => e.DateCreated)
                       .ToList();

Dynamic queries

Allows you to execute custom inline script.

const string sql = "SELECT TOP 1 Id, FirstName FROM Person ORDER BY Id DESC";
IEnumerable<dynamic> result = personRepository.QueryDynamic(sql);

License

Copyright 2011 Thad Smith, Page Brooks, Ryan Watson and contributors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

ryanwatson/Dapper.Extensions.Linq

ErrorLooks like something went wrong!

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages