Hi,
I'm not working on this issue currently and is not aware
if anyone else in the community looking at it.
But I think it's going to be fixed by 2.8 or 2.9 as it looks
quite important.
Best Regards,
Igor
On Fri, Jun 7, 2019 at 7:53 PM Charles Rene
wrote:
> Hi Igor, When will this issue be
Hi Igor, When will this issue be addressed? Thanks, Charlie
On Mon, May 13, 2019 at 9:55 AM Igor Sapego wrote:
> It seems like some encoding related issue to me.
> Added a Jira ticket: [1].
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-11845
>
> Best Regards,
> Igor
>
>
> On Thu, May
Charles,
Thanks for the reproducer, I'll check it out.
Best Regards,
Igor
On Thu, May 16, 2019 at 6:59 PM Charles Rene
wrote:
> Thanks Igor. I also noticed that the Linux ODBC Driver deserializes the
> Ignite UUID data type into a byte[] instead of the .Net Guid type. That is
> contrary to
Thanks Igor. I also noticed that the Linux ODBC Driver deserializes the
Ignite UUID data type into a byte[] instead of the .Net Guid type. That is
contrary to what is stated in the documentation (
https://apacheignite-sql.readme.io/docs/data-types#section-uuid).
SQL Example:
CREATE TABLE MyTable
It seems like some encoding related issue to me.
Added a Jira ticket: [1].
[1] - https://issues.apache.org/jira/browse/IGNITE-11845
Best Regards,
Igor
On Thu, May 2, 2019 at 1:15 AM Charles Rene
wrote:
> Hello,
>
> I'm having trouble using the Apache Ignite 2.7.0 Linux built ODBC driver.
>
Hello,
I'm having trouble using the Apache Ignite 2.7.0 Linux built ODBC driver.
I'm running a .Net Core 2.2 console application in a Linux environment in
Docker.
The problem is that when I run a SELECT statement through .Net's
System.Data.Odbc, I get back "bad data". It looks like a mismatch in
