This is a discussion on Re: changed behavior in libpq odbc driver within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto gsql-odbc-owner@postgresql.org] On Behalf Of Anoop Kumar > Sent: 24 August 2005 ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > -----Original Message----- > From: pgsql-odbc-owner@postgresql.org > [mailto > 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. ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |