Alvaro Herrera a écrit :
> Arnaud Lesauvage wrote:
>> Tomi NA a écrit :
>> >>I think I'll go this way... No other choice, actually !
>> >>The MSSQL database is in SQL_Latin1_General_CP1_Cl_AS.
>> >>I don't really understand what this is. It supports the euro
>> >>symbol, so it is probably not pure LATIN1, right ?
>> >
>> >I suppose you'd have to look at the latin1 codepage character table
>> >somewhere...I'm a UTF-8 guy so I'm not well suited to respond to the
>> >question. :)
>>
>> Yep, http://en.wikipedia.org/wiki/Latin-1 tells me that
>> LATIN1 is missing the euro sign...
>> Grrrrr I hate this !!!
>
> So use Latin9 ...
Of course, but it doesn't work !!!
Whatever client encoding I choose in postgresql before
COPYing, I get the 'invalid byte sequence error'.
The farther I can get is exporting to UNICODE and importing
as UTF8. Then COPY only breaks on the euro symbol (otherwise
it breaks very early, I think on the first "non-ascii"
character).
--
Arnaud
