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

From Antonio Gallardo
Subject Re: [BUG] - Invalid UNICODE character sequence found(0xc000)
Date
Msg-id 35282.10.0.0.5.1073657905.squirrel@ags01.agsoftware.dnsalias.com
Whole thread Raw
In response to Re: [BUG] - Invalid UNICODE character sequence found(0xc000)  ("Antonio Gallardo" <antonio@apache.org>)
Responses Re: [BUG] - Invalid UNICODE character sequence found(0xc000)
Re: [BUG] - Invalid UNICODE character sequence found(0xc000)
Re: [BUG] - Invalid UNICODE character sequence found(0xc000)
List pgsql-jdbc
OK. Confirmed:

Steps to reproduce:

1. createdb -E UNICODE mydbname.
2. create a table with some varchar inside, we will query on this field.
Example:

CREATE TABLE auth_role
  (
    rol_id      int4          not null default
nextval('auth_rol_rol_id_seq'),
    rol_name    varchar(50)   unique not null,
    rol_enable  boolean       default true,

    primary key(rol_id)
  );

INSERT INTO auth_role(rol_name,rol_enable) VALUES ('admin',true);
INSERT INTO auth_role(rol_name,rol_enable) VALUES ('zorro',true);

3. run psql and write a select like this:

SELECT * FROM AUTH_ROLE WHERE ROL_NAME LIKE 'z%';

After all you was right, this is not a JDBC related bug! :-D

Since we can also reproduce it using psql. I hoped it was my fault, but
looks like a postgresql bug. :-(

Please confirm the bug.

Best Regards,

Antonio Gallardo

> in psql the "SELECT version();" returns:
>
> PostgreSQL 7.3.4-RH on i386-redhat-linux-gnu, compiled by GCC
> i386-redhat-linux-gcc (GCC) 3.3.2 20031022 (Red Hat Linux 3.3.2-1)
>


pgsql-jdbc by date:

Previous
From: "Antonio Gallardo"
Date:
Subject: Re: [BUG] - Invalid UNICODE character sequence found(0xc000)
Next
From: Csaba Nagy
Date:
Subject: Re: [BUG] - Invalid UNICODE character sequence found(0xc000)