Good news: This is not a OJB bug, it is a Postgres bug!
Steps to reproduce:
1. create a database using UNICODE (UTF-8):
createdb -E UNICODE mydbname.
2. create a table with some varchar inside, we will query on this field.
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:
SELECT * FROM AUTH_ROLE WHERE ROL_NAME LIKE 'z%';
4. You got the error!
ERROR: Invalid UNICODE character sequence found (0xc000)
The problem is related to the string 'z%'.
If you replace the string with 'a%' or za% or any other sequence that does
not contain 'z%" then you don't get the bug.
After all you was right, this is not a OJB 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)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
