Re: changed behavior in libpq odbc driver

Hi,

I have committed the patch for returning SQL_NO_DATA_FOUND instead of
SQL_SUCCESS when no rows got affected in UPDATE/DELETE. You may check it
out from the CVS.

Regards

Anoop

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org [mailto:pgsql-odbc-
> owner(at)postgresql(dot)org] On Behalf Of Scot Loach
> Sent: Sunday, August 21, 2005 8:31 PM
> To: Marko Ristola
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] changed behavior in libpq odbc driver
>
> Thanks for the clarification, Marko.
> I use ODBC 3.0, so it would seem that this is a bug.
>
> scot.
>
>
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Marko Ristola
> Sent: Sunday, August 21, 2005 10:36 AM
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] changed behavior in libpq odbc driver
>
>
>
> Please check, but ODBC 3 should return SQL_NO_DATA, when
> no data has been updated.
>
> ODBC 2 should return SQL_SUCCESS wether any rows were updated, or not.
>
> So it depends on the ODBC standard, that the client program chooses.
>
> Marko Ristola
>
> Scot Loach wrote:
>
> >I'm not sure whether the old driver or the new one is correct.
> >
> >When executing an UPDATE query with a WHERE clause, if the WHERE
clause
> does not match any rows, the old driver returns SQL_NO_DATA. The new
> driver returns SQL_SUCCESS.
> >
> >
> >
> >---------------------------(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
> >
> >
>
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster