Re: changed behavior in libpq odbc driver

From: "Scot Loach" <sloach(at)sandvine(dot)com>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: changed behavior in libpq odbc driver
Date: 2005-09-07 12:09:33
Message-ID: 71837C040963F748B9B94E123A289678664E68@mailserver.sandvine.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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.

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2005-09-07 12:23:28 Re: changed behavior in libpq odbc driver
Previous Message Carlos Henrique Reimer 2005-09-07 11:24:16 Application bottlenecks