[
https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948862#comment-14948862
]
Pavel Tupitsyn edited comment on IGNITE-1571 at 10/8/15 5:02 PM:
------------------------------------------------------------------
11) User can use ReadObject for anything, but we have specialized methods, so I
don't see a reason to remove ReadGuid/ReadDate. They are also useful to
indicate that we do not expect nulls (and an exception will be thrown).
Other things fixed.
was (Author: ptupitsyn):
11) User can use ReadObject for anything, but we have specialized methods, so I
don't see a reason to remove ReadGuid/ReadDate. They are also useful to
indicate that we do not expect nulls (and an exception will be thrown).
> .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: 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)
