Hi, Wolfgang,
I just wanted to notify that I fixed the issue with ODBC driver returning
the wrong
ODBC version and some other issues: [1]
[1] - https://github.com/apache/ignite/pull/8528
Best Regards,
Igor
On Mon, Nov 30, 2020 at 6:20 PM Ilya Kasnacheev
wrote:
> Hello!
>
> There may be some
Hello!
There may be some issues with ODBC driver but it is generally working and
stable. I'm not sure why you would need the ODBC_V3 specifically?
Regards,
--
Ilya Kasnacheev
пн, 30 нояб. 2020 г. в 14:48, Wolfgang Meyerle <
wolfgang.meye...@googlemail.com>:
> Quite simple. I'd like to execute
Hello!
The workaround for third-party tools is probably
LD_PRELOAD=/path/to/libodbcinst.so
isql -foo -bar
Regards,
--
Ilya Kasnacheev
пт, 27 нояб. 2020 г. в 18:18, Igor Sapego :
> Hi,
>
> Starting from your last question, it's Version3.
>
> Now to the issue you are referring to. It definitely
Hi,
Starting from your last question, it's Version3.
Now to the issue you are referring to. It definitely looks like a bug to
me. It's weird
that no one has found it earlier. Looks like no one uses SQLConnect? It is
weird that
We do not have a test for that either. Anyway I filed a ticket and goi
Hello!
You can link your own binary to libodbcinst, in which case the linking
problem should go away. Can you try that?
Regards,
--
Ilya Kasnacheev
пт, 27 нояб. 2020 г. в 17:13, Wolfgang Meyerle <
wolfgang.meye...@googlemail.com>:
> Hi,
>
> after spending several hours to get the unixodbc dri
Hi,
after spending several hours to get the unixodbc driver up and running I
nearly gave up.
However together with the author of unixodbc I was able to find out that
the current odbc driver in Apache Ignite is not doeing what it's
supposed to do.
As soon as I execute the command:
et = SQLC