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

From Scot Loach
Subject Re: changed behavior in libpq odbc driver
Date
Msg-id 71837C040963F748B9B94E123A289678664E68@mailserver.sandvine.com
Whole thread Raw
In response to changed behavior in libpq odbc driver  ("Scot Loach" <sloach@sandvine.com>)
List pgsql-odbc
I'm pretty sure my driver had that change already.
I'll update and double check though.

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




> -----Original Message-----
> From: Scot Loach [mailto:sloach@sandvine.com]
> Sent: 07 September 2005 01:32
> To: Anoop Kumar
> Cc: pgsql-odbc@postgresql.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.

pgsql-odbc by date:

Previous
From: Carlos Henrique Reimer
Date:
Subject: Application bottlenecks
Next
From: "Dave Page"
Date:
Subject: Re: changed behavior in libpq odbc driver