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

Re: changed behavior in libpq odbc driver

From: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
To: "Scot Loach" <sloach(at)sandvine(dot)com>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-08-18 10:22:52
Message-ID: B4AF8C04F762D246A1E38EC5DFAEFC0B0379C1@blrmail2.aus.pervasive.com (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Scot,

Can you provide the following details?
	1. The psqlodbc (socket) version you used
	2. PostgreSQL version
	3. OS

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: Thursday, August 18, 2005 7:18 AM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] changed behavior in libpq odbc driver
> 
> 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

pgsql-odbc by date

Next:From: JUANFELIX SALAZARDate: 2005-08-18 12:17:02
Subject: Conexion posgresql con Oracle
Previous:From: Scot LoachDate: 2005-08-18 01:47:51
Subject: changed behavior in libpq odbc driver

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