I remember seeing some work done for the .NET support to provide better precision for time data values. Could it be that SQL now converts everything to Timestamp because of that?
D. On Wed, Feb 10, 2016 at 10:09 AM, Igor Sapego <isap...@gridgain.com> wrote: > Hello, > > Recently I've been working on implementation of the Date and Timestamp > types support for C++ client [1] and I today have faced an issue when I was > running tests with Date and SqlFieldQuery. > > Here is the issue. I have class that have field of type 'Date'. I was able > to create > instances of that class and put them in a cache, but when I tried to > retrieve > these fields with SQL query I've got an exception. After the short debug > session > I have found that the values that SQL queries return are of type > 'Timestamp'. > > So now I'm wonder, is it an expected behavior? Because to me it looks like > something that may be very confusing for a user. User knows that object's > field > is of type 'Date' but when they try to call GetNext<Date> on query row they > get an > exception. > > I have also tested simple caches with Date where Date is a value and these > tests > work just fine with 'Date' returned as a result of Cache#Get() requests. > > [1] - IGNITE-2222: CPP: Implement Date and Timestamp data types support for > binary protocol. <https://issues.apache.org/jira/browse/IGNITE-2222> > Best Regards, > Igor >
