Re: [BUG] - Invalid UNICODE character sequence found(0xc000)

From: Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-jdbc (at) postgresql (dot) org" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [BUG] - Invalid UNICODE character sequence found(0xc000)
Date: 2004-02-02 10:53:25
Message-ID: 20040202105325.H9502@bacon
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc


On 02/02/2004 03:26 Tom Lane wrote:
> 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.

Thanks Tom. I've recompiled on my Fedora box using 7.3 CVS tip and it's
now a happy bunny :)

--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller
Business |
| Computer Consultants |
http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+---------------------------------------------+

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Paul Thomas 2004-02-02 10:58:38 Re: Problem wih JDBC driver under Windows XP
Previous Message Bhushan Bhangale 2004-02-02 10:04:58 Re: Problem wih JDBC driver under Windows XP