Re: UNICODE

From: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
To: Marko Kreen <marko(at)l-t(dot)ee>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: UNICODE
Date: 2001-10-28 11:44:26
Message-ID: 4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-hackers

I only want this query to work under Unicode:
SELECT * FROM test WHERE source_content ILIKE '%accepté%'.

>* If client_encoding == server_encoding, the bytes are put into
> DB as-is - no conversion is done.
>
>So are you absolutely sure you have on client side UTF8 strings?
PostgreSQL is compiled with UNICODE and LOCALE support.
Unicode is used on both ends (PostgreSQL and psql).

>Unfortunately you cant use client_encoding=latin1 as PostgreSQL
>refuses the do the conversion between them. (I am with 7.1.3)
According to the on-line manual, only MULE provides instant transcoding.

>Eg. I did the following:
>
>* created db with encoding = UNICODE
>* Put your example into test.sql
>* iconv -f latin1 -t utf8 test.sql > test2.sql
>* psql < test2.sql
>
>and it worked as it should...

Nice to hear it works when transcoding files to UTF-8. It shows it is not a
back-end problem.

As for me, I typed INSERT INTO source_content VALUES ('Permis de conduire
accepté') in Psql.
Psql does not insert the data and I have to kill it manually. Can you
reproduce this?

Best regards,
Jean-Michel POURE

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Marko Kreen 2001-10-28 12:05:47 Re: UNICODE
Previous Message Marko Kreen 2001-10-28 10:53:55 Re: UNICODE

Browse pgsql-general by date

  From Date Subject
Next Message Marko Kreen 2001-10-28 12:05:47 Re: UNICODE
Previous Message Uros Gruber 2001-10-28 11:38:21 Problem with some function

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2001-10-28 12:05:47 Re: UNICODE
Previous Message Marko Kreen 2001-10-28 10:53:55 Re: UNICODE