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

Re: changed behavior in libpq odbc driver

From: "Scot Loach" <sloach(at)sandvine(dot)com>
To: "Marko Ristola" <marko(dot)ristola(at)kolumbus(dot)fi>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-08-21 15:00:31
Message-ID: 71837C040963F748B9B94E123A289678664C28@mailserver.sandvine.com (view raw or flat)
Thread:
Lists: pgsql-odbc
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

pgsql-odbc by date

Next:From: Scot LoachDate: 2005-08-21 15:02:01
Subject: Re: "Official" version
Previous:From: Marko RistolaDate: 2005-08-21 14:36:01
Subject: Re: changed behavior in libpq odbc driver

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