Re: changed behavior in libpq odbc driver - Mailing list pgsql-odbc

From Anoop Kumar
Subject Re: changed behavior in libpq odbc driver
Date
Msg-id B4AF8C04F762D246A1E38EC5DFAEFC0B0379C5@blrmail2.aus.pervasive.com
Whole thread Raw
In response to changed behavior in libpq odbc driver  ("Scot Loach" <sloach@sandvine.com>)
Responses Re: changed behavior in libpq odbc driver  (Zoltan Boszormenyi <zboszor@dunaweb.hu>)
List 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@vale-housing.co.uk]
> Sent: Wednesday, August 24, 2005 3:16 PM
> To: Anoop Kumar; Scot Loach
> Cc: pgsql-odbc@postgresql.org
> Subject: RE: [ODBC] changed behavior in libpq odbc driver
>
>
>
> > -----Original Message-----
> > From: pgsql-odbc-owner@postgresql.org
> > [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Anoop Kumar
> > Sent: 24 August 2005 07:17
> > To: Scot Loach
> > Cc: pgsql-odbc@postgresql.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:

Previous
From: "CHEN"
Date:
Subject: Trouble with encoding again
Next
From: "Dave Page"
Date:
Subject: Re: changed behavior in libpq odbc driver