unicode error and problem

From: Paolo Supino <paolo(at)telmap(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: unicode error and problem
Date: 2004-03-24 10:33:27
Message-ID: 143CFA2E3C9B5D459E78DA18E3F15F899AB2AF@plague.telmap.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hi

I received a unicode CSV file from someone (the file was created on a
windows system) and I'm trying to import it into postgresql. When it gets to
a line that isn't ascii it prints the following error and aborts: "ERROR:
copy: line 33, Invalid UNICODE character sequence found (0xd956)". When I
created the db cluster with "-E unicode" and initdb was run with "-E
unicode". As I wrote above the file was created on a windows system. I'm
trying to import it to postgresql 7.3.5 on a Solaris 9 system. Postgresql
was compiled by me with the following configure switches:
./configure --prefix=/usr/local --sysconfdir=/etc
--sharedstatedir=/usr/local/share --localstatedir=/var --enable-locale
--enable-recode --enable-multibyte --enable-nls
--with-java --with-openssl=/usr/local --with-CXX --enable-syslog
--with-includes=/usr/local/include --with-libraries=/usr/local/lib.

Anyone knows how to solve this problem so that the file will be imported
properlly?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message ogjunk-pg 2004-03-24 10:37:13 No pg_hba.conf entry for host localhost (was: Re: createused + createdb problems with passwords)
Previous Message Richard Huxton 2004-03-24 10:18:03 Re: createused + createdb problems with passwords

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Huxton 2004-03-24 13:30:28 Re: pg_advisor schema proof of concept
Previous Message Richard Huxton 2004-03-24 10:25:25 Re: where can I get the HTML docs