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

Re: changed behavior in libpq odbc driver

From: "Scot Loach" <sloach(at)sandvine(dot)com>
To: "Scot Loach" <sloach(at)sandvine(dot)com>,"Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-08-19 00:41:31
Message-ID: 71837C040963F748B9B94E123A2896785A0F9C@mailserver.sandvine.com (view raw or flat)
Thread:
Lists: pgsql-odbc
Another difference is the "state" that is returned from SQLGetDiagRec when a connection is lost during a query.  This used to return 08S01.  It now returns HY000.  From the documentation it would appear that 08S01 is the correct return code in this case.  I'm guessing the error codes are not implemented in the libpq version of the driver yet.

Also, SQLGetConnectAttr with SQL_ATTR_CONNECTION_DEAD doesn't seem to work anymore.



-----Original Message-----
From:	pgsql-odbc-owner(at)postgresql(dot)org on behalf of Scot Loach
Sent:	Thu 8/18/2005 10:03 AM
To:	Anoop Kumar; pgsql-odbc(at)postgresql(dot)org
Cc:	
Subject:	Re: [ODBC] changed behavior in libpq odbc driver
OS is FreeBSD 5.4, but I really don't think this matters.
PostgreSQL 7.4.6
old psqlodbc is version 07.03.0200, but it has various updates applied to it.
new psqlodbc is the latest from CVS as of about a week ago.


-----Original Message-----
From: Anoop Kumar [mailto:anoopk(at)pervasive-postgres(dot)com]
Sent: Thursday, August 18, 2005 6:23 AM
To: Scot Loach; pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] changed behavior in libpq odbc driver


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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
       message can get through to the mailing list cleanly



pgsql-odbc by date

Next:From: Josh BerkusDate: 2005-08-19 04:18:21
Subject: Re: dates and selection
Previous:From: Joel FradkinDate: 2005-08-18 20:38:36
Subject: nevermind answered my own question by looking at my question what a DOH!

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