Thanks Anoop.
Actually I think the old driver always returned 0 for select statements too, so the behavior should now be consistent.
scot.
-----Original Message-----
From: Anoop Kumar [mailto:anoopk@pervasive-postgres.com]
Sent: Friday, August 12, 2005 2:11 AM
To: Dave Page; Scot Loach; pgsql-odbc@postgresql.org
Subject: RE: [ODBC] psqlODBC 08.00.0102 available for download
Hi Scot,
I am attaching a patch to solve the SQLRowCount() issue you have faced.
This should enable you to get the number of rows affected by an
INSERT/DELETE or UPDATE operation.
The old odbc driver returned the number of rows after a select
statement. Now the libpq enabled version returns a zero.
Regards
Anoop
> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-
> owner@postgresql.org] On Behalf Of Dave Page
> Sent: Thursday, August 11, 2005 1:59 PM
> To: Scot Loach; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] psqlODBC 08.00.0102 available for download
>
>
>
> > -----Original Message-----
> > From: Scot Loach [mailto:sloach@sandvine.com]
> > Sent: 11 August 2005 03:56
> > To: Dave Page; pgsql-odbc@postgresql.org
> > Subject: RE: [ODBC] psqlODBC 08.00.0102 available for download
> >
> > I finally got around to giving the new driver a try.
> >
> > There's one major problem I'm running into. Specifically,
> > the SQLRowCount() function doesn't work with the libpq
implementation.
> >
> > Can anyone comment on this?
>
> I'll investigate....
>
> /D
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
