-
Notifications
You must be signed in to change notification settings - Fork 132
Feature: Support to Enumerable Scalar Values #538
Copy link
Copy link
Closed
Labels
deployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releaseenhancementNew feature or requestNew feature or requestfeatureDefined as a big development item (feature)Defined as a big development item (feature)fixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.priorityTop priority feature or things to doTop priority feature or things to dotodoThings to be done in the futureThings to be done in the future
Metadata
Metadata
Assignees
Labels
deployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releaseenhancementNew feature or requestNew feature or requestfeatureDefined as a big development item (feature)Defined as a big development item (feature)fixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.priorityTop priority feature or things to doTop priority feature or things to dotodoThings to be done in the futureThings to be done in the future
Currently, RepoDB requires a concreate .NET CLR Type return type just to retrieve the results from the fetch operations (i.e: ExecuteQuery, Query, QueryAll and BatchQuery).
Let us say, you only would like to query all the product name from the
[dbo].[Product]table (like below).You are required to create a concrete class
ProductNameOnly.This is quite too extensive in the client side (or the library consumer) just to create this un-organized class.
This user story will allow the developers to do the magic query of the targetted Scalar (column-based) values. The propose call would be below.
String:
Long/Int:
In which the result is of type
IEnumerable<Type>.