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 2022/07/07 17:20:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-17333:
------------------------------------
Description:
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).
was:
Table API provides object mapping capabilities:
{code:csharp}
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).
> .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
>
> 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).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)