Skip site navigation (1) Skip section navigation (2)

Re: [CYGWIN] Question about character encoding

From: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
To: "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de>,<pgsql-cygwin(at)postgresql(dot)org>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [CYGWIN] Question about character encoding
Date: 2002-02-21 13:27:25
Message-ID: 200202211327.g1LDRPFP001808@www1.translationforge (view raw or flat)
Thread:
Lists: pgadmin-hackerspgsql-cygwin
> I installed the latest cygwin snapshot along with PostgreSQL 7.2; I
> access the DB using the latest PGAdmin II 1.2.0. Almost everything seems
> to be working fine - with one major glitch: I just cannot insert nor
> select strings containing german umlaute or any other special characters
> into my database.
> I selected Unicode as encoding (was that correct?), but when I do

pAlthough it may sound strange, gAdmin2 is not yet compatible with Unicode 
for various reasons explained at pgadmin-hackers(at)postgresql(dot)org(dot) Unicode is 
mainly used for non european languages.

SQL_ASCII encoding can handle most european languages, including German. So, 
just create a database with SQL_ASCII encoding. And this will solve your 
problem. 

(If you are really interested by Unicode, use pgAdmin2 to create and maintain 
the schema of your database. But don't use it ***yet*** to view or insert 
data. Use Apache/Php or Java instead.)

Das lebte die deutsche-französische Freundschaft,
Jean-Michel pOURE


Dave : I am going to set defaut database encoding to SQL_ASCII. This will 
avoid a confusion.



In response to

pgsql-cygwin by date

Next:From: Dave PageDate: 2002-02-21 13:33:53
Subject: Re: [CYGWIN] Question about character encoding
Previous:From: Markus WollnyDate: 2002-02-21 13:06:29
Subject: Question about character encoding

pgadmin-hackers by date

Next:From: Dave PageDate: 2002-02-21 13:33:53
Subject: Re: [CYGWIN] Question about character encoding
Previous:From: Markus WollnyDate: 2002-02-21 13:06:29
Subject: Question about character encoding

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group