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

Re: changed behavior in libpq odbc driver

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>,"Scot Loach" <sloach(at)sandvine(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-08-24 09:46:13
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9C1E@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org 
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Anoop Kumar
> Sent: 24 August 2005 07:17
> To: Scot Loach
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] 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.

Ahh, one less item on my todo :-)

Do you intend to fix the state code problem and dead connection
detection issues reported by Scot as well? 

<sob story>it would really help me if you could as I've got a bunch of
other stuff to do :-( </sob story>

:-)

Regards, Dave.

pgsql-odbc by date

Next:From: Dave PageDate: 2005-08-24 09:49:09
Subject: Re: "Official" version
Previous:From: Anoop KumarDate: 2005-08-24 09:25:28
Subject: Re: ODBC Problem

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