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

From: Kris Jurka <books(at)ejurka(dot)com>
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-01-09 08:33:02
Message-ID: Pine.LNX.4.33.0401090330460.6759-100000@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Thu, 8 Jan 2004, Antonio Gallardo wrote:

> Hi:
>
> In the tested web application, we use postgreSQL JDBC driver. We have a 1
> field form where we allow the user to writte a search pattern a table. The
> generated SQL use LIKE to find for similars. Example:
>
> This works fine, even if we left empty the form field, to show all the
> records.
>
> The interesting stuff I found is:
>
> If we write just "z", "Z" or any string with that include the chars "z" or
> "Z" at any point of the string in the field, then I got the below error.
> How is this posible? I not an UTF-8, ISO-8859-1 or SQL_ASCII expert, but
> for me "z" or "Z" is part of the ASCII that means a 1 byte code in UTF-8.
>
> That means the driver has problems with an normal "z" or "Z"?
>
> Note: The same apply for the drivers:
>

Could you possibly write a standalone Java program that demonstrates this
error? What encoding is your database? What encoding is you web
application running in? What encoding is used in the browser?

Kris Jurka

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2004-01-09 08:46:04 Re: jdbc1.AbstractJdbc1Statement.setBinaryStream bug and
Previous Message Kris Jurka 2004-01-09 08:25:32 Re: Nmber of rows in a ResultSet