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

Re: New driver snapshot - 07.03.0209

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <cgg007(at)yahoo(dot)com>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: New driver snapshot - 07.03.0209
Date: 2004-04-16 14:24:08
Message-ID: 03AF4E498C591348A42FC93DEA9661B889FA88@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: Chris Gamache [mailto:cgg007(at)yahoo(dot)com] 
> Sent: 16 April 2004 14:59
> To: Dave Page; pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] New driver snapshot - 07.03.0209
> 
> 
> I guess what I'm getting at is 7.03.02.00 DOES behave differently than
> 7.03.02.09 in this situation. I don't know with which driver 
> there was a problem, old or new. 

My understanding is that sometimes non-multibyte code will work with
multibyte characters depending on how the app interprets the data. We
saw this in pgAdmin II which could often insert characters like umlauts
into an SQL_ASCII database, which then failed with pgAdmin III which has
full-blown Unicode support and refused to read the 'broken' characters.
In that case the answer was to use Unicode or Latin1 iirc.

> This might matter, and I 
> only brought it up because you were asking for feedback on 
> testing of the new ODBC driver.

All feedback is good :-)

Regards, Dave.

pgsql-odbc by date

Next:From: Lawrence_FisherDate: 2004-04-16 15:49:55
Subject: Strange error message
Previous:From: Chris GamacheDate: 2004-04-16 13:58:55
Subject: Re: New driver snapshot - 07.03.0209

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