-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Support to Enumerable Scalar Values #538
Comments
mikependon
added
enhancement
New feature or request
todo
Things to be done in the future
priority
Top priority feature or things to do
feature
Defined as a big development item (feature)
labels
Sep 2, 2020
mikependon
added a commit
that referenced
this issue
Sep 5, 2020
mikependon
added a commit
that referenced
this issue
Sep 5, 2020
mikependon
added a commit
that referenced
this issue
Sep 5, 2020
mikependon
added a commit
that referenced
this issue
Sep 5, 2020
mikependon
added a commit
that referenced
this issue
Sep 6, 2020
mikependon
added a commit
that referenced
this issue
Sep 6, 2020
mikependon
added a commit
that referenced
this issue
Sep 6, 2020
Automatic Conversion / Integration Tests / Compiler Updates #538
mikependon
added a commit
that referenced
this issue
Sep 6, 2020
mikependon
added a commit
that referenced
this issue
Sep 6, 2020
Supported the Typed Result for Enum (String/NonString). #538
The fix is available at version RepoDb v1.12.0-beta3 or above. |
Closing this ticket now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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>
.The text was updated successfully, but these errors were encountered: