74
User
Recs.
Recs.
26
Updates
Last
Updated
Updated
Activity
28 Options
Works across all .NET ADO providers including SQLite, SQL CE, Firebird, Oracle, MySQL, PostgreSQL and SQL Server.
Read article: Using Dapper Flexibly.
Specs
Specs are quantitative aspects of the option such as the price
Pros
Pro Makes it trivially easy to execute queries (scalar, multi-rows, multi-grids, and no-results)
Know any positive aspects of this option?
Cons
Con A pain to maintain
You've got a bunch of inline SQL statements that do various queries that have no strong ties to the DB architecture. This can quite easily lead to queries that get "left behind" when the underlying DB structure changes, which, again, you will not see at build time.
Con It doesn't track objects and their changes so you can just call SubmitChanges()
Know any negative aspects of this option?
Recommendations
Dapper
Recommended 2 years ago
Fast, flexible, free
Pro
Similar performance to a raw SqlCommand with DataReader and parsingPro
No need to roll your own conversion layer for the DataReaderPro
Very efficient and quickPro
Makes it trivially easy to execute queries (scalar, multi-rows, multi-grids, and no-results)Pro
Makes it trivially easy to turn results into objectsDapper
Recommended 5 years ago
StackOverflow and other websites of stackexchange are using this. Dapper extend the IDbConnection by providing useful extension methods to query your database.
Pro
Similar performance to a raw SqlCommand with DataReader and parsingPro
No need to roll your own conversion layer for the DataReaderPro
Very efficient and quickCon
It doesn't generate a class model or queries for youCon
It doesn't track objects and their changes so you can just call SubmitChanges()Con
Not even slightly typesafePro
Makes it trivially easy to correctly parameterize queriesPro
Makes it trivially easy to execute queries (scalar, multi-rows, multi-grids, and no-results)Pro
Makes it trivially easy to turn results into objectsCon
A pain to maintain