Hello Bob
We fix import of Oracle TIMESTAMP in issue:
https://issues.apache.org/jira/browse/IGNITE-3394
It is available in master branch.
It will be available in next nightly build. You can take it here:
https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/
--
;
> --
> 胡永亮
>
> 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
>
> Hello Bob.
>
>
> We cre
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
e 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 I
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 I
"BKE160" VARCHAR2(3),
> "BKE161" VARCHAR2(50),
> "BKE162" TIMESTAMP (6),
> "BKC401" VARCHAR2(3),
> "BKC285" VARCHAR2(300),
> "BKC286" VARCHAR2(300),
> "BKC287" VARCHAR2(100),
> "BKC288" VARCHAR
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
