[
https://issues.apache.org/jira/browse/IGNITE-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-18392:
------------------------------------
Description:
Table API provides object mapping capabilities:
{code:c#}
RecordView<PersonPojo> pojoView = table.recordView(Mapper.of(PersonPojo.class));
PersonPojo val = pojoView.get(null, key);
{code}
This is cleaner and more efficient than working with *IgniteTuple*s (less
allocations and type casts).
Implement similar functionality for SQL API - users should be able to map query
results to POJOs.
was:
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>*.
> Thin 3.0: SQL ResultSet object mapping
> --------------------------------------
>
> Key: IGNITE-18392
> URL: https://issues.apache.org/jira/browse/IGNITE-18392
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
>
> Table API provides object mapping capabilities:
> {code:c#}
> RecordView<PersonPojo> pojoView =
> table.recordView(Mapper.of(PersonPojo.class));
> PersonPojo val = pojoView.get(null, key);
> {code}
> This is cleaner and more efficient than working with *IgniteTuple*s (less
> allocations and type casts).
> Implement similar functionality for SQL API - users should be able to map
> query results to POJOs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
