Yes. I just found out the hard way yesterday by debugging through the
Ignite.Net source code and reached the same understanding. Thank you.
On Wednesday, November 21, 2018, 6:12:16 AM EST, Pavel Tupitsyn
wrote:
There is a subtle issue with DateTime and SQL [1]
If you always use UTC i
There is a subtle issue with DateTime and SQL [1]
If you always use UTC in Ignite (which you should), the proper thing to do
is:
var igniteCfg = new IgniteConfiguration
{
BinaryConfiguration = new BinaryConfiguration
{
Serializer = new BinaryReflectiveSerializer
{
Force
Sure. Hope this won't get too long and will still be readable from e-mail, and
thank you for helping. Really appreciate it.
using System;using System.Collections.Generic;using System.Linq;using
System.Text;using System.Threading.Tasks;using Apache.Ignite.Core;using
Apache.Ignite.Core.Cache;usi
Hi, can you please attach a minimal runnable project that reproduces the
issue?
On Fri, Nov 16, 2018 at 4:08 AM Peter Sham wrote:
> Hello,
>
> I’m trying to learn Ignite.Net and has been following examples bundled
> with source or binary distribution. However, when I try to define SQL
> Schema
Additional findings. Actually the SQL schema defined by running sql create
table works fine except for the date field. So I suspect the error message
"BinaryInvalidTypeException: Unknown pair [platformId=0,
typeId=-1854586790]" would probably mean the framework cannot find a mapping
between Java
Hello,
I’m trying to learn Ignite.Net and has been following examples bundled with
source or binary distribution. However, when I try to define SQL Schema that
will match an object either by sql create table statement or using QueryEntity
in cache configuration, without resorting to QuerySqlFie
