dapper

Currently, I am using OrmLite for DB operations. I am also planning to use Dapper ORM, but can anyone point me how to integrate DapperORM in ServiceStack. Do I need to implement both IDbConnection and IDbConnectionFactory interfaces with Dapper and plugin into the container. public override void Configure(Container container) { container.Register<IDbConnectionFactory>( c => new OrmLiteConnectionFactory(ConfigurationManager.ConnectionStrings["default"].ConnectionString, SqlServerDialect.Provider)); container.Register<IDbConnection>(c => c.Resolve<IDbConnectionFactory>().OpenDbConnection())

Is it possible to add and remove criteria on the fly with dapper? I need this to implement user driven filtering. It is not feasible to have a query for each filter as there are too many combinations. At the most basic level, you can just build the TSQL dynamically in a StringBuilder - adding extra and c.Name = @name etc . Don't worry about extra parameters; send them all - the library inspects the command and doesn't add any parameters that obviously aren't used. There is a second, newer API for this specific scenario, but I can't remember the specifics without checking (and I'm not at a

I have a class structure similar to this: public abstract class Device { public int DeviceId { get; set; } //Additional Properties } public class DeviceA : Device { //Specific Behaviour } public class DeviceB : Device { //Specific Behaviour } I need to retrieve a list of Devices, or a single Device which is instantiated as the appropriate derived type (based upon a Type value in the Device Record in the DB). That is, the collection of Device objects should contain a number of objects with different Types, all of which are derived from Device . I have implemented this the following way, but

I have a stored procedure that returns multiple result sets. I'm executing this with dapper. One of the result sets is Person JOIN Checks, where Person can have many Checks. The end goal is to have distinct person objects that have a collection of check objects. QueryMutliple gives me a Sqlmapper.GridReader . I see an overload of SqlMapper.GridReader.Read() that takes a Func<TFirst, TSecond, TReturn> . Is there an example of how to use this? Ronnie Overby Here's how I got it working: var q = _sqlConnection.QueryMultiple("MySproc", myParams, commandType: CommandType.StoredProcedure); var set1 =

it looks like there was an ExecuteScalar in Dapper... http://code.google.com/p/dapper-dot-net/issues/attachmentText?id=22&aid=220000000&name=ExecuteScalar.cs&token=9e2fd8899022f507b140ffb883c60e34 Was ExecuteScalar renamed or removed? Can this now be achieved with .Query or .Query<T>? ExecuteScalar was just added in 1.28: https://www.nuget.org/packages/Dapper I was able to call ExecuteScalar< T > with version 1.42.0 public Boolean BeforeToday(DateTime dateInQuestion) { try { using (var conn = new SqlConnection(ConnectionString)) { String sql = @"SELECT CONVERT(bit, CASE WHEN getdate() >

Most of examples/question just introduce solutions to map "only one" level of the query using split on like this: var sql = "SELECT P.Id, P.FirstName, P.LastName, " + "A.Id AS AddressId, A.StreetNumber, A.StreetName, A.City, A.State " + "FROM People P INNER JOIN Addresses A ON A.AddressId = P.AddressId; "; db.Query<Person, Address, Person>( sql, (person, address) => { person.Address = address; return person; }, splitOn: "AddressId" ).ToList(); I have a query like this one (just an example): Select * from Country C inner join State S on C.CountryId = S.CountryId inner join City Ct on S.StateId

Really impressed with Juile Lerman's pluralsight course on "EF in Enterprise" and decided to build my demo app. I am using VS 2012 and latest versions of EF,SQL Server and MVC. I am building a demo application which applies SOLID principles. I am doing this to better understand how to implement DI & unit testing. I have used DB first approach for this demo application. It contains only one table named UserDetails and below is how it looks in SQL server. I will use this table for CRUD operations. Below is how i have layered my application : 1. WESModel Solution: This layer contains my Model1