Added overloads allowing predicate expressions to limit scope #1586
+194
−0
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
DeleteAllAsync() and GetAllAsync() overloads accept a predicate expression that can be used to limit the scope of the action. I.E filter records returned or deleted.
Author
|
I'm not sure why the build failures occur for this PR, can anyone advise? I submitted this because the functionality would be super-useful for my own projects and therefore, I assume, others would find it useful too. |
Member
|
I can't speak to Contrib's future plans here and if this is a good fit, but please see #1658 - Dapper.Contrib is not located at https://github.com/DapperLib/Dapper.Contrib (separate from this repository). If you're wanting predicated functionality on builders, I'd personally recommend EntityFramework Core overall as it has progressed and gotten quite efficient. |
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.
DeleteAllAsync() and GetAllAsync() overloads accept a predicate expression that can be used to limit the scope of the action. I.E filter records returned or deleted.
This is obviously limited compared to what you can achieve with the QueryAsync or ExecuteAsync methods but does allow you to stay in the Dapper.Contrib world for simple use cases and not require any SQL strings.
For example to return entities where Age = 5:
await connection.GetAllAsync<User>(x => x.Age == 5)For example to delete entities where Age = 5:
await connection.DeleteAllAsync<User>(x => x.Age == 5)Some supporting tests have been added.