2015-10-06 12:45 GMT+03:00 Dmitriy Setrakyan <[email protected]>:
> On Tue, Oct 6, 2015 at 2:42 AM, Vladimir Ozerov <[email protected]> > 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
