Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement.
От | Heikki Linnakangas |
---|---|
Тема | Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement. |
Дата | |
Msg-id | 5318C83F.3050306@vmware.com обсуждение исходный текст |
Ответ на | Re: SQLFetchScroll with SQL_ATTR_ROWS_FETCHED_PTR closing statement. (Przemyslaw Rzepecki <przemyslaw.rzepecki@ericsson.com>) |
Список | 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
В списке pgsql-odbc по дате отправления: