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 14:34:49 +0100
Message-ID: <4.2.0.58.20011028140833.00d13490@pop.freesurf.fr> (raw)
In-Reply-To: <20011028140547.A15516@l-t.ee>
References: <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr>
	<4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr>
	<4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr>
	<4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr>


>psql uses your input literally - so is your console/xterm in
>UNICODE/UTF8?
Client: \encoding returns 'UNICODE'.
Server: \list show databases. All databases are UNICODE (except TEMPLATE0 
and TEMPLATE1 which are ASCII of course). I use a Mandrake 8.1 distribution 
and think my console is UNICODE.

> > As for me, I typed INSERT INTO source_content VALUES ('Permis de conduire
> > accepté') in Psql.
>As I said - psql does not do any conversion.
The faulty query is: INSERT INTO test (source_content) VALUES ('Permis de 
conduire accepté');

I just can't believe that Psql is not UTF-8 compatible. It seems unreal as 
Psql is PostgreSQL #1 helper application. Should I use PostgreSQL MULE 
encoding to have automatic trans coding. What are the guidelines, I am 
completely lost.

> > Psql does not insert the data and I have to kill it manually. Can you
> > reproduce this?
>No.  If it hangs this is serious problem.  Or did you simply
>forgot final ';' ?   It btw does not seem valid sql to me,
>considering you previously provided table structure.
Is it possible that my database is corrupted? I have used pg_dump several 
times to dump data from production server to development servers and 
conversely. Does pg_dump produce UTF8 output? What are the guidelines when 
using UTF-8: forget psql and pg_dump?

>In the end: are the strings/queries you give to psql/pg_exec
>UTF-8 - this is now main thing, as you have _configured_
>everything correctly.
Everything is configured correctly server-side (PostgreSQL, Psql).

Thank you very much for your support Marko,
Best regards,
Jean-Michel





view thread (23+ messages)  latest in thread

Message-ID: <4.2.0.58.20011028140833.00d13490@pop.freesurf.fr>
Permalink:  ../4.2.0.58.20011028140833.00d13490@pop.freesurf.fr/
Also on:    postgresql.org/message-id/4.2.0.58.20011028140833.00d13490@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.20011028140833.00d13490@pop.freesurf.fr>
  References: <4.2.0.58.20011028121057.00d1a100@pop.freesurf.fr> <4.2.0.58.20011028085953.00cfa740@pop.freesurf.fr> <4.2.0.58.20011028140833.00d13490@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