Adding support for composite keys in Dapper.Contrib #1614
Closed
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.

THIS IS A NEW VERSION OF A VERY OLD AND FORGOTTEN PULL REQUEST ( #636).
PLEASE REVIEW IT WITH LOVE. 🥰
Hello guys.
I changed a bit the implementation of the Get method so it can also work with composite keys. I have a few tables with this design and it always annoyed me the fact that Update, Insert and Delete supported them but I had to write custom queries when I wanted to retrieve records from database.
The method still works the same way it was defined before.
var regularKey = connection.Get<RegularKey>(1);But now also supports operations like this:
I was also able to optimize Update and Delete methods a bit by using a new method to retrieve all keys.
For your appreciation and code review.
Cheers