Added offset and fetch functions to the SqlBuilder to allow pagination #40
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe i'm missing something, but why not move this code into the SqlBuilder class and change it to public class SqlBuilder : Dapper.SqlBuilder |
|
The SqlBuilder is a Dapper class, I'd have to make a pull request for the official Dapper repository to change it. Instead, I created a class that inherits from the Dapper.SqlBuilder. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I came across the need of making a pagination and I implemented the SQL Server way of doing it.
It does work with postgree too since it is just ansi sql, but I think Oracle and MySQL don't have those clauses yet (although I wasn't able to test it against the latest version of those databases).