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: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>,"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-25 05:56:49
Message-ID: B4AF8C04F762D246A1E38EC5DFAEFC0B0379C5@blrmail2.aus.pervasive.com (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Dave,

OK, I shall look into the state code problem and dead connection
detection issues. :-)

Regards

Anoop

> -----Original Message-----
> From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
> Sent: Wednesday, August 24, 2005 3:16 PM
> To: Anoop Kumar; Scot Loach
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] changed behavior in libpq odbc driver
> 
> 
> 
> > -----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.

Responses

pgsql-odbc by date

Next:From: Dave PageDate: 2005-08-25 08:46:24
Subject: Re: changed behavior in libpq odbc driver
Previous:From: CHENDate: 2005-08-25 02:43:00
Subject: Trouble with encoding again

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