Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Dapper vs Venflow, the Slant community recommends Dapper for most people. In the question“What are the best ORMs for C#?” Dapper is ranked 2nd while Venflow is ranked 9th.
Question Ranking
Pros
Pro Very efficient and quick
Pro No need to roll your own conversion layer for the DataReader
Pro Similar performance to a raw SqlCommand with DataReader and parsing
Pro Makes it trivially easy to turn results into objects
Pro Makes it trivially easy to execute queries (scalar, multi-rows, multi-grids, and no-results)
Pro Makes it trivially easy to correctly parameterize queries
Pro Fast
Pro Effective
Venflow has some very innovative solutions that reduce memory usage
Pro Change tracking
Simple change-tracking for update operations.
Cons
Con Not even slightly typesafe
If you make a typo in the SQL your CI server is not going to catch it, you'll have to hope it's caught during automated UI or functional testing.
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 generate a class model or queries for you
Con It doesn't track objects and their changes so you can just call SubmitChanges()
Con Only PostgreSQL
Only PostgreSQL is supported at the moment.
