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 = SQLConnect(dbc, (SQLCHAR*)DSN, SQL_NTS, (SQLCHAR*)"", SQL_NTS,
I get a crash in my program stating that:
isql: symbol lookup error: /usr/local/lib/libignite-odbc.so: undefined
According to the author of unixodbc this is a function which is called
to find out where to connect to by opening the /etc/odbc.ini file an
looking for the DSN provided by the parameter.
I compiled the Apache Ignite odbc connector exactly as stated in the
manual. However an ldd on the /usr/local/lib/libignite-odbc.so does not
show me a dependency on the odbcinst.so as stated by the author.
So it seems that the configure script for the compilation is broken somehow.
I installed unixodbc-dev on my ubuntu box so that shouldn't be the problem.
Digging down into the cmake script it seems that it also correctly
detects the installed unixodbc-dev installation.
But the dependency to the odbcinst.so is missing.
Hopefully someone can help.
In the meantime I'm using the SQLDriverConnect routine which is not
dependent on the SQLGetPrivateProfileString. That works but it just a
dirty workaround and shouldn't be the final solution.
Which ODBC Version is implemented in the code?
Version2 or Version3?
You can link your own binary to libodbcinst, in which case the linking problem should go away. Can you try that?
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 going to take a look
at it soon: 
As a workaround you can try a solution suggested by Ilya. I can not provide a sound
workaround for third-party tools like isql though.
On Fri, Nov 27, 2020 at 5:43 PM Ilya Kasnacheev <[hidden email]> wrote:
The workaround for third-party tools is probably LD_PRELOAD=/path/to/libodbcinst.so isql -foo -bar
пт, 27 нояб. 2020 г. в 18:18, Igor Sapego <[hidden email]>:
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?
пн, 30 нояб. 2020 г. в 14:48, Wolfgang Meyerle <[hidden email]>:
Quite simple. I'd like to execute SQL queries.
I just wanted to notify that I fixed the issue with ODBC driver returning the wrong
ODBC version and some other issues: 
On Mon, Nov 30, 2020 at 6:20 PM Ilya Kasnacheev <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|