Skip site navigation (1) Skip section navigation (2)

Re: ODBC driver: Rows Affected

From: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
To: "Nathan Pfluger" <npfluger(at)vcommerce(dot)com>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: ODBC driver: Rows Affected
Date: 2005-08-24 06:45:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Hi Nathan,

The patch did not get into the 8.01.0003 Release. You have to get the latest CVS version for that.



-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Nathan Pfluger
Sent: Wednesday, August 24, 2005 3:22 AM
To: pgsql-odbc(at)postgresql(dot)org
Subject: [ODBC] ODBC driver: Rows Affected

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 by date

Next:From: Dave PageDate: 2005-08-24 09:05:27
Subject: Re: ODBC driver: Rows Affected
Previous:From: Anoop KumarDate: 2005-08-24 06:16:54
Subject: Re: changed behavior in libpq odbc driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group