ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Why portable marshaller handle Date and Timestamp in the same way?
Date Tue, 06 Oct 2015 10:08:03 GMT
2015-10-06 12:45 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:

> On Tue, Oct 6, 2015 at 2:42 AM, Vladimir Ozerov <vozerov@gridgain.com>
> wrote:
>
> > This doesn't answers the question. First, Java Timestamp has greater
> > precision than .Net DateTime, so silent data loss could happen in this
> case
> > as well. Second, "use timestamp" is defined on class level. It means we
> > cannot handle a class which have both Date and Timestamp fields.
> >
> > Looks like a bug and/or invalid design for me.
> >
>
> Agree, current design is not ideal. Vladimir, do you have other
> suggestions?


how about writing at max precision possible (+ proper type ID) and
interpreting binary data on read depending on (a) portable reader method
call or (b) on actual field type.

--Yakov

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message