[
https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-1571:
------------------------------------
Description:
Currently we force user to write Guid and DateTime as nullables. We do this to
be more compatible with Java.
But user is more likely to operate on plain types: Guid, Guid[], DateTime,
DateTime[].
We need to add these methods to API, and rename existing ones to
"ReadNullableDateTime", etc..
Note that while trivial to on writer side, it will be harder to implement for
readers. Currently we lookup by type ID, which will be equal for the type and
it's nullable counterpart. For this reason we probably must lookup by type ID +
type or simply by type.
was:
Currently we force user to write Guid and DateTime as nullables. We do this to
be more compatible with Java.
But user is more likely to operate on plain types: Guid, Guid[], DateTime,
DateTime[].
We need to ass these methods to API, and rename existing ones to
"ReadNullableDateTime", etc..
Note that while trivial to on writer side, it will be harder to implement for
readers. Currently we lookup by type ID, which will be equal for the type and
it's nullable counterpart. For this reason we probably must lookup by type ID +
type or simply by type.
> .Net: Improve Guid and DateTime reader/writer interface.
> --------------------------------------------------------
>
> Key: IGNITE-1571
> URL: https://issues.apache.org/jira/browse/IGNITE-1571
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: ignite-1.5
>
>
> Currently we force user to write Guid and DateTime as nullables. We do this
> to be more compatible with Java.
> But user is more likely to operate on plain types: Guid, Guid[], DateTime,
> DateTime[].
> We need to add these methods to API, and rename existing ones to
> "ReadNullableDateTime", etc..
> Note that while trivial to on writer side, it will be harder to implement for
> readers. Currently we lookup by type ID, which will be equal for the type and
> it's nullable counterpart. For this reason we probably must lookup by type ID
> + type or simply by type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
