New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paging large results #760
Comments
Hi.
in this query you can use these properties: you can add your new function to list of extensions. |
Hah yes, between asking that and your answer I used SqlTrace to examine what Linq2Sql actually sends and it is structurally identical to your recommendation. So performance will be identical! Thank you for presenting this as a preferred solution. |
@PeterWone Are you all set? Just cleaning up issues prepping for 2.0 here. |
Can I get by? Yes. Would skip/take be awesome if baked into Dapper? Yes they would. Is it a formula transform? Yes. Could I do it myself? Possibly. But I don't have familiarity with Dapper innards, I'm new to it. You can close this as an issue, it has a good answer. |
@PeterWone Gotcha, thanks! For others finding this: I'd say if you're after SQL generation, Dapper may simply not be the ORM for you :) That's just a different direction than the goals Dapper is after: simplicity, efficiency, and performance across many providers. |
What's the recommended approach to fetching a particular page from a large result? Is there something like Linq's Skip and Take? As of MSSQL2012 you can use
OFFSET skip FETCH NEXT take ONLY
but Linq was able to achieve this with older versions.The text was updated successfully, but these errors were encountered: