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

Re: New driver snapshot - 07.03.0209

From: Chris Gamache <cgg007(at)yahoo(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: New driver snapshot - 07.03.0209
Date: 2004-04-16 13:58:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
--- Dave Page <dpage(at)vale-housing(dot)co(dot)uk> wrote:
> That'll be the problem then. SQL_ASCII is only 7 bit ASCII safe (iirc)
> which those characters are certainly not. I'm the last person you want
> to ask about charactersets etc, but my guess is that you'll need to use
> UNICODE to /properly/ work with characters such as these.

You're the second-to-last person who should be asked about character sets. :) 

I wonder why those characters appear properly using the driver? Was
it incorrect behavior? There were three drivers that came standard in the
PostgreSQL MSI installer, the Standard 3.0 driver, the Legacy Driver, and the
Beta-Unicode driver. I was using the standard driver. If it didn't support the
extended ASCII characters, I wonder how those characters got inserted in the
first place?

I guess what I'm getting at is DOES behave differently than in this situation. I don't know with which driver there was a
problem, old or new. This might matter, and I only brought it up because you
were asking for feedback on testing of the new ODBC driver.



Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th

In response to

pgsql-odbc by date

Next:From: Dave PageDate: 2004-04-16 14:24:08
Subject: Re: New driver snapshot - 07.03.0209
Previous:From: Ibrahim El-FayoumiDate: 2004-04-16 08:56:08
Subject: long long under unixodbc

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