From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Antonio Gallardo" <antonio(at)apache(dot)org> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [BUG] - Invalid UNICODE character sequence found(0xc000) |
Date: | 2004-02-02 03:26:14 |
Message-ID: | 27455.1075692374@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
"Antonio Gallardo" <antonio(at)apache(dot)org> writes:
> Paul Thomas dijo:
>> I can reproduce this on my Fedora machine. On an older system with RH7.2
>> and PG 7.3.4 compiled from source, I don't get the problem. Re-compiling
>> from source on the Fedora machine still gives the error. HTH
> I already filled a bug in Fedora:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=113231
I was finally able to reproduce this with Paul's help.
The bug turns out not to be Fedora-specific at all. I believe it will
happen on any platform if you are using both a multibyte database
encoding (such as Unicode) *and* a non-C locale.
PG 7.4 has a more restricted form of the bug --- it's not locale
specific but does still require a multibyte encoding. Here is a Unicode
example:
test=# select * from test where txtfield like '\277%'; --
ERROR: invalid byte sequence for encoding "UNICODE": 0xc0
I've committed fixes in both CVS branches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Di Mauro | 2004-02-02 09:58:22 | Problem wih JDBC driver under Windows XP |
Previous Message | Dave Cramer | 2004-02-01 18:52:49 | Re: FW: [webmaster] jdbc site: documentation links broken |