From: | "Antonio Gallardo" <antonio(at)apache(dot)org> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [BUG] - Invalid UNICODE character sequence found(0xc000) |
Date: | 2004-01-09 14:18:25 |
Message-ID: | 35282.10.0.0.5.1073657905.squirrel@ags01.agsoftware.dnsalias.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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)
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Rawnsley | 2004-01-09 14:28:43 | Re: PreparedStatement parameters and mutable objects |
Previous Message | Antonio Gallardo | 2004-01-09 14:05:49 | Re: [BUG] - Invalid UNICODE character sequence found(0xc000) |