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 13:02:42
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9F32@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 13:48
> To: Dave Page; Anoop Kumar
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] 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?

Well the only time the error code should be set is if libpq reports the
connection as being bad, so if you're definitely seeing it, it must be
coming from somewhere else, or you're not checking the error code when
it actually arrives. 

Can you add a mylog line into the relevant part of the fix I posted so
youo can see if the error code is being set somewhen that you don't
otherwise notice?

Regards Dave

pgsql-odbc by date

Next:From: Tom LaneDate: 2005-09-07 14:48:59
Subject: Re: notice handler in libpq-based driver
Previous:From: Scot LoachDate: 2005-09-07 12:48:15
Subject: Re: changed behavior in libpq odbc driver

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