Re: [BUG] - Invalid UNICODE character sequence found (0xc000) - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: [BUG] - Invalid UNICODE character sequence found (0xc000)
Date
Msg-id Pine.LNX.4.33.0401090330460.6759-100000@leary.csoft.net
Whole thread Raw
In response to [BUG] - Invalid UNICODE character sequence found (0xc000)  ("Antonio Gallardo" <antonio@apache.org>)
Responses Re: [BUG] - Invalid UNICODE character sequence found
List 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


pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: Nmber of rows in a ResultSet
Next
From: Kris Jurka
Date:
Subject: Re: [BUGS] jdbc1.AbstractJdbc1Statement.setBinaryStream bug and