Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement.

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Przemyslaw Rzepecki <przemyslaw(dot)rzepecki(at)ericsson(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement.
Date: 2014-03-06 19:10:55
Message-ID: 5318C83F.3050306@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On 03/06/2014 07:05 PM, Przemyslaw Rzepecki wrote:
> Hi,
>
> Thanks for the answer! I have compare my program with Yours didn't
> noticed any logical difference. Then tried rerun the tests on two
> different systems, any my tests ware passing on one but the errors ware
> still present on the other.
>
> Tried to step by step eliminate all the differences and I believe its
> the libodbcinst.so.2 vs libodbcinst.so.1 which cause the difference. It
> works fine with unixodbc 1 but when I use a driver recompiled against
> unixodbc 2 then the error happens.
>
> Could You let me know which odbc libraries You use on your system? Is it
> possible for someone else to retest with odbc2 libraries?

I use what ships with Debian. Seems to be unixodbc 2.3.1.

Seems odd. I don't think the driver depends on libodbcinst.so. Could it
be caused by some kind of confusion between 32-bit and 64-bit versions
of libraries? Where did those libraries come from?

- Heikki

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Michael Paquier 2014-03-07 06:41:49 Re: Removing support for < 7.4 servers
Previous Message Heikki Linnakangas 2014-03-06 18:57:29 Re: Elimination of (more or less) all compilation warnings on OSX