You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kukushkin (Jira)" <ji...@apache.org> on 2020/11/03 20:44:00 UTC

[jira] [Updated] (IGNITE-12824) Interoperable Ignite.NET Dates

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

Alexey Kukushkin updated IGNITE-12824:
--------------------------------------
    Summary: Interoperable Ignite.NET Dates  (was: .NET: Write DateTime in interoperable format by default)

> Interoperable Ignite.NET Dates
> ------------------------------
>
>                 Key: IGNITE-12824
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12824
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms
>    Affects Versions: 2.8
>            Reporter: Alexey Kukushkin
>            Assignee: Alexey Kukushkin
>            Priority: Major
>              Labels: .NET, ignite-3, sbcf
>             Fix For: 3.0
>
>         Attachments: ignite-12824-vs-2.8.patch
>
>
> Presently BinaryReflectiveSerializer serialises .NET dates Ignite objects by default. This could be changed by either setting BinaryReflectiveSerializer.ForceTimestamp property to "true" or adding "QuerySqlField" attribute to Date fields. I have multiple Ignite/GridGain users using this functionality and all of them are confused with this default behavior. Let's see if we can change the default behavior to save .NET dates in interoperable Ignite TIMESTAMP format, converting them to UTC dates inside BinaryReflectiveSerializer so that the users do not have to do the ToUniversalDate conversion manually.



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