You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2023/01/26 14:57:00 UTC
[jira] [Commented] (IGNITE-17333) .NET: Thin 3.0: SQL ResultSet object mapping
[ https://issues.apache.org/jira/browse/IGNITE-17333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681012#comment-17681012 ]
Igor Sapego commented on IGNITE-17333:
--------------------------------------
Looks good to me.
> .NET: Thin 3.0: SQL ResultSet object mapping
> --------------------------------------------
>
> Key: IGNITE-17333
> URL: https://issues.apache.org/jira/browse/IGNITE-17333
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: .NET, ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Table API provides object mapping capabilities:
> {code:c#}
> IRecordView<Person> mappedView = Table.GetRecordView<Person>();
> Person res = await mappedView.GetAsync(...);
> {code}
> This is cleaner and more efficient than working with *IgniteTuple*s (less allocations and type casts).
> Implement similar functionality for SQL API - see *ISql.ExecuteAsync<T>*.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)