[ https://issues.apache.org/jira/browse/IGNITE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013873#comment-16013873 ]
Pavel Tupitsyn edited comment on IGNITE-4406 at 5/17/17 1:17 PM: ----------------------------------------------------------------- Another way we can enable control over this are {{BinaryConfiguration.ForceTimestamp}} and {{BinaryTypeConfiguration.ForceTimestamp}} properties. However, it is the {{IBinarySerializer}} implementation responsibility to use {{WriteTimestamp}} or not. was (Author: ptupitsyn): Another way we can enable control over this are {{BinaryConfiguration.ForceTimestamp}} and {{BinaryTypeConfiguration.ForceTimestamp}} properties. > .NET: Control DateTime serialization via attribute > -------------------------------------------------- > > Key: IGNITE-4406 > URL: https://issues.apache.org/jira/browse/IGNITE-4406 > Project: Ignite > Issue Type: Improvement > Components: platforms > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.1 > > > .NET can write DateTime in internal format (preserves DateTime.Kind) and as > Timestamp (does not allow non-UTC values). > By default we use internal format. To use Timestamp user has to mark field > with QuerySqlField (non obvious), or override IBinarizable. > * Provide a dedicated attribute to enforce timestamp mode. > * Attribute can be applied to a field, property, or a whole type > * Provide a property on {{BinaryReflectiveSerializer}} to force Timestamp > everywhere - this may be needed when class code can't be modified -- This message was sent by Atlassian JIRA (v6.3.15#6346)