Re: changed behavior in libpq odbc driver

so I'm definitely still able to reproduce this problem.
The test I'm running is somewhat complex, I can work on simplifying it.
Maybe the error code is left around from before and not properly cleared?

-----Original Message-----
From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
Sent: Wednesday, September 07, 2005 8:23 AM
To: Scot Loach; Anoop Kumar
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] changed behavior in libpq odbc driver

Hmm, I hope not - the dup key test was the main one I used when testing!

/D

> -----Original Message-----
> From: Scot Loach [mailto:sloach(at)sandvine(dot)com]
> Sent: 07 September 2005 13:10
> To: Dave Page; Anoop Kumar
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] changed behavior in libpq odbc driver
>
> I'm pretty sure my driver had that change already.
> I'll update and double check though.
>
> -----Original Message-----
> From: Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
> Sent: Wednesday, September 07, 2005 3:35 AM
> To: Scot Loach; Anoop Kumar
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] changed behavior in libpq odbc driver
>
>
>
>
> > -----Original Message-----
> > From: Scot Loach [mailto:sloach(at)sandvine(dot)com]
> > Sent: 07 September 2005 01:32
> > To: Anoop Kumar
> > Cc: pgsql-odbc(at)postgresql(dot)org; Dave Page
> > Subject: RE: [ODBC] changed behavior in libpq odbc driver
> >
> > I've found a problem with this.
> > This causes the correct state to be returned on db
> disconnect, great.
> > Unfortunately 08S01 is now returned for other errors as well.
> > For example, trying to insert a row with a duplicate key into
> > a table will cause 08S01 to be returned now, this was not the
> > behavior before.
>
> That's already fixed in CVS.
>
> http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/
> connection
> .c.diff?r1=1.108&r2=1.109
>
> Regards, Dave.
>