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

Re: changed behavior in libpq odbc driver

From: "Scot Loach" <sloach(at)sandvine(dot)com>
To: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>,"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-08-31 12:52:00
Message-ID: 71837C040963F748B9B94E123A2896785A101D@mailserver.sandvine.com (view raw or flat)
Thread:
Lists: pgsql-odbc
That didn't fix it, it still returns HY000.

This is the error message that comes back:

FATAL:  terminating connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally


-----Original Message-----
From: Anoop Kumar [mailto:anoopk(at)pervasive-postgres(dot)com]
Sent: Wednesday, August 31, 2005 1:51 AM
To: Scot Loach
Cc: pgsql-odbc(at)postgresql(dot)org; Dave Page
Subject: RE: [ODBC] changed behavior in libpq odbc driver


Hi All,

Please find the patch for the other bug pointed out by Scot. (Thanks to
Sivakumar)

"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."

I request you to review this patch as well. 

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

pgsql-odbc by date

Next:From: Dave PageDate: 2005-08-31 13:08:10
Subject: Re: changed behavior in libpq odbc driver
Previous:From: Carlos Henrique ReimerDate: 2005-08-31 11:57:35
Subject: Re: Transactions and SavePoints

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