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/02/02 09:06:00 UTC

[jira] [Commented] (IGNITE-18392) Thin 3.0: SQL ResultSet object mapping

    [ https://issues.apache.org/jira/browse/IGNITE-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17683288#comment-17683288 ] 

Igor Sapego commented on IGNITE-18392:
--------------------------------------

Looks good to me.

> 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)