From: | Dennis Gearon <gearond(at)fireserve(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange UTF-8 behaviour |
Date: | 2004-09-16 16:34:54 |
Message-ID: | 4149C0AE.2030101@fireserve.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
My guess is that something in the chain of getting the data into the
database is measuring:
BYTES
not
CHARACTERS.
"Marco Ferretti" <marco(dot)ferretti(at)jrc(dot)it> wrote:
</quote--------------------------------------->
<snip>
I have created a database with the UTF-8 encoding (createdb cassa
--encoding=UTF-8) .
Then I have made the following tests :
cassa=> create table test(id varchar(5));
cassa=> insert into test values ('12345');
INSERT 178725 1
cassa=> insert into test values ('123è');
INSERT 178726 1
cassa=> insert into test values ('1234è');
ERROR: value too long for type character varying(5)
<snip>
so, apparently the chars are stored the rigth way ( #123è#) but when
trying the query the è char is parsed as 2 chars ....
The database server version is 7.3.4 on a RedHat 9 machine ...
Any clue ?
</quote--------------------------------------->
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff | 2004-09-16 16:35:50 | Re: Postgres memory usage |
Previous Message | Tom Lane | 2004-09-16 16:22:27 | Re: plpgsql assigning RECORD := RECORD |