| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, paolo(at)telmap(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: unicode error and problem |
| Date: | 2004-03-24 16:36:40 |
| Message-ID: | 200403241636.40129.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wednesday 24 March 2004 14:15, Tatsuo Ishii wrote:
> > 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
>
> The error messages all. 0xd956 cannot be proper UNICODE (actually
> UTF-8 in case of PostgreSQL) character at all.
I _think_ I've seen something very similar though, with one of the WIN9999
charsets. Can't remember for sure, but it's probably worth checking.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Harris | 2004-03-24 16:48:30 | postmaster won't start under cygwin after password change |
| Previous Message | Mike Nolan | 2004-03-24 16:33:39 | case statement as inline function? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-03-24 16:39:35 | Re: Chapter on PostreSQL in a book |
| Previous Message | scott.marlowe | 2004-03-24 16:32:52 | Re: Log rotation |