--- Dave Page <dpage@vale-housing.co.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 7.03.02.00 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 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. This might matter, and I only brought it up because you
were asking for feedback on testing of the new ODBC driver.
CG
CG
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html