/
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/argument-type-mismatch-of-oracle-TIMESTAMP-field-when-call-loadCache-tp5935p6365.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
The related code was not changed for fixing this bug.
I want to know, how can I get the code patch?
thanks.
胡永亮
Bob
From: Vasiliy Sisko
Date: 2016-06-29 15:37
To: user@ignite.apache.org
Subject: Re: Re: argument type mismatch of oracle TIMESTAMP field when call
loadCache
se version: 1.6.
>
> --
> 胡永亮
>
> Bob
>
>
> *From:* Vasiliy Sisko <vsi...@gridgain.com>
> *Date:* 2016-06-28 19:18
> *To:* user@ignite.apache.org
> *Subject:* Re: Re: argument type mismatch of oracle TIMESTAMP field when
> call load
sorry, the infomation is not in detail.
My ignite's version is new release version: 1.6.
胡永亮
Bob
From: Vasiliy Sisko
Date: 2016-06-28 19:18
To: user@ignite.apache.org
Subject: Re: Re: argument type mismatch of oracle TIMESTAMP field when call
loadCache
Hello Bob.
What version of Ignite
ot; VARCHAR2(300),
"BKC287" VARCHAR2(100),
"BKC288" VARCHAR2(200),
"BKC289" VARCHAR2(50),
"BKC290" VARCHAR2(50),
"BKC291" FLOAT(126),
"BKC292" FLOAT(126),
"BAB024" VARCHAR2(200),
"AAE009" VARCHAR2(200),
"
Hi, Bob!
Could post here a sample table script that help us to reproduce the problem?
Something like "create table test ()".
Also, just in case please specify your Oracle version.
Thanks!
--
Alexey Kuznetsov
hi,
When I loaded the data from oracle through cache.loadData.
The exception which is argument type mismatch of oracle TIMESTAMP happened.
The detail:
I produced the schema through the tool schema-import-tool.
A pojo object is Kc21, and it has a property Bkc192, its type is
