ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-12377) .NET: Add IBinaryObjectBuilder.SetField(name, val, type) overload
Date Fri, 15 Nov 2019 16:14:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Tupitsyn updated IGNITE-12377:
------------------------------------
    Description: 
Right now the only general-purpose overload is {{SetField<T>(string fieldName, T val)}}.
Let's say we get name-value pairs from some other system (e.g. from Dapper - see linked user
list thread), and we want to create binary objects from them.
When we call SetField<object>, binary metadata will have Object type for all fields
(type code 103), which is not good.
The only workaround is to create a huge if-else and call proper SetXxx method depending on
actual data type - bad usability.

In fact, we can easily provide SetField(string name, object val, Type valType) overload to
solve this.

> .NET: Add IBinaryObjectBuilder.SetField(name, val, type) overload
> -----------------------------------------------------------------
>
>                 Key: IGNITE-12377
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12377
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET
>             Fix For: 2.8
>
>
> Right now the only general-purpose overload is {{SetField<T>(string fieldName,
T val)}}.
> Let's say we get name-value pairs from some other system (e.g. from Dapper - see linked
user list thread), and we want to create binary objects from them.
> When we call SetField<object>, binary metadata will have Object type for all fields
(type code 103), which is not good.
> The only workaround is to create a huge if-else and call proper SetXxx method depending
on actual data type - bad usability.
> In fact, we can easily provide SetField(string name, object val, Type valType) overload
to solve this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message