pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jean-Michel POURE <jm.poure@freesurf.fr>
To: Marko Kreen <marko@l-t.ee>
Cc: pgsql-hackers@postgresql.org
Subject: Re: UNICODE
Date: Sun, 28 Oct 2001 12:44:26 +0100
Message-ID: <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr> (raw)
In-Reply-To: <20011028125354.A13053@l-t.ee>
References: <4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr>
	<4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr>

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



view thread (23+ messages)  latest in thread

Message-ID: <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr>
Permalink:  ../4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr/
Also on:    postgresql.org/message-id/4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jm.poure@freesurf.fr, marko@l-t.ee, pgsql-hackers@postgresql.org
  Subject: Re: UNICODE
  In-Reply-To: <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr>
  References: <4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr> <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox