Dapper.NET and IQueryable

Question

Is there a plan to make Dapper.net compatible with IQueryable interfaces? If not, what's the workaround to use Dapper with "Expression Trees" filters?

Unarm

Surely a question about the future of Dapper.Net would be better placed on github? – Weathercock

This is a feature request for an external library. – Cisco

At nearly 1,000 reputation, you should know the rules by now. This is completely offtopic. – Origen

Some may quibble about whether this question satisfies the rules, but it asked a question I was looking for, and the answer was helpful. – Telepathist

Excellent question, I will be working with Dapper soon, my first question was what is it? and my second question was exactly this one! – Malayalam

What solution did you end up with Bill? As you might be looking for a faster performing solution then the default EF behavior? – Cirillo

Any updates to this, given there several years passed by – Impost

Updating this for QuickGrid in 2023. Although it'll work with Dapper I guess there's no point?! – Carleton

Answer 1

No, there are no plans to do this. It is far far outside what dapper tries to do. So far that I would say it is antithetical. Dapper core tries to be the friend to those who love their SQL.

There

Great answer - If any doesnt like SQL, there are other solutions like Entity Framework. – Ilke

I really like SQL (or I really like to like SQL). but i also like getting paid early. Screw SQL, i want to deploy. Entity Framework for SQLite it is! – Fremont

I'm sorry SQL, I really meant screw OData! Forgive me, I'm crawling back to your arms! – Fremont

SQL is faster in the end, not EF 🤡 – Carleton

@Carleton Faster to run, certainly. Not always/necessarily faster to build with -- particularly on medium to medium(ish)-sized projects. – Subtemperate

@BrianLacy A matter of taste, experience and it depends how you define 'faster'. With SQL I know exactly what's going on, I'm speaking the language of the database, I take the results and Dapper maps them. Simples. With EF it does all sorts of its own weird joining and data access in an opaque way, often highly inefficiently and highly unpredictably. Not my thing but to each their own. – Carleton

@Carleton indeed, we also need to consider the time spent when EF doesn't do what we expect, plus the time spent finding out that EF didn't do what we expected (from a symptom like performance reports); this doesn't happen every time, but when it does: it can be a time sink – There

Answer 2

Checkout Dapper.TQuery NuGet package for that.

Nathannathanael