Skip site navigation (1) Skip section navigation (2)

Re: changed behavior in libpq odbc driver

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Scot Loach" <sloach(at)sandvine(dot)com>,"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 07:35:27
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9EF7@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----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.

pgsql-odbc by date

Next:From: Dave PageDate: 2005-09-07 07:40:56
Subject: Re: Using Which Driver [correct]
Previous:From: Scot LoachDate: 2005-09-07 00:31:45
Subject: Re: changed behavior in libpq odbc driver

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group