fix: Row() and Rows() functions should automaticaly apply the generic type as model #7664
+53
−10
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.
What did this pull request do?
Changes the
RowandRowsfunctions in the generic api to specify the generic type as the model for the db operations internally, similar tosetCreateOrUpdateGorExec.User Case Description
When using
Row()andRows()functions in the traditional api the caller has to specify the Model to use in the db operations.However, in the generic api, I think the behaviour expected is that the generic api uses the generic types to do the operations without specifying the model in a separate step. Specifically:
should successfully return the users that are named "Alice", instead we get:
since without caller specifying the model for the operation in a separate step, the Table remains empty.