You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/02/02 09:09:00 UTC
[jira] [Updated] (IGNITE-18698) С++ 3.0: SQL ResultSet object mapping
[ https://issues.apache.org/jira/browse/IGNITE-18698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-18698:
------------------------------------
Labels: ignite-3 (was: .NET ignite-3)
> С++ 3.0: SQL ResultSet object mapping
> -------------------------------------
>
> Key: IGNITE-18698
> URL: https://issues.apache.org/jira/browse/IGNITE-18698
> Project: Ignite
> Issue Type: Improvement
> Components: platforms, thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> 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)