ODBC driver: Rows Affected

Поиск
Список
Период
Сортировка
От Nathan Pfluger
Тема ODBC driver: Rows Affected
Дата
Msg-id 4645EC60A48BFD4789FB0CDC161E19580250353E@mail.vcommerce.local
обсуждение исходный текст
Список pgsql-odbc

Previous (non gborg) versions of the driver return the number of RowsAffected by an Update (didn’t test delete) statement, but this one does not.  It seems to always return -1.

 

Not sure if it’s the odbc interface or the tools I’m using (ADO dataset with Delphi)  I am looking at the difference in the ODBC logs and see this:  (Query was in a transaction and rolled back)

 

I read through the archives and saw that this problem was in a patch to the 02 version. Did that patch get into 0003.

 

Also it was noted that the 0003 version should fix the BDE issue and it has not (which is why I using ADO.  The reason I use BDE still is that it seems to behave better with very large record sets and the Declare/Fetch option turned on)  I can use ADO but I liked having the flexibility. 

 

The issue (I looked into this while tracking down some Unicode stuff with the old driver) is that the driver returns a data type that is unrecognized by the BDE which then just throws the field away (this is what makes the dbexplorer tool not work)

В списке pgsql-odbc по дате отправления:

Предыдущее
От: John Lawler
Дата:
Сообщение: SQLDescribeParam not defined: any workaround?
Следующее
От: "Anoop Kumar"
Дата:
Сообщение: Re: changed behavior in libpq odbc driver