Add support for mapping columns to nested object properties #815
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.
Current functionality does not allow the user to select and map columns to nested object properties of the return type when using the Query function.
This change will allow the user to alias a column as NestedObject.PropertyName, which will instantiate the NestedObject (if no default value) and assign the value of the column to the specified PropertyName of the NestedObject.
Example:
Given the table structure and DTO
Current implementation would force us to populate the nested object
FooReferenceProperty
and its properties by combining multiple queries and in memory assignment like so:Doing this can become very cumbersome, especially when several nested objects are involved.
This modified implementation of
ExecuteDeferredQuery
will allow us to populate the nested objectFooReferenceProperty
and its properties with just a singleQuery
call:Note: Mapping will only be valid to the nested objects of the root object. This change does not support mapping to nested objects of nested objects.