Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement.

From: Przemyslaw Rzepecki <przemyslaw(dot)rzepecki(at)ericsson(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement.
Date: 2014-03-06 17:05:07
Message-ID: 1394125507.15011.18.camel@salti.rnd.ki.sw.ericsson.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

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?

Best regards,
Przemek

On Tue, 2014-03-04 at 16:21 +0200, Heikki Linnakangas wrote:
> usage of the fetch scroll function incorrect?
>
> Looks correct to me. I tried to reproduce this with the attached test
> program (modified from the regression tests), and it worked fine.
>
> - Heikki

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Heikki Linnakangas 2014-03-06 18:57:29 Re: Elimination of (more or less) all compilation warnings on OSX
Previous Message Tom Lane 2014-03-06 16:50:51 Re: Elimination of (more or less) all compilation warnings on OSX