Re: LATIN1/9 conversion.... - Mailing list pgsql-odbc

From Dave Cramer
Subject Re: LATIN1/9 conversion....
Date
Msg-id E94B8BA4-D365-4CCF-B318-C8B08D690805@fastcrypt.com
Whole thread Raw
In response to Re: LATIN1/9 conversion....  ("Tim Clarke" <Tim.Clarke@manifest.co.uk>)
List pgsql-odbc
So what is the upshot of all of this. I have a client who is seeing
the same error messages.

They have tried the unicode driver but get connection errors which
eventually cause IIS to crash.

Dave
On 10-Feb-06, at 9:23 AM, Tim Clarke wrote:

> Marc.
> That is a useful interjection, ISTR trying many of the combinations of
> export coding in latinx from Oracle and postgreSQL database latiny
> coding. Not sure if I hit 9 tho. The instant we the overnight oracle
> data transfer out of the way I shall try to dump and rebuild the
> database in unicode. I hope that cures these issues once and for
> all...
>
> Tim Clarke
>
>> -----Original Message-----
>> From: pgsql-odbc-owner@postgresql.org
>> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Marc Herbert
>> Sent: 10 February 2006 13:56
>> To: pgsql-odbc@postgresql.org
>> Subject: Re: [ODBC] LATIN1/9 conversion....
>>
>>
>> Ludek Finstrle <luf@pzkagis.cz> writes:
>>
>>> Could you try LATIN1 database with Unicode psqlODBC driver?
>>> Does it still break the euro symbol?
>>>
>>
>> By the way latin9 is the "fixed" version of the obsolete latin1.
>> Among
>> the fixes there was the addition of the euro symbol.
>>
>> <http://czyborra.com/charsets/iso8859.html#ISO-8859-15>
>>
>> My two cents.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
>


pgsql-odbc by date:

Previous
From: Tony Caduto
Date:
Subject: Re: Access2000 & sequence as primary key in view : #DELETED
Next
From:
Date:
Subject: [ psqlodbc-Bugs-1000749 ] Crashes when using SSL with 8.02.0002 and .0100